Sales Development Onboarding SOP
Overview
- What: take a new Sales Development Representative from no access to answering prospect replies unsupervised.
- When: a new SDR joins, or replaces one. Run by the Implementation Lead.
- Who: Implementation Lead provisions, supervises and clears. SDR reads, shadows, demonstrates.
- Time Required: about a day of setup, then two weeks of supervised work.
Prospecting already has seven documents and six SOPs. None of them is an order to read them in, and none says when someone is allowed to answer a live prospect. This is that document.
Prerequisites
Implementation Lead, before day one. The SDR starts none of this until all four are done.
- Signed NDA. No access of any kind before it, including read-only.
- The compensation and engagement terms are settled and in the contract. An SDR paid partly on booked meetings cannot be onboarded against an open question.
- A sending identity exists for the SDR — their own name and address, not a shared mailbox and not the Implementation Lead's.
- A calendar the SDR can book into, with availability, timezone and buffers already set.
Procedure
Phase 1 — Access (Implementation Lead, before day one)
Grant only these, and confirm each one loads before the SDR starts reading.
| System | Scope |
|---|---|
| Sub-account | Contacts and Conversations only. Not Settings, not Billing, not Workflows, not Payments |
| Calendar | Booking access to the discovery calendar |
| Slack | Prospecting channel and direct messages |
| Drive | Read on the prospecting folder. No client delivery folders |
| 1Password | Only if a credential is genuinely needed. Usually none is |
The client-data problem, and what to do about it. Symphony Core's own clients live in the same sub-account as its prospects. A Contacts grant therefore exposes client records, their conversations and their invoices. Before granting:
- Walk the contact list with the SDR and say plainly which records are clients and that they are out of scope.
- Set the SDR's default view to a smart list filtered to prospecting contacts, so the client records are not the first thing they see.
- Record the grant, and its scope, where the access grant is logged.
⚠️ GHL's permission model does not cleanly separate prospects from clients inside one sub-account. Until it does, this is a stated boundary rather than an enforced one, and it belongs in the contract as well as in this document.
Phase 2 — Reading, in this order (SDR, days one to three)
Ordered so that each document answers a question raised by the one before it. Stop and ask rather than skipping.
Day 1 — what the business sells, and to whom
- SC Goals — what the company is trying to do
- Prospecting Bucket Taxonomy — the five problems SC leads with
- Prospecting Outreach Email Templates — what the prospect actually received
Day 2 — the motion 4. GHL Prospecting Outreach Cadence SOP — the cadence and the tag model 5. Prospecting Automated First Touch SOP — what the machine does without anyone 6. Prospect Reply Handling SOP — the job itself 7. Prospecting Objection Handling
Day 3 — the limits 8. SC Outbound Calling Compliance Standard — certification required, see below 9. GHL Prospecting Audit Accuracy SOP — what the report can and cannot be trusted for 10. Team Ways of Working
Compliance certification is a gate, not a reading item. Before the SDR touches a phone or names a state, they answer these without notes:
- Which three states are never called, and why is New York not one of them?
- What are the calling hours in Connecticut?
- Is recording a call one-party or all-party consent in Connecticut and Massachusetts, who tells the prospect it is recorded, and when must the caller say it themselves?
- May an AI voice place a call?
A wrong answer is re-read, not a discussion. The exposure here is regulatory and it lands on the company, not the individual.
Phase 3 — Supervised (days four to fourteen)
The SDR does the work; the Implementation Lead reads every outbound message before it sends. Ten-minute end-of-day debrief while this lasts.
Checkpoint 1 — first booked call. The SDR answers an interested reply end to end and puts a call on the calendar. Pass: handover line present and in their own name · two concrete times offered · no price discussed · tagged · cadence cancelled · a one-line note on the record.
Checkpoint 2 — first difficult reply. A price question, a hostile reply, or a remove-me. Pass: the right one of escalate / suppress / answer was chosen · nothing commercial was invented · a suppression, if any, went on immediately and was not argued with.
Checkpoint 3 — substitutability. By day fourteen, for any step in the loop, the SDR can answer "which document tells me how to do this?" and name the right one.
This is the delegation test. If they ask a person instead of finding the document, either the documents are incomplete — record the gap — or the reading was not grounded. Both are fixable; neither is the SDR's fault.
Phase 4 — Solo
Cleared when all three checkpoints pass, the compliance questions are answered clean, and five consecutive replies needed no correction before sending.
After that: weekly review per the Reply Handling SOP, and the first month's replies are read in batch rather than in advance.
Phase 5 — Continuity and offboarding
While they are here. Every prospect state lives on the record — tag, note, next step — not in the SDR's head. A prospect mid-conversation must be pickup-able by anyone reading the record alone. Test this once by having someone else take a live thread cold.
When they leave. All access revoked within 24 hours. Open conversations reassigned before the last day, not after. Any prospect expecting a call from them is told a different person will make it, by name.
Verification
- The SDR names the correct document for any step, unprompted, by day fourteen.
- Five consecutive replies sent without correction.
- Compliance questions answered clean, recorded with the date.
- Access matches Phase 1 exactly — no Settings, no Billing, no Workflows. Re-check at thirty days; scope creeps.
- A live thread was picked up cold by someone else and nothing was lost.
Related Documents
- Prospect Reply Handling SOP - the job this onboards into
- Prospect Outreach Execution SOP - the daily loop and the role boundary
- Prospecting Automated First Touch SOP - the tagging pass
- SC Outbound Calling Compliance Standard - the certification gate
- Support Operator Onboarding SOP - the pattern this follows
- Team Member Onboarding Checklist - the company-wide steps that run alongside
- Access Revocation Checklist - Phase 5
Document History
| Version | Date | Changes |
|---|---|---|
| 1.0 | 2026-09-21 | Initial version, written when prospecting replies moved to an SDR. Follows the Support Operator Onboarding shape: access, then ordered reading, then supervised work with named checkpoints, then solo. Adds two things that role did not need — a compliance certification gate before any call, and an explicit boundary around client records, which share a sub-account with prospects and are exposed by the same Contacts grant |
| 1.2 | 2026-10-26 | Published to the internal wiki. The compliance certification gate in Phase 2 is the only copy of the four questions a caller answers before dialling, and it was unreachable by the people who have to answer them |
| 1.1 | 2026-09-25 | Compliance certification questions updated for the four-state posture and the recorder-start rule |