Replacing the phone tree.
The case against touch-tone is easy. The question that actually stalls the project is how you get off it without breaking the line customers already have. This is that part.
01
Keep the number
Nothing about the published number changes. The line is re-pointed, so no customer has to learn anything, no printed bill becomes wrong, and no magnet on a fridge stops working. This is the single biggest reason IVR replacement is less disruptive than it sounds.
02
Decide what the agent owns on day one
Scope is a choice, not a limit. Balance, due date, usage, payments, arrangements, service start and stop, appointments and outage reports are the usual first set because they are the volume. Everything outside that scope goes to staff untouched rather than getting a partial answer.
03
Connect the system of record
The agent reads account state, balances, open cases and service history from the CIS directly rather than from a nightly export, so what a caller is told matches what a CSR sees. This is the step that takes integration work, and it is the step that decides whether the deployment is worth doing.
04
Keep the tree as the fallback, briefly
The existing menu does not have to be deleted on cutover day. Leaving it reachable while the agent takes the front of the line means the rollback is a routing change rather than a project.
05
Measure the right thing
Containment is the number everyone asks for, and alone it flatters. Watch time on hold, the share resolved end to end, and how many callers came back within a week, which is the one that catches a system closing calls it did not actually finish.
The one migration we can put numbers against is the City of Kingsport, which replaced its customer system and put Grace on the line in the same window rather than waiting for the new CIS to settle. Across its first month, covering a water outage, it handled 20,379 calls and resolved 60.3% end to end with no measurable time on hold.1
Common questions
What is the difference between an IVR and an AI agent?
An IVR is built around selection: the caller picks from a menu that lists departments, and the system routes them. An AI agent is built around conversation: the caller says what they need in their own words, and the agent identifies them, reads their account and completes the request. The menu stops being the thing the customer has to navigate.
Can an AI agent replace a utility IVR?
Yes, and for a legacy phone system that is usually the point. The agent takes over the line entirely: it answers, understands what the caller wants, identifies them, reads their account, and completes the request. If a utility is not ready to retire the old system, the agent can sit in front of it instead and take the calls it can finish.
Can we keep our published phone number?
Yes. The published number stays the same and the line is re-pointed behind it. Nothing printed on a bill or saved in a customer's phone becomes wrong, which is what makes IVR replacement far less disruptive than most system changes a utility runs.
Does this work with our existing phone system?
Yes. Grace connects to the telephony the utility already runs, alongside its CRM and customer systems, and the line is re-pointed rather than rebuilt. The systems that hold customer data stay exactly where they are.
What happens when a caller asks for a person?
They are transferred, with the context attached: who the caller is, what they asked and what was already checked. At the City of Kingsport the CSR receives a written summary and the full transcript, posted to the customer's account, so the caller never repeats their account number or their reason for calling.1
Can the agent verify a caller before transferring?
Yes. The number the caller rings from is matched against the account first, which at the City of Kingsport verified 67% of callers with nothing keyed in, and callers who do not match are taken through a challenge. The transfer then carries the verified identity, so staff do not ask again.1
How long does migration take?
Weeks, from kickoff to handling live volume, rather than a phased pilot. The integration with the system of record is the work; the telephony change is not. The City of Kingsport replaced a customer system it had run for roughly twenty years and put the agent on the line in the same window, rather than waiting a quarter for the new CIS to settle.1
Can we phase the rollout, or keep the old tree as a fallback?
Both. Scope can start with the high-volume requests and grow, with everything outside it going to staff untouched. The existing menu does not have to be deleted on cutover day either: leaving it reachable while the agent takes the front of the line means a rollback is a routing change rather than a project.
What does the agent do during an outage surge?
It answers every call at once. Grace runs hundreds of concurrent conversations, so the hundredth caller waits as long as the first. At the City of Kingsport the first month in production covered a water outage, and the line stayed answered on the first ring with no measurable time on hold; outage reporting was added during that outage without taking the agent off the line.1
What does it cost, and how is it priced?
Pricing scales with volume. What you run, how much of it you want handled and the call volume behind it shape a quote, and Dial AI comes back with a figure rather than a range. The pricing page has a calculator for estimating the saving on your own numbers first.
What happens to our call data?
It stays yours and stays where it is. Grace reads from and writes to the customer information system directly and keeps no shadow copy of customer data, each organisation's data is isolated from every other's, and every conversation is recorded so it can be reviewed afterwards. Dial AI is SOC 2 Type II and hosts on AWS in US and Canadian regions, with Canadian data residency available.2
What results has an IVR replacement produced?
At the City of Kingsport, across one month covering a water outage: 20,379 calls handled, 60.3% resolved end to end, an average call of 1:53 against a 4:00 CSR baseline, no measurable time on hold, and 67% of callers authenticated from the number they called on. Those figures are that deployment's first month, set out with their method on the case study.1
Ready to deliver faster, more consistent service?
See how Grace handles a real call on your systems: voice, chat, email and beyond.