Every reactivation call ends with a decision nobody on the retention desk wants to make by hand: what just happened, and what happens next. AI call disposition automation makes that decision inside the call itself, so a dormant trader who says "call me after payday" becomes a scheduled callback, "stop calling me" becomes a suppression, and "how do I fund the account" becomes a task for an account manager, all before the line drops. At $0.35 per minute all-inclusive, the disposition adds nothing to the bill.
This guide covers the disposition list a brokerage campaign needs, how the AI agent decides which value applies, how to check it's right, and what each outcome should drive across retries, suppression, the CRM and the compliance record.
Key Takeaways
- A brokerage disposition list of eight to ten values covers deposit intent, callback, KYC blocked, not interested, do not call, handoff, no answer and wrong number.
- HubSpot ships six default call outcomes (Busy, Connected, Left live message, Left voicemail, No answer, Wrong number), so deposit and KYC dispositions must be created as custom outcomes.
- The FTC's Telemarketing Sales Rule bars calls to anyone who has said they don't want calls from the seller, so a "do not call" disposition has to suppress at once, not at the next import.
- FCA-regulated firms keep call recordings for five years, and up to seven on request, so the disposition should link to the recording rather than stand in for it.
- Topcalls prices calls at $0.35 per minute all-inclusive, and the disposition, summary and recording link ship with every call at no extra charge.
- A weekly review of 30 to 50 sampled calls per disposition catches a definition drifting before the drift skews the campaign report.
1. What is AI call disposition automation?
AI call disposition automation is the practice of having the calling system assign each call's outcome from the conversation itself, then act on that outcome without a human wrap-up step. For a brokerage campaign, the agent listens for deposit intent, a callback request, a KYC problem or a refusal, tags the call, and the tag drives the retry, the CRM update and the suppression list. No dropdown, no notes field, no Friday cleanup.
Compare that with a human call center. The agent hangs up, picks a value from a dropdown while the next number is already ringing, and types a note if there's time. The dropdown is where campaign data goes to die. A disposition is the one thing a campaign can't run without: retries key off it, the report keys off it, and the compliance desk keys off it.
An AI voice agent removes the gap between the conversation and the record because the same system that heard the trader writes the outcome. The trader confirms the callback window on the call. The agent doesn't have to remember it.
2. Why do manual dispositions fail brokerage campaigns?
Manual dispositions fail because they're recorded after the call, by a person who's already dialing the next number, from a list nobody agreed the meaning of. In a brokerage campaign that turns into three problems: retries that reach traders who asked to stop, deposit intent buried in free-text notes, and a campaign report that says "connected" and little else.
The catch-all is the first casualty. "Not interested" absorbs the trader who lost money and won't come back, the trader who moved to another broker, and the trader who said "not this week". Three different follow-ups, one value. The retention lead can't tell which segment is worth a second attempt, so the whole bucket gets retried or the whole bucket gets dropped.
Then there's the compliance gap. A do-not-call request typed into a notes field is a note, not a suppression. The number stays on the list, the next campaign imports the list, and the trader gets called again. The do-not-call handling guide for AI dialers walks through why that request has to land as a flag checked at dial time.
And the cost is real even when the data is right. Wrap-up time on a human team is unpaid talk time: every 30 seconds of after-call work on a three-minute call is a 17 percent tax on the agent's day.
The Brokerage CRM Integration Planning Checklist has a section on dispositions: a ten-value limit, a definition per value, a stage change and a follow-up per value, and an owner for the calls that fit none of them.
3. Which dispositions should a brokerage campaign use?

Eight to ten values, each with a one-line definition, one owner and one action. Fewer than that and "not interested" becomes a catch-all again. More than that and the retention team stops agreeing on the boundaries. The table below is the list most brokerage campaigns settle on for dormant trader, deposit follow-up and KYC reminder campaigns.
| Disposition | The trader says something like | What the outcome drives | Retry? |
|---|---|---|---|
| Deposit intent | "How do I add funds?", "I'll top up next week" | Task to account manager, cashier link by SMS | No, handoff |
| Callback requested | "Call me Thursday after six" | Next call scheduled inside the window | Once, in window |
| KYC blocked | "My documents got rejected" | KYC status flag, upload link by email | After documents |
| Not interested | "I moved to another broker", "I lost too much" | Reason captured, 90-day exclusion | No |
| Do not call | "Stop calling me", "Remove my number" | Suppression on every list | Never |
| Handoff to human | Complaint, pricing dispute, unresolved objection | Warm transfer or urgent task | No |
| No answer or voicemail | Nothing said | Attempt count, cadence retry | Capped attempts |
| Wrong number | "Never had an account here" | Contact flagged, list hygiene queue | No |
The CRM won't have these out of the box. HubSpot's calls API ships six default call outcomes: Busy, Connected, Left live message, Left voicemail, No answer and Wrong number, each stored as a GUID, and custom outcomes get their own GUIDs once an admin creates them. Deposit intent and KYC blocked are custom values on every CRM a broker runs. The call outcome to CRM update guide covers the field mapping in detail.
Two values deserve a note. "Handoff to human" is a disposition, not a failure. And "wrong number" on a dormant list usually means the trader changed phones years ago, so route the record to list hygiene rather than retrying.
4. How does the AI agent decide the disposition?
The agent decides from two sources at once: call events and conversation content. Telephony events settle the easy ones, so no answer, busy and voicemail detection need no interpretation. Conversation content settles the rest. The agent's instructions define what counts as deposit intent, a callback, a refusal or a do-not-call request, and the agent tags the call against those definitions while the trader is still on the line.
Precedence matters more than people expect. A trader can say "I might top up next month, but stop calling me" in one breath. Do-not-call beats everything. Handoff beats deposit intent. A callback with a stated window beats a vague "maybe later". Write the order down, because the agent applies whatever order it was given, and a missing rule becomes a wrong tag.
Confirmation is the part manual dispositions never had. With sub-500ms response latency, a Topcalls agent can close the loop inside the conversation: "So I'll call you Thursday after six, is that right?" The trader confirms the outcome. The disposition is stated by the person it concerns, not inferred from a transcript afterwards.
Language is the other trap. Topcalls runs campaigns in 32 languages, and a refusal in Portuguese or a callback window in Arabic has to hit the same definition as its English version. Define dispositions by intent, not by phrase, and test each one in every language the list contains. For the rules on when the agent should stop and pass the call to a person, see when an AI call should hand off to a human.
When a call fits no definition, the right disposition is "needs review", not a forced guess. A small review bucket is a feature. A large one means the list needs a value nobody wrote down.
5. How do you check disposition accuracy?
Sample and score. Pull 30 to 50 calls per disposition each week, have someone on the retention desk read the transcript or play the recording, and mark agree or disagree. Track disagreement per value. A disposition that's wrong more than one call in ten needs a clearer definition or a split into two values, not a better model. Most errors are definition errors wearing a technology costume.
Watch the confusion pairs. "Not interested" versus a soft callback is the usual one: "not right now" belongs to callback if the trader gave any hint of timing. KYC blocked versus deposit intent is the other: a trader who wants to fund but can't pass verification is a KYC case first, and the task should go to onboarding, not to sales.
Keep the recording attached. FCA SYSC 10A requires firms to take all reasonable steps to record telephone conversations relating to financial instruments and to keep them for five years, and up to seven where the FCA asks. The disposition should carry the recording link, so the reviewer and the compliance desk are looking at the same call. Topcalls includes recording and transcription in the $0.35 per minute price, so there's no separate archive to reconcile.
The accuracy review feeds the campaign report, and the report is only as honest as the dispositions behind it. The call quality metrics brokerage teams should track covers what to measure once the outcomes are trustworthy, and the real-time analytics view shows disposition counts per campaign as the calls complete.
6. What should an automated disposition trigger?
Four things, in a fixed order: suppression first, then the CRM write, then the follow-up, then the report. A do-not-call disposition lands on every list before anything else runs. The CRM receives the disposition with the summary, the recording link and whatever the agent captured. The follow-up fires from the CRM rule or the campaign cadence. The report counts the disposition, not "connected".
Suppression goes first for a legal reason. The FTC's Telemarketing Sales Rule, 16 CFR 310.4, prohibits calling a person who "previously has stated that he or she does not wish to receive an outbound telephone call made by or on behalf of the seller". A request that sits in a queue until the nightly sync is a request the next campaign can miss. Topcalls' compliance posture covers TCPA, TSR, DNC and GDPR, and the do-not-call flag should be a write-once value that never reverts.
Retries are where dispositions earn their keep. "No answer" retries on the cadence with a capped attempt count. "Callback requested" retries once, inside the window the trader gave. "Deposit intent" never retries, because the next touch is a person with a cashier link. The failed calls, retries and campaign recovery guide covers what to do when a whole batch fails rather than a single call.
The CRM and follow-up path runs through Integrations: native connectors for HubSpot, Salesforce and Pipedrive, webhooks on call events, and 5,000+ tool connections through the automation path for the SMS, email and ticketing steps. A dormant trader reactivation campaign that fires the cashier link within a minute of "deposit intent" is the whole point of the exercise. And the report is what the ops lead watches while the campaign runs; how to monitor an AI calling campaign in real time covers what a healthy disposition mix looks like hour by hour.

7. What does AI call disposition automation cost?
With Topcalls, nothing beyond the minutes. $0.35 per minute all-inclusive covers the voice model, telephony, recording, transcription and analytics, with no per-seat, setup, bundle or add-on fees. A three-minute reactivation call costs $1.05 and arrives with its disposition, summary and recording link already written. The saving sits on the human side: no wrap-up time, no dropdown, no weekly cleanup of the "not interested" bucket.
Scale is the second half of the cost story. Topcalls processes 63,000+ AI calls a day across its customers, and at that volume there is no version of manual dispositioning that keeps up. A human team on AI dialing typically lifts call volume 3 to 10 times, and every one of those extra calls needs an outcome nobody has time to type.
To put a number on the dormant book itself, the dormant trader revenue calculator takes your inactive account count, average deposit and expected reactivation rate and shows what a campaign is worth before the first call. If the figure justifies a pilot, book a 30-minute call; Topcalls returns a proposal within 48 hours of the strategy call.
8. When doesn't disposition automation fit?
Disposition automation doesn't fit when the campaign has one outcome, when a human needs to own the classification, or when nothing downstream reads the tag. In each case the automation runs fine and changes nothing, which is the expensive kind of success. Check the fit before building the list.
- Single-outcome campaigns. A regulatory notice call has two results, delivered or not delivered, and telephony events already capture both. Building a ten-value list for a two-value campaign is busywork.
- Complaint-led lists. If most conversations on a list are complaints or disputes, the honest disposition is "handoff" almost every time, and the campaign should start with a person rather than route to one.
- Regulated classification. Where a regulator's rules define what counts as a complaint or a vulnerable customer, the AI agent can flag the call, but a trained person makes the classification and owns the record.
- No system of record. A disposition that lands in a spreadsheet nobody opens is a note with better formatting. Get the CRM or the list tool in place first.
- Very small volume. Under a few hundred calls a month, a human wrap-up with a shared ten-value list works, and the team will feel the drift themselves.
9. How do you get disposition automation live in two weeks?
Agree the list, map it, build the definitions into the agent, test with your own numbers, then pilot with daily review. Topcalls takes about 15 minutes for first setup and gets live campaigns running within about two weeks; the disposition work is what fills those two weeks, and most of it is decisions rather than configuration.
- Days 1 to 2: retention lead and compliance desk agree the eight to ten values, one definition each, and the precedence order.
- Days 3 to 5: the CRM admin creates the custom outcomes and maps each value to a field change and a follow-up, using the planning checklist.
- Days 6 to 8: the agent instructions get the definitions and the confirmation phrases, in every language on the list.
- Days 9 to 10: ten internal test contacts, one per disposition, with the team's own phones. Time the do-not-call suppression from the words "stop calling" to the flag landing everywhere.
- Days 11 to 14: a small live list, a daily 30-call review, and a definition rewrite for whichever value disagrees most.
The Brokerage CRM Integration Planning Checklist covers the mapping half of that plan: owners, field mapping, dispositions, triggers, sync direction, webhooks, testing and data access, in a form your CRM admin can build against.
The disposition is the smallest piece of data in a campaign and the one everything else depends on. Get the list right and the rest of the automation is plumbing.
Frequently Asked Questions
Get AI calling tips in your inbox
No spam. One email per week with actionable sales automation tips.






