Flag the accounts the phone agent should hand to a person
7 min read
By Lumina Software
- Voice reception
- Service business
- Operations
- Customer records
- Call handling
A plumbing company has a customer who still owes on three invoices from the summer. The office has called twice and sent a letter. On Tuesday night that customer calls the after-hours line, and the phone agent does exactly what it was set up to do: it finds an open slot on Wednesday morning, books a drain cleaning, and texts a confirmation.
Wednesday at 8, a tech pulls into the driveway. Nobody at the office knew the visit was on the board until the tech called in from the job.
The phone agent did not make a mistake. It booked a valid caller into a valid slot. What it did not know is that this account needed a person to talk to them first. Every service business has a handful of accounts like that, and most phone agents have no way to tell them apart from everyone else. This post covers how to mark those accounts and what the agent should do when one of them calls.
Which accounts need a person first
The list is usually short, but it is different for every shop. Here are the kinds of accounts that tend to belong on it:
- Past due balances. The office wants to talk about the money before anyone schedules more work. Some shops set a threshold, such as anything more than 60 days late.
- Safety notes. A dog that bites, a property where a tech was threatened, a house with a known gas or electrical hazard. These visits may need two techs, a manager's sign off, or a different plan.
- Open disputes. A customer who is unhappy about a recent job, has asked for a refund, or has left a complaint the owner is still handling. A cheerful automated booking can make that conversation worse.
- Commercial and contract accounts. A property manager or a business with its own approval process, purchase orders, or a dedicated contact at your company. Booking around that contact causes confusion on both sides.
- Warranty and callback jobs. A return visit for work you already did is often free, and the office wants to know before it goes on the schedule as a paid call.
- Accounts you have stopped serving. It happens. If the decision was made, the phone agent should not quietly reverse it at 10 p.m.
You do not need all of these. Pick the ones that have actually caused trouble in the last year and start there.
Put the flag where the agent can see it
The most common reason this goes wrong is that the information exists, but only in someone's head or in a free text note on the customer record. "Do NOT book, talk to Dana" typed into a notes field works for a person reading the screen. A phone agent that only checks name, address, and open slots will never see it.
The fix is a small, structured field on the customer or property record. It can be as simple as a single choice with a few values:
- None
- Needs office review before booking
- Needs manager approval
- Do not book
Add a short reason field next to it for the office, and an optional date for when the flag should be checked again. Then make sure the phone agent reads that field every time it finds a matching customer, before it offers any times.
If your scheduling software does not support a custom field, a tag or a separate list the agent can check works too. What matters is that the flag is something a system can read, not a sentence buried in a paragraph.
Decide what the agent says and does
Once the agent can see the flag, it needs a script for each value. The script should be polite, short, and should not reveal why the account is flagged. Telling a caller "your account is past due" on an automated line is a bad experience, and telling them "there is a safety note on your house" is worse.
A version that works for most flags:
"Thanks for calling. I've got your information, and I want to make sure the right person handles this. Someone from our office will call you back by 10 tomorrow morning. Is this the best number to reach you?"
Then the agent should:
- Take the same details it would take for any request: the problem, the address, timing, and access notes.
- Not book anything, and not promise a specific visit time.
- Send the office a message marked with the flag and the reason, so whoever reads it in the morning knows why it was held.
- Send the caller a short text confirming someone will call back, with the time window.
For a real emergency on a flagged account, decide ahead of time. A burst pipe at a house with a past due balance is still a burst pipe. Many shops choose to route that call to the on call person right away and sort out the balance later. Some do not. Either way, the decision should be written down so the agent is following your rule, not guessing.
Keep the list current
A flag that never comes off is almost as bad as no flag. The customer who paid their balance last month should not get a callback message for the rest of their life. The property with the aggressive dog may have new owners.
A few habits keep the list honest:
- Clear the flag when the reason is resolved. Make it part of the same step. When the payment posts, the flag comes off. When the dispute is closed, the flag comes off.
- Use the review date. If a flag has a date, someone looks at it on that date and either clears it or sets a new one.
- Check the whole list once a month. It should take a few minutes. If it takes longer, the list has grown past what the office can manage, and some of those flags probably do not need to be there.
- Limit who can add a flag. The office manager, the owner, and maybe a lead tech. If anyone can add one for any reason, the agent will end up sending half the calls to voicemail.
Test it before you trust it
Before you rely on this, run a few test calls. Set up a test customer record for each flag value, call the line from a number tied to that record, and listen to what happens:
- Does the agent find the record?
- Does it read the flag before offering times?
- Does the caller hear the right script, with no reason given?
- Does the office get a message that clearly says the call was held and why?
- Does an emergency on a flagged account go where you decided it should?
Then try the cases that tend to break things. Call from a different number than the one on file. Give the address slightly differently. Have a second person in the same household call. If the agent only matches on phone number, a flagged account can slip through the moment someone calls from their work phone.
After it goes live, include a few flagged calls in your regular review of real calls. They are rare, which means problems with them are easy to miss until a truck is already in the driveway.
Start with the one that hurt last
If this feels like a lot, start with the single case that caused the most trouble recently. For many shops, that is past due accounts. Add one field, one script, and one rule for emergencies. Test it with three calls. Then add the next flag when you need it.
The point is not to make the phone agent suspicious of callers. Almost everyone who calls should get booked quickly, without friction. The point is that the few accounts your office already treats differently get treated the same way at 10 p.m. as they would at 10 a.m.
Written by Lumina Software. Have a question? Book a call