GTMGTM

Close · Replies

The answer is written while the reply is still warm

When a reply lands and it is not an opt-out, the answer is drafted immediately. Qualifying, or proposing the call, and queued, so it leaves on the next tick through the same gate as everything else. One unsent answer per thread is what stops a second being written while the first is still waiting.

Inbox14,208
AllRepliedBookedLost
Aisha BelloEmail

Thursday works. Send an invite for 2pm?

Booked
Priya RaghavanLinkedIn

Interesting. How does it handle our EU list?

Replied
Daniel OkoyeEmail

Not right now, maybe Q3.

Later
Jonas WeberEmail

Please take me off this list.

Opted out
Interesting. How does it handle our EU list?

Drafted · queued for the next tick

Honestly: we serve the US today and say so rather than implying otherwise. The controller-grade machinery is built. Provenance, retention, suppression, so an EU list is a decision rather than a rewrite. Worth twenty minutes Thursday?
Gate verdict recorded · unsubscribe and postal address injected

What is actually going on

Every claim below is followed by the mechanism under it, because a claim without a mechanism is a slide.

01

Drafted straight to queued, not parked for a human

There is no needs-approval folder. Removing a hold in front of the gate is not removing the gate, and every check that only ever ran because somebody clicked now lives on the launcher side.

02

A reply moves the heat, and outranks everything else

Replied with interest is 5, replied at all is 4. A negative reply is closed rather than cold. The heat is left alone rather than driven to 1 and mixed in with people who have simply not engaged.

03

Classification is a badge; the stop is not

The sequence stops on any inbound, before anything is classified. The label is for you.

04

Connector delivery retries rather than degrading

An event that cannot reach your CRM is queued and retried with backoff. Five minutes doubling to six hours, dead after eight attempts. Rather than silently lost on a card that says degraded.

Step by step

How reply handling runs

  1. 1

    Stop

    Pending steps for that contact are skipped.

  2. 2

    Screen

    Keyword opt-out pass. A match suppresses and ends it.

  3. 3

    Draft

    The answer is written from the thread and the evidence, and queued.

  4. 4

    Send

    Next launcher tick, through the gate, with the footer the transport appends.

The numbers

Facts, not adjectives

Every figure here is a real value from the running product. A cadence from the scheduler, a price from the credit table, a limit from the ramp. A marketing page that invents a limit is a support ticket with a delay on it.

CloseReplies
Draft latency
On arrival
Send latency
Next eligible minute tick
Per thread
One unsent answer at a time
Retry policy
5 min doubling, cap 6 h, dead at 8 attempts
Retry budget
25 deliveries per pass

Reply handling, honestly

What if I want to read it first?

Set the campaign to Supervised. Review the held steps inside that campaign and inspect conversation drafts in Inbox.

Can it book the meeting?

It proposes the call and works toward it. The booking lands on whichever calendar you connected, and the booked transition dispatches to your CRM.

Reply handling is one part of it. The rest runs too.

Sourcing, enrichment, intent, copy, sending, replies and reporting are one product with one bill and one gate. Connect a channel and the whole motion starts.

Start with sales. $2,000 or $5,000 onboarding, then at least $250 monthly credit funding.