ServiceTitan
Working your ServiceTitan aging report: a collections playbook
The short version
Treat your ServiceTitan aging report as a weekly work queue, not just a finance report. Nudge current-to-30 balances before they slip, get a firm commitment at 30 to 60, escalate and document at 60 to 90, and recover what you can past 90 before it gets written off. Write every result back to ServiceTitan.
Read the buckets as a work queue
Your ServiceTitan aging report already sorts every open balance into buckets: current, 1 to 30, 30 to 60, 60 to 90, and past 90. Most teams read it as a finance summary. The operators who collect well read it as a queue, where each bucket calls for a different move.
The goal is to catch balances early, get commitments in the middle, and recover hard in the late buckets before the money is gone.
Current to 30 days: a friendly nudge
This is the easiest money you will collect all month. The customer remembers the job and has no reason not to pay. A short reminder with the invoice number and amount, by text or email, clears most of these before they ever age.
Do not save these for a call. Automate the nudge and spend your human time further down the report.
30 to 60 days: get a commitment
Now it is worth a conversation. Call with the invoice context and ask for a specific payment date, or take the card on the spot. If they need a few days, that is fine, but get a date and log it as a promise-to-pay. A vague "soon" is how an invoice slides into the next bucket.
60 to 90 days: escalate and document
Balances in this window are starting to harden. Outreach gets firmer and more frequent, and documentation matters as much as the call. Note every attempt, every promise, and every response on the customer record. If the account ever goes to a collections step or a dispute, that paper trail is what protects you.
Past 90 days: recover before write-off
Here is the part most shops get wrong. Invoices past 90 days often just get written off. The team decides the money is gone and moves on.
A lot of it is still recoverable, but only with a focused push before the write-off. Treat the 60-to-90 window as your last clean shot, and run a deliberate recovery pass on anything that crosses 90 instead of letting it disappear.
Close the loop in ServiceTitan
Whatever happens on the account, write it back to ServiceTitan. Payment, partial payment, promise, dispute, no answer. The next person to touch the account should see exactly where it stands. When the aging report and the customer profile agree, the whole collections process gets faster and less stressful.
Running it without burning out the team
Working the full report this way, every week, across every brand, is a lot of repetitive contact. It is also exactly the kind of structured, rules-based work an AI agent can carry.
The same playbook runs automatically, by bucket: nudge the early balances, call the middle, escalate the late ones, capture promise-to-pay, and write it all back to ServiceTitan. Your team works the exceptions and the judgment calls, not the list. See how FrontDeskCollect works the aging report.
Frequently asked
How often should I run the aging report?+
Weekly. Monthly reviews let balances sit for weeks before anyone reaches out, and collectability drops fast after 60 days.
What happens to invoices past 90 days?+
In a lot of shops they quietly get written off. That is recoverable money walking out the door, which is why a focused push in the 60-to-90 window matters.
Does every balance need a phone call?+
No. Early balances often clear with a text or email. Save the calls for the balances that have aged or gone quiet, where a real conversation is what moves them.
See it run on your actual ServiceTitan data.
Book a demo
