Products / Fast Reply

Production tested

Every reply. One surface. Nothing buried.

FastReply pulls every sending mailbox into a single surface. Triage, reply, and follow up from one queue, no matter how many mailboxes sit behind it.

Join the waitlist -> See the workflow
Live

One queue for every reply.

Categorize a thread and the cascade runs itself: the deal is created, EmailBison is marked, the webhook fires, Slack hears about it.

$ inbox events (illustrative replay, not a live capture)
categorize thread as positive
✓ deal created in pipeline
✓ marked interested in EmailBison
✓ engaged-lead webhook fired
✓ Slack notified
Illustrative event shape. Counts, timing, and thread totals vary per inbox; see PROOF NEEDED below.
PROOF NEEDED - a real captured triage session (reply volume, categorization mix, cascade timing) to replace the illustrative replay above. The demo figures previously shown here (42 inboxes connected, 18 new replies, 6 positive threads ranked by intent) had no source in the owning repo and were removed.
What it is

The reply layer for a solo operator at scale.

FastReply is where all of it converges: one surface for every inbox, every reply, every follow-up. It is the Master Inbox app the GTM team runs daily, under its Legion name.

One surface, every inbox

Connect every sending mailbox into a single unified view. No tab-hopping across dozens of accounts to find the reply that matters.

Suggested categorization, grouped triage

Three-level grouping (Customer, Date, Categorization) with suggested categorization on every thread, so the ones that convert sit at the top of one queue.

Reply drafts start pre-filled

The reply agent drafts a first pass on incoming threads and pre-fills the reply box; you edit and send through the EmailBison API with CC and attachment support. You never start from blank.

Positive threads trigger the cascade

Categorizing a thread positive creates the deal, marks it in Bison, fires the engaged-lead webhook, and notifies Slack. One click, four systems updated.

Follow-ups stay visible

Out-of-office reminders with return-date filtering, subsequence tracking with progress dots, activities, and a weekly calendar. No thread goes quiet.

Slots and numbers on tap

Fetch client Cal.com times with smart slot selection and enrich prospect mobile numbers via Clay, all from inside the thread.

A read-only link, when a client needs the thread

Generate a share link for any thread. It opens to a read-only view of the conversation only, no CRM data, no categorization, and no internal notes.

Inside a look

Every mailbox on the left. Every reply on the right.

A live look at Fast Reply - open a reply, read the prospect's context, then respond.

Illustrative mock. No production run, customer outcome, or performance metric is claimed here.

PROOF NEEDED - a real inbox screenshot (redacted as needed) to replace the illustrative mock above.
The reply workflow

From every inbox to one next action.

01

Connect the fleet

Every sending mailbox flows into Fast Reply as one surface - however many are behind your campaigns.

02

Categorize the queue

Incoming replies arrive grouped by customer, date, and categorization, with a suggested category on each thread. The ones that convert sit at the top instead of drowning.

03

Act or hand off

Send the pre-filled draft as-is or edit it first, or let the positive-thread cascade file the deal and flag the meeting. You stay in control of what sends.

04

Follow-ups stay on screen

OOO reminders, subsequence tracking, and activities hold every thread open until it is done.

Part of the operating system

Works with the whole stack.

A thousand soldiers. One general. You.

Run every inbox like one operator.

FastReply comes with every founding seat, alongside the brain, the CLI, and a new system every month.

Join the waitlist ->