Post-call feedback that agents actually fill in: how to design your dispositions

Every manager wants the same three things from a call log: what happened, what was promised, and what to do next. Every agent has the same constraint: the next call is in ninety seconds. Feedback forms that ignore the second fact never deliver the first. The result is a CRM full of “Other” and blank notes, and a manager who does not trust the reports.

Dispositions — the one-tap outcomes an agent picks when a call ends — are the most important design decision in a calling CRM. Here is how to get them right.

Four principles

1. Ask at the moment the call ends, on the device the call happened on. A prompt on the phone the second the call disconnects gets answered; a form on a laptop at 6 pm does not.
2. One tap for the common case. The outcome list must cover 90% of calls with a single tap and no typing.
3. Every outcome implies a next step. If the CRM can pre-fill the follow-up time and move the stage from the outcome, the agent only confirms.
4. Questions only when they change what happens next. A “budget” question for a lead marked Not reachable is noise; the same question after Interested is gold.

Building the outcome list

Start from what actually happens on calls, not from the report you want. Pull the last hundred call notes and group them. You will usually find a handful of connected outcomes and a handful of not-connected ones.

Twelve to sixteen outcomes is the comfortable maximum on a phone screen. Group them under short headings so the eye lands on the right cluster. Names should be the words agents already say: “Send details” beats “Information request pending”.

Let the outcome do the paperwork

Each outcome carries defaults: a follow-up offset (“Send details” → 1 hour; “Call back later” → agent picks; “No answer” → retry in 3 hours), a stage move (“Visit booked” → Qualified; “Won” → Won), and whether it counts as connected for reports. The agent sees the pre-filled follow-up and changes it only when the customer named a time. This is how you get 95% of leads with a next action without asking anyone to remember.

Questions that earn their place

Custom questions are where forms bloat. Keep the rule strict: a question is attached to an outcome, not to every call, and it must be either a choice list, a number, a yes/no or a five-point rating. Free text is the note field, which is optional. Good examples: after Interested — budget range (choice), timeline (choice); after Not interested — reason (choice); after Visit booked — number of people attending (number).

Mark a question required only when a missing answer breaks a downstream process. Required fields that do not matter train agents to fill in the first option.

Notes: short, spoken, searchable

The best notes are one line in the agent’s own words — “wants 2BHK east-facing, husband decides, call Sat” — and they exist because the field appears at the right moment with a good hint. A hint like “What the next caller should know” produces better notes than “Remarks”. Notes belong on the lead timeline, in order, with the outcome and duration next to them, so the next person reading has the whole story.

Should feedback be mandatory?

Three settings are reasonable. Remind: the prompt appears and can be dismissed, and pending outcomes show as a count on the home screen. Block: the agent cannot start the next call until the last one has an outcome. Off: for roles where calls are not the job. Most teams start with Remind, look at the pending-outcome count for two weeks, and switch to Block only for agents who consistently skip it. Block is a stick; a good outcome list is the carrot, and the carrot usually suffices.

What good feedback makes possible

• Outcome mix per agent and per source: where the “Not interested” comes from, which channel produces visits.
• Connected rate by hour of day, so the team calls when people answer.
• Reason codes for lost leads that a product or pricing team can act on.
• A pipeline that is actually accurate, because stage moves happened at the moment of the call.