October 20, 2026 · 6 min read
You pay for every call that rings your tracking numbers. Until now, Dispatch Scout could tell you which number rang, whether someone picked up, and how the call scored. This update fills in the rest: who on your team answered, what the caller needed, whether it booked, and how many invoiced dollars came back from each number.
Four pieces shipped together. Each one is useful alone. Together they answer the question every owner asks about marketing spend: which calls actually made money?
When a tracked call rings through to your team, Dispatch Scout now records which phone picked up. Each phone a call rings is matched to a team member by the mobile number on their profile, and the first one to answer gets the call. Inbound calls show Answered by with that person’s name on the Call Log row and on the call page.
A forward step in a call flow can also point at a specific team member now. It rings the mobile on their profile and falls back to the step’s number if they don’t have one.
If you run campaign numbers through CallRail, those calls get a name too, as long as your CallRail account routes calls to agents. The agent’s email is matched to a user in Dispatch Scout. If no one matches, the CallRail agent is still shown on the call.
Once you know who answered, you can count it. The new Rep Call Performance report lists every team member with these columns:
Filter by date, location, tracking number or team member, click a name to see only that person, and download a CSV. Answered calls with no team member named, such as a shared line or a call from before answer tracking, land in an Unattributed row so the totals still add up.
The report states its own limits right on the page. When a call forwards to a personal cell, Dispatch Scout only knows the cell picked up, so a cell’s own voicemail counts as answered. CallRail calls add to Answered and talk time but not to Offered or Answer Rate, because CallRail doesn’t report who else was rung.
Owners, admins and managers only. The people answering the phones are often the dispatchers and CSRs, so this report is limited to the roles that coach them.
On tracking numbers with AI call scoring turned on, the AI analysis on the call page now opens with a call summary. It answers what you’d ask the CSR if you walked over to their desk:
The Call Log and a lead’s Calls list show the reason, a booked badge and the next step under each call, so you can scan a morning of calls without opening any of them. The summary is for reading. It never changes a lead or job status on its own. Calls scored before this update look the same as they did.
Call counts tell you a number is ringing. Revenue per Tracking Number tells you whether it’s paying. For each number it shows Calls, First-time callers, Leads, Jobs, Invoiced, Paid and Invoiced / call, with totals at the bottom. Switch to By lead source to roll numbers up by source, and click any job count to see the jobs behind it.
Here is how the credit works:
Put that next to what you spend on each campaign and the conversation about your marketing budget gets short.
Revenue by source only works if every job has the right source on it. Every job needs a lead source that a person chooses, and Dispatch Scout no longer fills one in by default. On a new job, the Lead Source field starts on Select and stays required.
The one automatic signal is a tracked call. If the client called one of your tracking numbers in the last 7 days, and that number is mapped to an active lead source, the form suggests that source with a note: Suggested: this client called a tracking number for this source in the last 7 days. It’s a suggestion. Change it and your pick stays, even if you switch clients. No recent tracked call means no suggestion, and whoever books the job picks the source.
The iPhone app does the same on the create job screen, with a small From recent call caption while the suggested source is showing.
If you connect an AI assistant to Dispatch Scout over MCP, the same call data is there. list_calls lists inbound calls, answered and missed, with who answered and the summary fields. get_call returns one call’s detail and transcript. get_rep_call_stats returns the per team member numbers, limited to the same roles as the report. get_marketing_attribution can add invoiced and paid dollars per tracking number and lead source. When an assistant books a service call and no tracked call suggests a source, it asks the caller how they heard about you. See AI and automation for setup.
Included in the flat $40/user/month. Every feature is included, with no add-ons. Answered by, Rep Call Performance, the call summary, Revenue per Tracking Number and lead source suggestions are part of call tracking and marketing.
Owners, admins and managers. Dispatchers, CSRs and accounting, who are often the people answering the phones, do not see it.
Each job is credited to one inbound call: the earliest call linked to the job, its lead, or the same client, no more than 90 days before the job was created. Invoiced leaves out voided and No Charge invoices. Paid is net of refunds and leaves out deposits.
Yes. CallRail calls show who answered when your CallRail account routes calls to agents, matched to your team by the agent’s email. CallRail does not report who else was rung, so those calls add to Answered and talk time but not to Offered or Answer Rate.
No. Every job needs a lead source a person chooses. The only automatic signal is a tracked call: if the client called one of your tracking numbers in the last 7 days and that number is mapped to a lead source, the new job form suggests it and says why. You can change it. With no recent tracked call, the field stays on Select.
No. Every feature is included in the flat $40 per user per month. There are no add-ons.
See call tracking and attribution on the marketing feature page, or start a trial and open Revenue per Tracking Number on your own calls.
Marketing & leads Start Free TrialDispatch Scout is field service management software built for growing home service businesses. Scheduling, dispatch, invoicing, call tracking and payments in one platform, at one flat price of $40 per user per month.