What Assembled learned by deploying its own voice AI in its support queue
Assembled's support operation relied heavily on tribal knowledge, and its knowledge base covered mainly the happy path — missing the edge-case documentation that AI requires to handle real customer queries consistently.
At a previous role, the support lead had over-focused on automating first-touch contacts without designing the broader workflow architecture, making the wider flow of work harder to manage. Early voice AI workflows at Assembled were also too rigid — structured like decision trees — causing the agent to keep asking for clarification even when the customer had already provided the needed context.
Assembled had its first agentic workflows live within a few weeks, with support agents shifting toward editing and fact-checking AI outputs rather than handling routine queries directly, and workflow ownership becoming part of the support role itself.
Frequently asked questions
What did this team achieve with this AI workflow?
Assembled had its first agentic workflows live within a few weeks, with support agents shifting toward editing and fact-checking AI outputs rather than handling routine queries directly, and workflow ownership becomin…
What tools did this team use?
AI voice agent.
What results were reported?
Time to first agentic workflows live: within a few weeks (source-reported, not independently verified).
What failed first in this deployment?
At a previous role, the support lead had over-focused on automating first-touch contacts without designing the broader workflow architecture, making the wider flow of work harder to manage.
How is this customer support AI workflow structured?
Customer calls support queue → Tier 1 vs complex routing → Voice AI handles Tier 1 query → Escalation to human agent → Workflow review and iteration.