How to Automate Support Without Losing Trust
Finding the right balance between efficiency and customer confidence as you introduce automation into support workflows.
DEAR STAGE 2: We want to automate a large portion of our support interactions to free up our team for higher-value work. But we are nervous about hurting the customer experience or losing trust. How do we determine the right level of automation and design the right off-ramp to a human? ~PRIORITIZING CSAT IN AN AI-WORLD
DEAR PRIORITIZING CSAT IN AN AI-WORLD: Every founder and support leader is feeling this tension right now.
You see the opportunity. Automate repetitive tickets. Free up your team. Reallocate headcount to strategic work. Improve margins.
But you also know one bad automated experience can undo months of goodwill with a customer.
We asked Mary-Beth Donovan, former Chief Customer Officer at EDB and Stage 2 LP, to share her take on how operators should think about automation without compromising trust. Her framing was simple and practical. There are three lenses to evaluate every automation decision: operational efficiency, customer experience, and product value.
Here is how to approach it thoughtfully.
Start with capacity, not cost savings
The cleanest use case for automation is not eliminating people. It is reallocating their time.
Mary-Beth emphasized that the first win most teams should chase is freeing up one full-time equivalent from low-value interactions. If AI can consistently handle repetitive, predictable questions, your team can move upstream into more proactive and strategic conversations.
This shift matters. Customers will tolerate automation if it leads to better human engagement where it counts.
Before setting an automation target, ask:
Which interactions are repetitive and rules-based?
Which conversations require judgment and context?
What higher-value work would we do if we reclaimed this time?
If automation does not unlock a better customer experience somewhere else, it is the wrong goal.
Trust and tolerance are the real metrics
Mary-Beth introduced a powerful framing around trust and tolerance.
“Customers will tolerate imperfection if they feel understood and steps of progress are being made. Tolerance is lost when customers feel stuck in a loop with no path forward and have no off-ramp to access the escalation path.”
You do not need 100 percent perfection to automate. In many environments, good enough is acceptable if you preserve trust. The danger is over-automation that traps customers in loops or prevents escalation when they need it.
Every automated workflow should clearly answer one question. When does a human step in? That moment should not feel hidden or punitive. It should feel seamless.
Practical guardrails include:
A clear path to escalate to a human
Monitoring negative feedback patterns
Regular review of cases that required escalation
Automation without a visible safety net erodes confidence quickly.
You cannot automate bad documentation
One of the most common surprises teams encounter is that their knowledge base is not ready for automation.Outdated documentation, inconsistent articles, or unclear processes will surface immediately once AI begins referencing them. Automation does not fix weak foundations. It amplifies them.
As an aside, I recently had a pretty funny intersection with an AI chatbot. I asked a “how to” question, and was immediately told it wasn’t possible. After playing around for 5 minutes, I found a way to do it and replied to that effect in the chat. The AI asked “can you walk me through how you did it so I can give better feedback to the next question?”. Rather than insisting I was wrong, I was surprised and delighted to see that the company had thoughtfully architected this moment for learning and growth.
Before increasing your automation rate, invest in tightening your knowledge base and documenting edge cases. The quality of your answers will determine whether customers view automation as helpful or frustrating.
This is often less about technology and more about discipline.
Set targets, and revisit them quarterly
There is no universal “right” automation percentage. The correct level depends on your customer base, complexity of product, and support model.
Mary-Beth cautions against chasing an arbitrary number like 80 percent automation without considering the downstream impact. Instead, set a goal tied to a clear business outcome. For example, freeing up capacity for proactive outreach or improving time to resolution on complex cases.
Then measure not only deflection rates, but also customer satisfaction and expansion indicators. If satisfaction drops or renewal conversations become harder, reassess.
Automation is not a one-time project. It is an evolving balance between efficiency and experience. When done well, it does not replace your team. It elevates them.
Until next week!