Our Top Picks
“Connected” is a starting point, not a follow-up plan. The next rep still needs to know whether to call tomorrow, send the promised information or leave the person alone.
A call disposition is a label that summarizes the outcome of a call. A useful disposition list helps your team distinguish the phone result, the business outcome and the next action. Give every label a definition your reps can apply without guessing.
The worksheet below is for the manager setting those rules. It is not another place for reps to copy every call out of their CRM.
Want to see Trellus inside your CRM? Explore the HubSpot workflow and walkthrough before mapping your team's outcomes.
Three questions, not one overloaded dropdown
After a call, your team needs three answers:
- What happened to the call? No answer, voicemail, busy or another system-recorded result. A technical “completed” status does not, by itself, describe the conversation.
- What happened in the conversation? A callback was requested, a meeting was agreed, or the prospect said there was no fit.
- What should happen next? A particular person owns a specific action, with a time when one was agreed.
Your CRM may use different names for these fields. HubSpot, for example, lists call status, call outcome and call notes separately. Its call index also associates the activity with contacts, companies and deals. HubSpot's call-record guide shows those distinctions.
These are three questions to answer, not a requirement to create three new CRM fields. HubSpot's default call outcomes, for example, already include no answer, busy and connected. Map the worksheet to your existing fields and notes. Keep useful system results intact; let the selected outcome summarize the call and the note explain the commitment.
Copy this six-outcome template
Use these suggested labels to agree on what each outcome means and what follows it. Fill in the CRM location and responsible owner for your team. Map them to existing fields before adding new ones.
Callback requested
Use when: The person asks for another call—not simply when the rep wants another attempt.
Required context: Why you are returning; the agreed date, time and time zone.
Next action: Create the callback task with that context.
Owner and timing: Assigned rep __________; agreed callback __________.
CRM location: Outcome __________; note __________; task list __________.
Check: Another rep can find the commitment without asking the original caller.
Information requested
Use when: The person asks for specific material or an answer.
Required context: What was promised, where to send it and whether a follow-up was agreed.
Next action: Send the requested material; schedule a follow-up only when appropriate to the agreement and your team's contact rules.
Owner and timing: Person sending it __________; promised delivery __________.
CRM location: Outcome __________; note __________; delivery/task record __________.
Check: “Send me something” is not automatically counted as buying interest or a booked meeting.
Meeting agreed
Use when: The person agrees to meet.
Required context: Purpose, attendees and scheduling commitment.
Next action: Send the invitation or complete the agreed scheduling step.
Owner and timing: Meeting coordinator __________; next scheduling action due __________.
CRM location: Outcome __________; note __________; meeting record __________.
Check: Keep agreement, invitation sent, booking confirmed and meeting held distinguishable. A calendar entry alone does not establish a qualified opportunity.
Revisit later
Use when: A specific future event makes another conversation appropriate, such as a project milestone or contract review.
Required context: The trigger and whether the person agreed to another contact.
Next action: Record the trigger and the agreed next step; do not invent a callback date.
Owner and timing: Account owner __________; agreed date or review trigger __________.
CRM location: Outcome __________; note __________; reminder or account record __________.
Check: Use “callback requested” for an actual request to call again; use this label for the future circumstance that needs review.
Not a fit
Use when: A concrete mismatch makes the account unsuitable, such as an absent required capability or an incompatible workflow.
Required context: The factual reason and whether it applies to this contact or the whole account.
Next action: Route the record through your team's disqualification or data-review process.
Owner and timing: Account/data owner __________; review needed __________.
CRM location: Outcome __________; fit reason __________; contact/account __________.
Check: Reaching the wrong person is not enough to reject the entire account.
Not interested
Use when: The person declines without establishing a fit issue or agreeing to a later next step.
Required context: The stated reason, if offered. “Declined; no reason given” is better than a guess.
Next action: Apply your team's contact policy. A request not to be called again also needs the suppression process.
Owner and timing: Responsible rep or operations owner __________; required action __________.
CRM location: Outcome __________; note __________; suppression record when applicable __________.
Check: Selecting a disposition is not proof that a stop-calling request has been applied to the active calling list.
Keep phone results accurate alongside these definitions. “No answer” may follow the existing cadence; “wrong number” needs a phone-data correction. Neither means “not interested.”
For the broader measurement model, see sales call tracking. For the tradeoffs between a separate sheet and a connected call record, see our call-logging guide. This worksheet has the narrower job of making the labels and handoff consistent.
Make the note useful to someone who missed the call
A good handoff answers three questions: what did the person say, what did we agree, and who does what next?
For example:
The team reviews its calling setup next month. Morgan asked for the HubSpot workflow and requested a callback Tuesday at 2 p.m. Eastern. Dana will send the walkthrough today and owns the callback.
For this example, choose Callback requested. Put the promised HubSpot walkthrough in the note, and create the callback task for Dana at the agreed time. If a person asks for both information and a callback, the callback is the primary outcome; the note keeps the other promise visible. If they agree to a meeting instead, use Meeting agreed and track the scheduling step separately. Your team can adopt this rule when mapping the template to its existing fields.
The useful part is the structure: the reason, the promise and the owner. You do not need a transcript pasted into the task title.
Compare it with “Interested. Follow up.” The shorter note creates work for whoever reads it next. They have to reconstruct what happened before they can act.
If an automatic summary helps prepare the note, review the commitments and dates before saving it. An implied next step is not the same as one the prospect accepted.
Map the dictionary to your CRM before changing automation
Do not rename every option on a live team account at once. Start by writing the current field beside the proposed meaning. Include the reports and workflows that already depend on it.
In HubSpot, custom call and meeting outcomes have subscription and permission requirements. HubSpot's documentation also warns that a saved custom outcome cannot simply be edited afterward. Check the current custom-outcome instructions before making changes.
HighLevel distinguishes system-recorded Call Status from user-selected Custom Disposition. Its disposition guide explains how to use that selected outcome in follow-up workflows. Before attaching an automation, check which field your calling workflow actually updates.
The practical question is simple: after a rep selects the outcome in the calling tool, where does it appear in the CRM, and what happens next? Test the exact combination you will use.
Try five cases before asking the whole team to use it
Use approved test records, not real prospect outreach, to check the mapping:
- An unanswered attempt stays unanswered. It does not add a positive sales outcome.
- A callback request carries the agreed time and owner into the right task.
- An information request records the actual promised material, without being counted as a booked meeting.
- A not-fit conversation keeps its reason with the correct contact or account.
- A stop-calling request follows the team's suppression process and is not put back into the active calling list.
Have a second person read the saved records. Can they tell what happened and what they own? If they need the original rep to explain every entry, improve the definition or required note before adding more labels.
After a real call block, review a small sample together. Focus on disagreements: one rep chose “revisit later,” another chose “callback requested.” Clarify the rule using the conversation, not a target percentage. Once the labels are consistent, use the actual results in your next call-block plan.
Keep the follow-up beside the worklist
Trellus adds power and parallel dialing to supported sales-platform workflows. For HubSpot, use the integration guide to review the supported calling views, call logging and follow-up options for your setup.
Your reps can apply the agreed definitions while logging the calls they are already making. Available fields and actions depend on the platform and setup; use the integration directory to check yours.
Bring one real worklist and your current outcome labels to a HubSpot workflow demo. The question to answer is not how many dropdown options you can create. It is whether the next person knows what to do.
Power and parallel dialing in your CRM.
