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.
How it works
Common implementation structure
How this type of workflow is generally built, generalized across documented cases — not tied to any one vendor's stack. Click any stage to read what happens there. Specific products that implement these stages appear in “Tools commonly seen” below.
Stage 1 · Customer contacts via messaging
Customers initiate conversations in GoDaddy's messaging channels—SMS, WhatsApp, and web.
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.
What failed first
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.