outbound · manual
← Control room

Outbound Machine — Operator Guide

URL: https://outbound.bogowi.com/

What it is: Control panel for the B2B outbound pipeline (easychain + B-Web3).

Who logs in: @kode.zone accounts (Hugo, Barbara, Jonathan). Get your password from Hugo on a private channel — not in public chats or GitHub issues.


1. What this is (1 minute)

Not a classic CRM and not a bulk mail blaster.

It is a signal-first outbound pipeline:

  1. Find companies (harvest).
  2. Research them from public data — website, resale listings, reviews, news, contacts. That step is Enrich (Claude + web search/fetch).
  3. Score fit, pain evidence, and timing → quality TOP / HIGH / MEDIUM / LOW.
  4. You review, assign, fill gaps, and send email by hand from the warmed outreach mailbox.
  5. Log outcomes in the panel (contacted → replied → meeting) so the funnel stays accurate.

The email should open with their situation and numbers (e.g. tickets on StubHub, review volume with no loyalty program), always backed by evidence URLs.

Hard rules:

Verticals:

Code Product Brand What we measure
T Anti-scalping ticketing easychain Secondary-market / StubHub-style resale
L Loyalty / rewards wallets B-Web3 Reviews, missing loyalty, OTA dependency

Senders: Hugo → T · Barbara → L · Jonathan → books meetings after a reply (not a cold sender).


2. Sign in

  1. Open https://outbound.bogowi.com/
  2. Log in with email (name@kode.zone or local part, e.g. barbara).
  3. Sign out when done (top right).

If login fails: private window or hard refresh. If it still fails, contact whoever runs the server.

Manual on the site: https://outbound.bogowi.com/manual (also Manual in the panel).

Something broken: Feedback → opens a GitHub issue.


3. Screen map

Area Purpose
Pipeline / Territories Lead funnel vs countries/cities to harvest
Stage rail harvested → enriched → approved → contacted → replied → meeting → disqualified
Filters T/L · quality TOP/HIGH/MEDIUM/LOW · country · city · owner
Queue (left) Leads in the current stage
Dossier (right) Detail: quality, owner, next step, email draft, evidence, history
enrich / score / sync gmail Jobs that move data (enrich spends API money)

Quality badge (after score):

Badge Meaning (score total)
TOP A · ≥ 26 — priority
HIGH B · ≥ 18
MEDIUM C · ≥ 10
LOW / unscored D, or not scored yet

Queue sorts TOP first.


4. Typical weekly flow

A) Add companies (harvest)

B) Enrich

C) Score

D) Review

  1. Stage enriched.
  2. Filter TOP (then HIGH if needed).
  3. Open dossier: you are here → do this, evidence, contacts.
  4. Approve or Reject (a / r on enriched).

E) Prepare and send email

  1. Stage approved.
  2. Check email preview and gaps / missing for send.
  3. Close gaps: manual fields (event, markup, leak €, audit URL…), verified contact email, brand legal / sending domain if blocking send.
  4. Copy subject + body.
  5. Send from the warmed outreach mailbox for that vertical.
  6. In the panel: Mark as contacted.

F) Replies and close


5. Owner

Filters: mine / unassigned / by person.


6. How to prioritise

  1. TOP first.
  2. Then HIGH.
  3. MEDIUM only if capacity.
  4. Bad reply rates → fix the hook, do not add mailboxes.

Keyboard (focus not in an input):

Key Action
j / k Next / previous in queue
a / r Approve / reject (enriched)
/ Search

7. Do not


8. If something fails

Symptom What to do
Site / lock icon Use exactly https://outbound.bogowi.com/
Login fails Password from Hugo; private window; do not hammer login (throttle)
Enrich stuck / error Check history and error block; do not re-run in a loop (costs money)
Email “incomplete” Each gap says why and how to fill it
Panel bug Feedback in the bar → GitHub issue

9. One line

Log in → filter TOP → check evidence → fill gaps → send by hand → update the funnel. The machine researches and ranks; you decide and talk to the prospect.

docs/operator-guide.md · https://outbound.bogowi.com/manual