Grace is now handling inbound email for a Canadian energy company — the same agent, the same systems, the same guardrails as voice. Email is the channel where a backlog is invisible, which is exactly why it needed the help.
Grace has gone live on email for a Canadian energy company. Email joins voice, chat and SMS as a channel she handles, and it runs on the same agent that answers the phone — same integrations, same guardrails, same escalation rules.
Why email, and why it is harder than it looks
Voice gets the attention because the pain is audible. A queue has hold music, and everyone in the building knows when it is long.
Email has no hold music. A backlog of 400 unanswered messages makes no sound at all. Nobody hears it, the customer just doesn’t hear back, and the only signal that anything is wrong is the second email — usually a more frustrated one — arriving three days later. The channel where service quietly decays is the one nobody is watching.
It is also the channel with the least slack in it. A contact centre can flex staff onto phones during a storm or a billing cycle. Nobody flexes onto the inbox, so the inbox absorbs the delay. That is why email backlogs form after exactly the events that generate them, and why they persist for weeks after the calls have stopped.
And email is unforgiving in a way a call is not. A phone answer is spoken once and gone. A written answer is a durable artefact — it gets forwarded, quoted back, and attached to complaints. Getting it wrong in writing is worse than getting it wrong out loud, which is the real reason utilities have been slow to automate here.
What we are seeing
The deployment is deliberately conservative, and the interesting part is what Grace declines to touch.
A routing agent reads first. Every inbound message is classified before anything is drafted. If the request falls outside the flow’s scope, it goes to staff untouched — no partial answer, no attempt to be helpful at the edges. Restraint is the feature.
Threads that pre-date go-live stay with humans. An email conversation already in progress when Grace switched on is left alone. Picking up someone else’s half-finished thread is exactly where an agent produces a confident answer to a question it has not actually read.
Staff can turn her off per conversation. Not as a global kill switch buried in an admin panel, but per thread, in the moment, by the person handling it.
Escalation-risk detection shipped alongside it. The system watches for the signals that a conversation is deteriorating and surfaces it before the customer escalates it for you.
Where this goes
The point of running one agent across voice, chat, email and SMS is not channel coverage for its own sake. It is that the customer who called on Tuesday and emails on Thursday is the same person with the same problem, and should not have to explain it twice. Shared context across channels is the part that is hard to build and the part that customers actually notice.
Email is where that matters most, because email is where the history already lives.