Product / Replies & pipeline

Every reply is read, drafted, and then waits for you.

One inbox across every mailbox. Each inbound message is matched to the lead and the sequence that produced it, classified, and answered in draft. The draft sits in a queue. Approve and it goes; edit and your version goes; do nothing and nothing happens.

Triage — example data
Needs reply 4
Interested 2
Question 1
Objection 1
Unclassified 0
No reply yet 318
Handled automatically 11
All mail 337

Handled automatically is where out-of-office, unsubscribe and dead-address replies go. They are recorded, filed, and never counted as a person replying.

Classification

What a reply can be, and what happens to each.

Interested

A draft is written from what the account knows about them. On approval it goes out in-thread and an opportunity opens with the thread attached.

Question

Answered in draft from the knowledge base. If the base does not cover it, the draft says so rather than inventing an answer.

Objection

Drafted for a person to weigh, never auto-closed. You decide whether it is a no or a not-yet.

Out of office

The return date is extracted. The lead is parked until then and resumed inside the campaign a person already launched. Anyone named as covering is captured as a suggested contact.

Wrong person / left the company

The named replacement, if any, becomes a suggested contact. Nothing is sent to them and no credit is spent until you approve the enrolment.

Unsubscribe

Honoured immediately and added to the do-not-contact list, whether or not you uploaded one.

Unclassified

Shown as unclassified. Not guessed into a bucket to keep the numbers tidy.

The queue

Four things you can do to a draft. Silence is not one of them.

Each queued reply shows the message you sent, the reply that came back, and the draft with a confidence tag. Low confidence is shown as low confidence.

Approve
The draft goes, as written
From the mailbox that started the thread, in the same thread.
Edit
Your version goes
The engine records the edit, and the share sent as written is a real metric on Setup.
Schedule
Goes at a time you pick
The only automated send in the product is the delivery of a draft a person approved.
Skip
Nothing goes
Filed, not deleted. A skipped reply still counts as a person who replied.

Guarded before it leaves: a draft carrying a repeated greeting or an unresolved merge token is refused at send time, on both send paths. A repeated signature is flagged rather than refused, because a quoted sign-off and a real one look alike and a false refusal costs a real reply.

Pipeline

Interested becomes an opportunity. Away becomes a date. Referred becomes a contact.

TabColumnsWhat it is for
AllContact · Company · Stage · Source · Heat · Last activityStages: new, meeting booked, completed, won, lost, transferred out. Heat is a three-bar score; when it cannot be computed it is a dash.
Waiting on usContact · Company · Waiting since · HeatThe ones where the last word was theirs.
Out of officeContact · Company · Back on · Days left · StatusWaiting, reminded, done or dismissed. A delay, not a dead end.
Suggested contactsNamed contact · Named by · Source · StatusCovering while away, referred by the prospect, or left the company. Captured is not enrolled: you approve each one.

Counting rule: a reply is one distinct person with at least one genuine inbound message. Automated replies are shown as their own number beside it, never folded in. See Campaigns & results.

Put a person on every send, without slowing the send down.

The queue is the whole job. Most mornings it is a handful of decisions.