A practical records and review service
The starting point is your existing call reports, quote or job records, and payment evidence. We map what can be connected, identify what is missing, and agree on a small process for resolving the gaps. The deliverable is a useful measurement workflow and an agreed review, not automatic access to all your systems.
This service can include a field map, a reconciled sample, a tracker setup, outcome definitions, and a recurring review format. The records, period, tools, access, and ongoing responsibilities are agreed first. New phone numbers, telephony subscriptions, custom integrations, and automated dispatch are separate work if they are actually needed.
- One service request per inquiry ID; multiple call events can belong to it.
- Bookings, completion, and payment are confirmed separately.
- Unknown outcomes remain visible with a person responsible for checking them.
What evidence supports each step
A phone number can help locate records but is not a permanent unique job ID. One caller can request several jobs; several people can discuss one job. Ambiguous matches belong in a confirmation queue. We do not turn uncertain joins into confident revenue totals.
| Step | Evidence to seek |
|---|---|
| Inquiry | Provider call/event ID or a recorded request, with time and source evidence. |
| Suitable request | Service, location, equipment, and timing fit confirmed by the operator. |
| Quote and booking | Quote/job identifier and explicit acceptance or booking status. |
| Completed work | A confirmed job record rather than an assumption from call duration. |
| Collected money | Recorded payment, partial payment, or refund linked to that job. |
A callback is activity, not a second lead
This example can be reconciled exactly. Real records are often incomplete. Missing payment means unknown payment, not zero revenue. Quoted money never becomes collected money just because the job was booked.
| Record | How it is treated |
|---|---|
| 08:12 missed call; 08:17 callback | Two events linked to one inquiry after confirming they concern the same request. |
| $240 quoted; customer accepts | Quoted and booked, with payment still unknown. |
| Job marked complete | One completed job, even if collection is still unresolved. |
| $240 received; $40 refunded | $200 net collected; preserve the refund evidence. |
| $120 direct job cost | $80 contribution before marketing and fixed overhead. |
Make the weekly review small enough to keep
We distinguish the date an inquiry arrived from the date money was collected. A scheduled job may mature after the campaign week ends. Comparing one week's ad spend with all payments received that week can mix different cohorts.
Recorded attribution also has limits: it says which source was observed, not whether the job would have happened without advertising. Small samples, missing costs, and incomplete payment records limit the conclusions. The report should say where the evidence stops.
- Choose a defined inquiry period and record when outcomes were last checked.
- Resolve duplicate events and ambiguous inquiry-to-job matches.
- Confirm completion and collection with the person who holds the records.
- Review suitability, booked/completed counts, costs, and outstanding unknowns.
- Choose one change, one responsible person, and a date to check it.
Prepare a small, useful sample
Begin with a bounded period your team can actually review. Identify who can confirm job status and payment, what each system can export, and where private records may be handled. Use redacted examples for the first conversation. Do not upload real caller information into our public browser demonstration.
Our own tracker shows the definitions and an editable fictional example. It is a starting aid, not a live connection to Towbook, Autura, a bank, or your dispatch system. Any vendor-specific integration needs separate access, testing, and scope.