Article
SDR Call Dispositions: Turn Outcomes Into Next Actions
prospectboss.com
Quoted on this wiki
Every place a page here uses this source, in the order the words come in it.
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
“SDR call dispositions should describe what happened on the call clearly enough to guide the next action.” 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.
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. “The examples are suggested operating labels, not a list of default fields in a particular platform.” Three separate questions: What happened on this call? Where does the lead stand overall? What should happen next?
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. “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.” 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.
Keep Call Results Separate From Lead Stages “A lead stage summarizes the broader relationship.” 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.
Keep Call Results Separate From Lead Stages “A task describes future work.” 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.
Keep Call Results Separate From Lead Stages “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.
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.” 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.
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. “Changing the overall stage to “no answer” would hide the ongoing evaluation.” 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.
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. “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.
“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.
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.” 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. “Record: Purpose, date or agreed timing, time zone when relevant, and owner.” A contact restriction deserves the organization’s designated handling process. Do not bury it in an optional note while leaving incompatible outreach tasks active.
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. “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.
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.” Start With a Small Set of Observable Outcomes
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.” 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.
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.” 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.
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. “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.