1. First map the calls your office receives
Listen to a representative sample of existing calls before shopping. Label new service requests, existing-customer updates, reschedules, warranties, sales pitches and emergencies. Count the calls lost during fieldwork or overflow separately from calls your office handles well. Replacing a strong dispatcher is a different decision from rescuing unanswered inquiries.
A one-truck garage-door shop may need service-area screening and a callback task while repairing a spring. A restoration firm may need an on-call escalation path. A flooring showroom may need a measure appointment with a sales representative. One generic book-anything prompt cannot serve those three operating models safely.
Write a one-page boundary document: which jobs can be booked, which require human approval, which are declined, and what the agent may say about prices. If nobody can approve that document, you are not ready to automate the front desk.
2. Native agent or standalone answering tool?
A native agent can be attractive when it reads the same job types, capacity, and customer records as your existing system. ServiceTitan's current help documentation, for example, describes after-hours booking prerequisites including enabled skills, technician shifts, configured timeframes, and arrival windows. You still have to set those up, and the documentation does not prove that every account is ready.
A standalone service can spare you a platform change. You still need to test the connection. Ask whether it creates a confirmed job, a calendar event, or only a message, and whether the write happens right away. Then ask what happens when the integration times out. A sales demo that shows an email arriving has not booked the job.
Do not migrate your entire business-management platform solely to buy a pleasant phone voice. Ask the current provider which supported integration exists and test with a disposable job before buying.
| Decision | Native integration | Standalone service |
|---|---|---|
| Customer history | Potentially already connected; verify permissions | Needs explicit lookup and access controls |
| Booking | May use native capacity rules | Verify calendar writes and duplicate prevention |
| Failure path | Know the platform fallback | Require retries, alerts and manual recovery |
| Switching cost | Tied to the existing platform | Check number portability and data export |
3. Price the same call load across vendors
Do not compare a per-minute quote with an unlimited-looking headline. Goodcall's public page checked November 5, 2026 lists Starter at $79 for 100 unique customers, Growth at $129 for 500 and Scale at $299 for 2,000. The page describes unique customers as distinct phone numbers per month and lists respective overage rates of $0.79, $0.26 and $0.15. Confirm that public quote again before you buy, because plans change.
Worked billing example: 545 unique customer numbers on the advertised Growth plan would be $129 + 45 × $0.26 = $140.70 before any separate charges or taxes. Five calls from the same number would count differently from five new numbers under that definition. Confirm eligibility, integrations and contract terms directly before purchasing.
For a minute-metered alternative, request the same monthly caller mix, average duration, transfer time and spam treatment. Add setup, booking integrations, outbound texts, recording retention and human escalation. A lower subscription can be the more expensive system once every useful action is an add-on.
4. Specify exactly what a booking means
Write down the fields each trade has to collect before a booking counts. For plumbing, get the location, the problem, and how urgent it is. A planned water-heater quote may also need the fuel type and a photo request. For an electrical upgrade, book a site walk, and save any fixed price for after someone has seen the work. For tree service, you can request photos. Tell the caller to stay clear of power lines, and leave any close inspection to a qualified person.
A successful booking should have a unique job identifier, correct service family, customer contact, service location, arrival window and a clear confirmation. Do not tell a caller a technician is assigned if the system has only created an unassigned task. This distinction is especially important overnight.
Give the calendar duplicate protection. If a caller rings twice, or a timeout causes a retry, one request should take one appointment slot. Send an error alert, and keep a recovery queue that a person in the office owns, so the booking stays on the calendar.
- ☐ Document bookable services and excluded work
- ☐ Confirm ZIP coverage before offering an appointment
- ☐ Distinguish confirmed booking from callback request
- ☐ Block sold-out windows and incorrect technician skills
- ☐ Check duplicate creation after retries
- ☐ Make every failed CRM write visible to an owner
5. Safety escalation must beat the booking script
Keep the receptionist on intake for these calls. Gas odors, carbon monoxide alarms, electrical hazards, active sewage, and other urgent conditions follow the safety response your qualified team has approved. That response may send the caller to emergency services or the utility. Use a regular appointment only when the call fits a normal visit.
ServiceTitan's current escalation documentation is useful because it exposes a real design choice: a trigger can transfer, take a message or apply different after-hours behavior. Copying the concept does not mean every vendor supports it equally. Test it, including the case where the on-call number does not answer.
Let callers reach a human when they ask. A repeated request for a person should not turn into a loop of sales resistance. Avoid fake human names and answer honestly if the caller asks whether the voice is automated.
6. The 15-call acceptance test
Before forwarding live paid leads, run a written test set. Suggested scenarios: ordinary in-area repair; out-of-area caller; excluded service; fully booked day; existing warranty customer; repeat call; noisy line; interrupted speech; requested language change; human-transfer request; unanswered transfer; safety trigger; price request outside the approved range; integration outage; and a caller correcting their address mid-call.
Pass or fail each call on factual accuracy, the right disposition, and what lands in the CRM. How natural the voice sounds matters less than those three. Save the expected outcomes so a later prompt or integration update can be tested against the same cases.
A single safety-critical failure should block launch until corrected. For noncritical mistakes, name the owner and retest the scenario. Name the owner and retest the scenario. A promise that the model will improve over time does not clear the test.
7. A conservative ROI model that does not invent revenue
Illustrative example: an overflow pilot generates eight appointments you can establish would otherwise have been missed. Six complete, and contribution after direct job costs averages $150 each. That is $900 contribution before software and oversight. Subtract a hypothetical $200 monthly tool bill and $150 of review labor: $550 remains. These are assumed inputs for a worksheet. Keep them separate from any published LocalPro client result.
Do not count all agent-booked jobs as incremental. Some callers would have left a voicemail and booked later. Use a baseline, matched time windows or a controlled rollout to estimate true recovery. Also count cancellations, repeat truck visits and customer complaints.
The scorecard should include response speed, correct qualification, confirmed bookings, completed work, margin and human recovery time. If the office spends longer repairing records than it saved on calls, the pilot is not succeeding.
8. Roll out in stages and protect customer data
Start with overflow or a limited after-hours window. Leave the rest of the phone numbers on the current path until that window is stable. Keep routing reversible and maintain a human fallback. Review recordings or transcripts only when lawful and with appropriate notice and consent; recording rules differ across U.S. States.
Ask about storage location, retention, deletion, access controls and whether recordings are used for vendor training. Collect only intake details needed for the job. Do not request payment-card numbers or unnecessary sensitive information in ordinary transcripts.
Assign an operations owner for holiday schedules, dispatch fees and service-area changes. An agent with last month's availability is an automated source of broken promises. Keep holiday schedules, dispatch fees, and service areas current. A launch-day demo goes stale the week the holiday schedule changes.
9. Keep control of the phone number
Before signing, document who owns the advertised number, how forwarding can be reversed and what happens on cancellation. Test the fallback with the agent disconnected. Reliable intake should not require surrendering control of the number your customers already know.