Prospect Reply Handling SOP
Overview
- What: answer a reply to a prospecting email, and either book a discovery call or close the prospect out cleanly.
- When: any inbound reply from a prospect in the outreach cadence. Same day, on the channel it arrived.
- Who: Sales Development Representative answers. Implementation Lead takes anything commercial and runs the discovery call.
- Time Required: most replies are two minutes. The ones that are not are the ones that escalate.
Every prospecting document up to this point ends at the send. This one starts where they stop, and it is the document that makes a reply someone else's work instead of founder work.
Prerequisites
- Sub-account access to Conversations and Contacts, scoped per the onboarding SOP.
- The prospect's audit report open before replying. Nearly every question is about what is in it.
- The Objection Handling bank to hand. It is written for spoken calls; the substance transfers, the phrasing does not.
Policy
The handover line
Check whose name the first email went out in before you reply. Two things send the audit now, and they are signed differently.
| The audit went out as | Then |
|---|---|
| First Email - Offer or First Email - Audit Only, Email 1A, 1B or 1C (Templates 19 to 22), or the older automated report email — the Implementation Lead's name | You are answering for someone else. Use the handover line. A reply to Email 1A often names a time to call: book it, and do not dial before it |
Your own send after a call — the C-021.Prospecting Send Marketing Audit snippet, signed by you | You are answering for yourself. No handover line; just reply |
Answering for someone else, say so in the first sentence and do not be coy about it:
Hi {first name}, thanks for getting back to us. I work with {sender} at Symphony Core and look after the reports, so I can pick this up.
That is the whole trick. A named person who says who they are reads as a company; an unnamed person writing as someone else reads as a bait-and-switch, and the prospect will notice on the second exchange rather than the first.
Never answer as the Implementation Lead. Never sign that name, never use "I" for something they did.
What the SDR decides alone
| May decide | Never decides |
|---|---|
| When the call happens, and rescheduling it | Price, discounts, or terms |
| What a report section means, factually | Whether any guarantee applies |
| Whether to answer a question or escalate it | Whether SC can deliver something not in the offer |
| Closing a prospect out as not interested | Anything where the report looks wrong |
Escalate rather than improvise. A reply that seems to need judgement is a reply for the Implementation Lead, not a sentence to invent. Handing one over costs an hour; guessing at a commercial answer costs the prospect.
Rules that do not bend
-
Same day, on the channel it arrived. A reply to a cold email is a short window and it closes.
-
Never quote a score or percentage from the report. Hand-counted facts only — the same rule the emails follow.
-
"Remove me" is actioned immediately, before anything else:
sc-suppressed, and it is never removed.⚠️
sc-suppresseddoes not yet exist in the sub-account (verified live 2026-09-23). Create it on first use, spelled exactly, and set DND on the contact — DND is enforced by the platform, whereas nothing currently reads this tag. Both, not either. Tracked as S1-1 in the follow-up sprint. -
One ask per reply. The ask is the call. Do not stack a second.
-
A reply stops the cadence. Remaining touches are cancelled the moment someone answers.
Procedure
-
Read the report before the reply. Open the prospect's record and their audit report. Answering a question about a report you have not opened is the fastest way to lose the thread.
-
Classify the reply. One of these, every time.
Reply shape Action Tag Interested, or asks to talk Book it. Offer two concrete times, and a link prospecting-respondedAsks what something in the report means Answer factually in two sentences, then offer the call prospecting-respondedAsks the price The price line in Objection Handling and nothing beyond it: ninety-nine to start, nothing monthly until it gets them a job or gets their reviews moving, and the twenty-minute call is where the rest is answered. Escalate if they press prospecting-responded"Who are you / how did you get this" Answer straight: public business listing, report built from public sources, no list purchased. Offer to remove them prospecting-responded"Send me more information" The polite brush-off. Send one thing only — the report walkthrough — and ask a single question back prospecting-respondedWrong person Ask who owns it, thank them, correct the record prospecting-respondedNot interested One line, no argument, leave the door open. Close out prospecting-not-ready-nowRemove me, unsubscribe, do not contact Stop everything. Suppress. No reply beyond a one-line acknowledgement sc-suppressedHostile, or "this is spam" Apologise once, suppress, do not defend the email sc-suppressedAuto-reply or out of office Not a reply. Leave the cadence running none Bounce Not a reply. Clear the email from the record so nothing sends again none -
Send the reply. Plain text, in the same thread, from the SDR's own identity. Keep it under the length of the email they answered.
-
Book, if it is a booking. Offer two specific times in the prospect's timezone, plus the scheduling link as a fallback. Confirm in the thread once it is on the calendar.
-
Record it. Apply the tag above, cancel the remaining follow-up tasks, and note in one line what they actually said. The note is what the Implementation Lead reads before the call.
-
Hand over anything commercial, the same day, on the escalation channel. An escalation says: which prospect, what they asked, what you checked, what you would do.
Verification
Per reply:
- Answered the same day, in the same thread, signed by the person who wrote it.
- Exactly one tag applied, and the remaining cadence touches are cancelled.
- No price, no guarantee, no percentage from the report anywhere in the text.
- A one-line note on the record saying what the prospect said.
Weekly, by the Implementation Lead:
- Read three answered replies end to end. The test is whether the reply would have been sent the same way by either of you.
- Check that every
sc-suppressedapplied this week has a reply behind it that asked for it. - Count replies by bucket. This is the measurement the bucket taxonomy exists to produce, and it is the first week it becomes possible.
Related Documents
- Prospect Outreach Execution SOP - the daily loop, and the role boundary this document changes
- Prospecting Automated First Touch SOP - the email being replied to
- GHL Prospecting Outreach Cadence SOP - the cadence a reply stops, and the tag model
- Prospecting Objection Handling - the substance behind the harder replies
- Prospecting Outreach Email Templates - what was sent, and the signature rule
- Symphony Core Sales Pipeline SOP - where a booked prospect goes next
- Sales Development Onboarding SOP - how someone is cleared to answer replies at all
Document History
| Version | Date | Changes |
|---|---|---|
| 1.4 | 2026-11-09 | The sender check names First Email - Offer and Audit Only. A price question gets the Objection Handling line instead of "do not quote", because the offer email already states the $99 |
| 1.3 | 2026-11-04 | The sender check names Email 1A, 1B and 1C, which are signed by the Implementation Lead. Adds the case Email 1A invites: a reply proposing a better time to call |
| 1.2 | 2026-11-02 | Published to the team wiki, and the handover line stops assuming one sender. The caller now sends the audit herself after a call, from the C-021.Prospecting Send Marketing Audit snippet signed in her own name, so the instruction to open with a handover was wrong for half the replies she will answer. The section becomes a two-row check on whose name the audit went out in. The template's two names become placeholders, per reference-roles-strictly |
| 1.1 | 2026-09-23 | Records that sc-suppressed does not exist in the sub-account, so a remove-me request sets DND on the contact as well as creating the tag. A tag nothing reads is not a suppression |
| 1.0 | 2026-09-21 | Initial version. Written when reply handling moved from the Implementation Lead to an SDR, which required saying for the first time what a reply is answered with rather than only who answers it. Carries the handover line, because the first email is sent in one person's name and answered by another; eleven reply shapes with a tag each; and the line between what the SDR decides and what escalates |