SDR call dispositions should describe what happened on the call clearly enough to guide the next action. A label such as “good call” does not explain whether the representative reached the intended person, answered a question, or agreed on a callback.
This guide offers a practical way to define call outcomes for a sales development team. The examples are suggested operating labels, not a list of default fields in a particular platform. Adapt them to your campaign and test how they work in your actual setup.
Three separate questions: What happened on this call? Where does the lead stand overall? What should happen next?
Keep Call Results Separate From Lead Stages
A call result describes one attempt. A lead stage summarizes the broader relationship. A task describes future work. Treating all three as the same field can make the record misleading.
For example, a prospect can remain in an active evaluation while the latest call goes unanswered. Changing the overall stage to “no answer” would hide the ongoing evaluation. Similarly, marking a call “connected” does not explain whether the prospect asked for any further action.
Use the fields available in your system to preserve these distinctions. Where the interface combines some information, document a consistent convention so representatives interpret it the same way.
Start With a Small Set of Observable Outcomes
Choose labels that describe evidence rather than enthusiasm. A manageable initial list is easier to apply consistently than dozens of subtly different options.
- No live answer: No live conversation took place on that attempt.
- Wrong contact information: The record needs correction or review.
- Other person reached: Someone answered, but not the intended contact.
- Conversation completed: The intended person spoke with the representative.
- Technical issue: A problem prevented normal execution.
Then capture relevant conversation outcomes separately: information requested, callback agreed, meeting agreed, no current interest, or contact restriction raised. Your system may support structured fields, subcategories, or a defined note format.
Write Definitions With Boundaries
For each label, explain when it applies, when it does not, and what review or action follows. “Other person reached” should not automatically count as a conversation with the target buyer.
Illustrative definition:
Label: Callback agreed.
Use when: The prospect explicitly agrees to a return call.
Do not use when: The representative simply plans another attempt.
Record: Purpose, date or agreed timing, time zone when relevant, and owner.
Next step: Create the appropriate task after checking the current record and contact requirements.
A contact restriction deserves the organization’s designated handling process. Do not bury it in an optional note while leaving incompatible outreach tasks active.
Connect Each Outcome to an Appropriate Action
Not every result should create another call. A wrong number may require data review. A request for a document may require a response through an approved channel. A refusal may require closing the inquiry or applying contact controls.
Make the next action specific enough to execute. “Follow up” is less useful than “answer the prospect’s question about implementation scope.” Assign an owner and record any agreement accurately.
If dispositions trigger automations, test those rules with internal records. Do not assume a label pauses a sequence, creates a task, or updates another system unless you have verified that behavior.
Add a Short Note Where the Label Is Not Enough
A disposition helps sort activity; a note preserves context. Capture the relevant prospect statement, what remains unknown, and the agreed next step without copying unnecessary personal information.
Illustrative record:
Call result: Conversation completed.
Prospect request: Wants an explanation of setup responsibilities.
Lead stage: Reviewing fit; buying timeline unconfirmed.
Next action: Assigned representative to provide the approved explanation.
Scheduling: No meeting or callback agreed.
This is more useful than marking the lead “hot” and leaving the next person to infer what happened. It also avoids counting an information request as a meeting commitment.
Calibrate the Definitions Across the Team
Use fictional scenarios during training and ask representatives which labels they would select. Where answers differ, improve the definition rather than assuming everyone interpreted it incorrectly.
Review whether “other” or “unknown” is being used frequently. That can indicate missing categories, unclear instructions, or a need for better notes. Do not force representatives to choose a confident label when the outcome truly is uncertain.
Use Disposition Patterns to Investigate the Workflow
A rise in wrong-contact outcomes may justify a data review. Many conversations without a documented next action may prompt a process check. Treat patterns as starting points for investigation, not automatic proof of poor rep performance.
The ProspectBoss SDR Dialer page describes connecting calls, dispositions, notes, and next actions. The taxonomy here is an adaptable team standard, not a claim that the platform makes qualification or follow-up decisions automatically.
Frequently Asked Questions
What is an SDR call disposition?
A structured label describing a call’s outcome. It works best alongside relevant notes, the current lead stage, and any next action.
Is “no answer” a lead stage?
It is more useful as an attempt result. The broader lead relationship may remain unchanged.
How many dispositions should a team use?
Use enough to distinguish meaningful outcomes, but keep the set understandable. Add categories when a real operating need appears.
Should every disposition trigger a callback?
No. Match the action to the outcome and applicable contact procedures.
Can a disposition replace call notes?
Not when context matters. A concise note should explain the request or issue that the label cannot capture.
Keep SDR Conversations Connected to Next Actions
Explore how ProspectBoss brings calling, dispositions, CRM notes, and follow-up into one workflow.
