Sales Systems 10 min read

Call Disposition: Sales Codes and CRM Follow-Up Rules

Learn what a call disposition means, which sales codes to use, and how to give each callback an owner, set a due time, and keep stop requests out of the queue.

A
RevOps Consultant & AI Automation Expert
Published 2026-11-22

A call disposition is a code that records the outcome of a single phone call. Use it to tell the sales team what happened and tell the CRM what to do next. A requested callback needs an owner and a due time. A do-not-call request needs a stop rule.

Table of contents

What a call disposition tells you

A call disposition answers a narrow question: what happened on this attempt? Dialpad’s definition includes outcomes such as “no answer” and “follow-up required.” Those labels let a manager read a call log without opening every note.

Suppose a buyer has a proposal and answers a call from the closer. The buyer asks for a call on Friday after a budget meeting. The call outcome is callback requested. The deal can stay at proposal sent. Nothing in the conversation says the buyer has accepted or declined the offer.

The call note has a separate job. “Ask about the budget meeting” gives the closer a useful opening on Friday. That sentence belongs in the note. The promised time belongs in a date field that can put work on the closer’s calendar.

Keep the disposition on the call record. A contact can have a missed call in the morning and a booked meeting that afternoon. If each new outcome replaces the last one on the contact, the morning attempt disappears from the history. A latest-outcome field can help a rep scan a queue, but keep the calls behind it.

Trestle’s outbound guide connects disposition codes to callback routing and list hygiene. That gives a manager a useful design test: pick a label, then name the decision it supports. “Wrong number” passes that test because someone can take the number out of the queue.

A call disposition worksheet for sales teams

Use this worksheet to give each sales call outcome a selection rule, a required detail, an owner, and a next action. It is a suggested CRM setup. Adapt the owner names and queue rules to your team before you put it in front of reps.

No answer

  • Select when: The attempt ends without an answer from a person. If your team tracks voicemail separately, use that code for a message left.
  • Required detail: Save the number dialed and the time of the attempt.
  • Owner: The rep assigned to the outreach queue.
  • Next action: Check the current call permissions and retry policy before placing the lead back in the queue.

No answer tells you nothing about buying intent. Leave the qualification field alone. Also leave the callback calendar alone: the buyer did not agree to a time. The queue owner can decide whether another attempt is due under the team’s contact policy.

Callback requested

  • Select when: The person asks the rep to call again.
  • Required detail: Record the agreed date, local time, and time zone. Flag any timing that still needs confirmation.
  • Owner: Name the person who will place the call.
  • Next action: Create a callback task for the agreed time. Keep the lead out of the general retry queue while that task is open.

Give the rep a short prompt: “When should I call, and which time zone is that?” If the buyer says “after lunch,” the rep can settle the detail while the buyer is still there. Do not turn a vague preference into a firm appointment the buyer never made.

Meeting booked

  • Select when: The buyer agrees to a slot and the booking exists on the calendar.
  • Required detail: Link the booking to the call. Include the meeting host.
  • Owner: The person responsible for the scheduled meeting.
  • Next action: Start meeting prep and send the approved booking confirmation.

A setter may finish the call with useful context for the closer. Put the buyer’s reason for taking the meeting in the handoff note. If the setter only sent a calendar link, record that fact without counting the lead as booked. The booking itself is the check.

Wrong number

  • Select when: The person who answers confirms the number does not reach the intended contact.
  • Required detail: Identify the exact number used on the call.
  • Owner: The person who maintains contact data for that account.
  • Next action: Remove that contact-number pairing from active dialing and send it for review.

Apply the correction to the phone field that caused the problem. A lead might have a valid office line and an incorrect mobile number. Closing the opportunity would hide a data issue inside a sales result. Dialing the same mobile number again would leave the issue unresolved.

Do not call

  • Select when: The person asks the team to stop calling.
  • Required detail: Record the request against the relevant number and contact under your approved policy.
  • Owner: The person responsible for the team’s call suppression list.
  • Next action: Block further calls within the scope of the request. Remove matching entries from active call queues.

Do not file a stop request as “not interested.” A buyer can decline an offer without asking to stop calls. When the person does ask to stop, the rep should not have to guess which sales stage will keep the number out of circulation.

How to set up call disposition rules

Build the rules around events your CRM can check and work your reps can own. ClearTouch’s guide to call disposition describes how a tag feeds reporting and future outreach. The setup below turns that idea into a checklist for a sales manager.

  1. Give each code a selection test. Write a sentence a rep can read at the end of a call. Include a common case that does not qualify. For “meeting booked,” the test is a confirmed slot, not a promise to check a calendar. The rep now has a clear basis for the choice.
  1. Decide who supplies each field. Let the dialer log an attempt time and any end state it can identify reliably. Ask the rep to record what the buyer requested. An answered line alone does not establish that the rep spoke with the intended person.
  1. Require the detail that drives the action. For a scheduled callback, require a due time and an owner before the task can enter the queue. Give unresolved timing its own review path. A blank date should not leave a callback sitting outside every work list.
  1. Choose an owner for exceptions. Decide who gets the work if the rep is absent or no longer owns the account. Give that person a queue they can see. If you share leads across setters, use a written rule for assigning the next sales action.
  1. Tie the task to its source call. Store the call reference on the task when the rule creates it. On a correction, find the existing task and update or cancel it. Saving the same record again should not give a rep another copy of the same job.
  1. Check stop rules at the point of dialing. Check the current suppression status when adding work to a queue. Check it again before a queued call goes out. That covers the case where a stop request arrives after tomorrow’s calls have already been assigned.
  1. Walk through the handoff before release. Use a sample contact and save a callback. Open the assigned rep’s work list, change the time, then inspect the task again. Repeat with a stop request and inspect the dialing queue. Judge the result by the work left behind, not the label on the screen.

For agencies, run these checks inside the relevant client account. A task can have a valid owner who lacks access to that client’s records. When planning your agency CRM setup, check access from the assigned rep’s view. An admin seeing the task does not settle that question.

What happens after the rep saves the code

Saving a disposition should leave a visible result: work assigned, a record sent for review, or a call blocked. Follow a callback and a stop request through the suggested setup to see what that means in practice.

A buyer asks for a Friday callback. The closer confirms the time and saves the outcome. The CRM creates the task against the call record. When the closer opens Friday’s list, the buyer’s name, number, and note about the budget meeting are there.

Now suppose the rep notices a time zone error. Fix the due time on the existing task and keep the original call reference. Check the rep’s calendar for the old slot. If the old reminder survives the edit, the buyer could still get a call at the wrong time.

A buyer asks the team to stop calling. The rep records the request, and the stop rule takes effect. There is no retry task. The useful check happens outside the call log: can a setter still pull that number from an open campaign?

Check pending work as well as new assignments. If the buyer had a callback on Friday, that task needs attention too. Preserve the earlier agreement in the history, but do not let it authorize another call after the stop request.

If a rep later questions a stop code, route the record to the person who handles suppression. Do not let an ordinary call-log edit restore dialing access. Use your approved policy to decide the scope of a request and who can change its status.

For teams that need this work installed, ClickToClose connects call outcomes with rep ownership and follow-up as part of its done-for-you follow-up operations. The worksheet here is a planning tool, not a description of a specific client installation.

How to audit call outcomes and follow-up

Audit the record on each side of the handoff. A complete call log tells you a rep selected a code. It does not tell you a callback reached the right person’s queue or a blocked number left the dialer.

Start with callbacks. Pull calls marked “callback requested” and match them to tasks by source call. Flag records with no task, no due time, or no active owner. Also flag open tasks that point to a call whose outcome has since changed.

Then inspect completed tasks. Ask what the rep actually did: placed the call, reassigned it, or closed the task by mistake? Keep the result of a new call on its own record. The original callback request should still tell you why the follow-up existed.

Check stop requests against actual queues. Match suppressed numbers to pending calls, including work assigned before the request. Check the number format used in each list. A space or country prefix should not conceal a match. Send conflicts to the suppression owner before the queue runs.

Name the unit in each report. For an attempt-level answer rate, divide answered attempts by all attempts in the reporting period. For lead reach, divide distinct leads reached by distinct leads attempted in that period. Define “reached” in writing, including whether someone other than the intended buyer counts.

Use the unit that answers the manager’s question. To plan rep workload, look at calls due. To find buyers still waiting for a promised callback, look at distinct buyers with overdue tasks. Repeated attempts at the same number should not create extra buyers in the report.

Review unclear labels with reps. Read a call note alongside the chosen code and the action it triggered. If the note says “sent the link” but the code says “meeting booked,” inspect the calendar. Use that example in your next sales coaching session to explain the selection test.

Call disposition FAQ

A useful call disposition identifies what happened and gives the next person a clear instruction. These questions cover the points that tend to need a written team rule.

How does a call disposition differ from a note or deal stage?

The disposition records the outcome of the call. The note holds context the next rep may need. The stage describes the state of the deal. A buyer can request a callback while the deal stays at proposal sent.

Which code fits a buyer who asks to talk tomorrow?

Use “callback requested.” Confirm a local time and time zone before ending the call. If the buyer cannot commit to a time, record that detail and assign the scheduling follow-up. Do not mark a sales meeting as booked without a booking.

Which outcomes can a dialer record on its own?

Use the dialer for events it can reliably detect, such as an unanswered attempt. Have the rep confirm outcomes that depend on what someone said. A connection signal does not tell you whether the buyer asked for a callback.

How can a manager find callbacks that nobody owns?

Start with calls marked “callback requested,” not the task list. Match each call to its task and inspect the owner field. Starting with tasks alone leaves out the exact failure you need to see: a logged request that never created work.

Does a wrong number mean the lead is lost?

No. It means the dialed number did not reach the intended person. Flag that number on the contact record and assign a data review. Keep the opportunity decision separate from the phone correction.

What should happen when a rep corrects a code?

Review the action created by the old code. Update or cancel pending work tied to the source call, and keep the correction history. If the change affects a stop request, keep the dialing block in place pending authorized review.

Book a Demo