A reply is a change in workflow
A reply webhook or a monitored inbox starts this process. The output is an owned next action, suppression where required and a CRM receipt linked to the original campaign. A classifier's label is not a response, and a positive reply is not a qualified meeting.
Keep the full thread available to the owner. “Not now” may be a timing instruction, a polite rejection or an out-of-office message. The account context and the wording decide the path.
Process in a safe order
- Match the event to the thread, sender, account and campaign. Deduplicate repeated provider notifications using a stable event key.
- Pause remaining automated touches for that contact immediately. A later classifier error should not let the old sequence continue.
- Check opt-out and complaint language before interpreting commercial interest. Write suppression to the central list and connected senders; retry failed writes visibly.
- Distinguish automated replies from human responses. A return date can schedule a review, but it is not permission to bypass an opt-out elsewhere in the thread.
- Assign a category with a reason and confidence. Low confidence or contradictory instructions go to a person, not an automatic message.
- Resolve the existing account or opportunity owner. Interested replies get the context, the original reason for outreach and a useful response draft.
- Treat referrals as proposed introductions. Verify the new person's role and eligibility before contacting them. Do not convert a referral into automatic enrollment.
- The owner reviews and sends the response. Log the category, action, deadline and CRM stage without overwriting original campaign attribution.
The owner receipt
- Thread
- Matched to the approved signal-led cohort
- Category
- Interested, needs context about implementation
- Automation
- Remaining touches paused
- Owner action
- Review the draft and arrange the next conversation
- Commercial stage
- Positive reply; qualification still pending
Exceptions to make visible
| Reply | Next action |
|---|---|
| “Please remove me” | Suppress and record the completed writes |
| “Talk to our ops lead” | Review the referral and role before contact |
| “Next quarter” | Record the stated time and an owner review task |
| Ambiguous or hostile response | Human review; no automatic persuasion |
| Provider webhook repeats | Keep one disposition and no duplicate task |
Test the whole path
Replay an opt-out, interested reply, referral, out-of-office, duplicate event and a reply to an already open deal. Simulate a suppression write failure. The system must keep the sequence paused, expose the failure and retry without sending a new message.
Measure time to an owned action, unowned replies, suppression completion and qualified conversations. Report reply categories and denominators. Do not combine automated responses with human positive replies or equate meetings booked with opportunities created.
Feed back useful evidence
Bad-fit and wrong-person replies correct the ICP and buying-group map. Timing replies test signal decay and campaign windows. Interested replies test the message's usefulness, while qualification tests the offer. Keep those observations separate in the company brain so the next campaign improves for the right reason.
Publication and source record
Published on GTMhub: . Last reviewed: .