Call disposition codes for small businesses: a 10-code starter system

A call disposition code is a short label that records how a phone call ended: “Booked”, “Left voicemail”, “Needs callback”, “Wrong number”. Contact centres have used them for decades, but the idea is just as valuable for a Canadian small business with one phone line and a handful of staff: tag every call with its outcome for a month, and you will know exactly how many enquiries turned into revenue, how many are still waiting on you, and how many quietly slipped away. This guide gives you a ready-to-use 10-code list, a tracking method that needs nothing more than your existing call log and a spreadsheet, and an honest look at what to automate.

What a disposition code is, and what it isn't

Three different things get mixed up in call notes, and separating them is what makes the data useful:

• Call reason is why the person phoned: “price of a furnace tune-up”, “toothache”, “is my order ready”.
• Disposition is what happened by the end of the call: booked, quoted, promised a callback, went to voicemail.
• Quality is how well the call was handled. That's coaching material, not an outcome.

A disposition answers one question only: what happened? When reason, outcome and opinion get crammed into a single “notes” field, you can no longer count anything. Keep the reason as a two-or-three-word note in its own column, pick the disposition from a fixed list, and leave quality out of the log entirely.

Why a five-person business should bother

Because your phone is almost certainly leaking money, and without outcome tags the leak is invisible. Three numbers appear within a couple of weeks of consistent tagging:

• Your booking rate: the share of genuine enquiries that end in an appointment or sale. This is the single most useful number a service business can track from its phone.
• Your callback debt: calls tagged “needs callback” that are still open at the end of the week. These are people who wanted to give you money and are waiting.
• Your missed-call share: rings that no one answered and voicemails no one returned. For most small businesses this is the biggest and least visible bucket.

Here is a worked example using numbers you should replace with your own. Suppose a missed job is worth $300 to you, and your log shows that one “needs callback” per week is simply forgotten. That single un-returned call is roughly $15,600 a year walking out the door, found with a spreadsheet and five minutes a day. Your own job value and call volume will differ; the point is that the log turns a vague worry into a number you can act on.

A starter list: 10 codes that cover most small businesses

You do not need to invent a taxonomy. Start from this list, rename the labels to match how your business talks, and delete anything you will not act on. Every code earns its place by having a concrete next action. A code with no action attached is clutter.

Ten is not an arbitrary count. Common guidance in call-handling circles puts the practical ceiling at around 10 active codes per list, because past that point the person tagging starts guessing, and a guessed tag is worse than no tag. If two codes could describe the same call, merge them.

How to track outcomes without contact-centre software

You need exactly two things: a record that the call happened, and a place to write the outcome.

1. Source of truth: your phone system's call log (the history screen on a cell phone, the online portal for a business line, or the call list in a phone answering service). It already has the date, time, number and duration; you only add the outcome.
2. The log: a spreadsheet with six columns. Date, number, caller (if known), reason in two or three words, disposition from your fixed list, and next action with a due date.
3. The habit: tag at the end of each call or in one five-minute pass at the end of the day. Any longer and memory fills the gaps with fiction.
4. The review: fifteen minutes a week. Count calls per code, clear the open CALLBACK and QUOTE rows, and glance at MISSED. That column is your growth ceiling.

One rule of thumb keeps the whole system honest: if an “Other” or catch-all bucket grows past roughly 5% of your calls, don't let it swell: pull those rows, find the pattern, and either add one specific code or fold them into an existing one. Oversized catch-alls are the most common failure in outcome tracking, because they hide specific, fixable problems behind a generic label.

Keeping the list alive

Taxonomies decay. In a small business, governance is mercifully simple: one owner (probably you), and a monthly skim of the counts. Retire any code unused for two months. Split any code that has started meaning two different things. Resist the urge to add a code for every rare situation. Rare things can live in the reason column. The list should change a few times a year, not weekly, and every change should be announced to whoever else answers the phone before their next shift, not after.

Canadian wrinkles: two languages and callback rules

If you serve customers in both English and French, keep one code list and add a language column instead of duplicating codes per language. Within a few weeks you will know what share of your enquiries come in French and how their booking rate compares, which is exactly the evidence you need when deciding whether your front desk needs bilingual coverage.

On outbound calls: returning a call or a voicemail from someone who contacted you is a normal business callback. But if your follow-up starts to look like telemarketing (cold calls to prospects, promotional call campaigns), Canada's CRTC telemarketing rules and the National Do Not Call List apply, and commercial electronic follow-ups such as texts and emails fall under CASL. See the Government of Canada's guidance at fightspam.gc.ca. The rules differ by situation; this is not legal advice. A DNC code in your list (“asked not to be contacted”) is worth adding the day you start any outbound activity.

Common mistakes and quick fixes

• A growing catch-all bucket. Sample it, find the top missing outcome, add one specific code.
• Two codes for the same thing. Merge them and tell everyone who answers the phone before the next shift.
• Codes with no next action. Delete them. An outcome nobody acts on is trivia.
• Tagging from memory at week's end. Tag same-day or the data is fiction.
• Grading the call in the outcome field. “Handled badly” is not a disposition. Keep coaching out of the log.

Where AlmaTalk fits

The one disposition no spreadsheet can fix is MISSED: a call that rang out leaves you nothing to tag and nobody to call back. That gap is what AlmaTalk exists to close. It answers your line 24/7 in over 30 languages with automatic language detection (Canadian English and Quebecois French are the core pair), books appointments during the call into Google Calendar, Outlook or Cal.com, follows up by SMS and email, remembers returning callers, and transfers a caller to a human using the ranked backup numbers you set. Every call is recorded, and you receive a daily summary of what happened on your line. For a business of one to ten people, that does the job of a disposition report: who called, what they wanted, what got booked, with no one filling in a dropdown. Across a recent 90-day window, answered calls averaged 80 seconds across 2,639 calls.

To be clear about fit: AlmaTalk is not a contact-centre analytics suite, and if you run multi-queue campaign reporting you need different tooling. What it does is make sure the outcomes exist to be counted (answered, booked, followed up), starting at $97.97 CAD per month for 150 minutes, billed by the second, with no setup fee and no per-call fee. The fastest way to judge it is to phone the live demo line yourself: 1-888-775-9770.