GoDaddy Digital Care: 10 lessons learned operationalizing LLMs in customer support messaging
GoDaddy's Digital Care team handles over 60,000 customer contacts per day across messaging channels. Their initial mega-prompt AI assistant became unwieldy as prompts grew past 1,500 tokens, accuracy declined with each new instruction added, and LLMs proved slow and unreliable in production.
The mega-prompt caused the LLM to ask questions unrelated to the target topic. Users were sometimes stuck with a bot that refused to transfer them to a human agent. Early RAG implementations queried on every prompt invocation and retrieved irrelevant content before customer intent was established.
GoDaddy evolved to a multi-agent Controller-Delegate architecture, implemented deterministic guardrails for human transfers, and adopted intent-aware RAG with LLM Agents.
Early SPR experiments showed over 50% reduction in token usage.
Show all 8 reported metrics
Frequently asked questions
What did this team achieve with this AI workflow?
GoDaddy evolved to a multi-agent Controller-Delegate architecture, implemented deterministic guardrails for human transfers, and adopted intent-aware RAG with LLM Agents.
What tools did this team use?
ChatGPT 3.5 Turbo, ChatGPT 4.0, ChatGPT functions, RAG, SPRs.
What results were reported?
Daily customer contacts in messaging channels: over 60,000; Prompt size at second experiment launch: over 1500 tokens; Chat completion failure rate at model provider: 1%; invalid output rate on ChatGPT 3.5: 1% (source-reported, not independently verified).
What failed first in this deployment?
The mega-prompt caused the LLM to ask questions unrelated to the target topic.
How is this customer support AI workflow structured?
Customer contacts via messaging → AI classifies support topic → Guardrails check content → Intent-aware RAG retrieval → Topic-specific question collection → Route to support queue → Summary extracted for human Guide.