AI-Powered Co-pilot System for Digital Sales Agents
wayfair · E-commerce · 2024 · source Agentic: no · promotional bias: med · source-backed · extracted with prompt 0.5.4 (schema v2)
Generated from extraction.json — do not edit by hand. Every claim cites verbatim source evidence; stated means the quote directly asserts the claim, implied means it supports it indirectly.
Problem
Domain: E-commerce digital sales support
Wayfair wanted to help digital sales agents answer customer chats faster and more consistently while keeping humans responsible for the final message sent to customers.
Constraints:
- agents need real-time product, policy, and conversation context
- generated responses must follow service guidelines
- hallucinated product or policy details would damage trust
- agents may edit or reject suggestions
- business impact depends on handle time, adoption, conversion, and quality
Architecture
Wayfair Agent Co-pilot constructs context-rich prompts from policy, product, and conversation data, generates recommended chat replies, keeps human sales agents in control, and monitors quality with metrics, feedback, logs, and a QA LLM.
Diagram confidence: reconstructed (reconstructed from prose).
flowchart LR digital-sales-chat-interface["Digital sales chat interface"] prompt-constructor["Prompt constructor"] llm-response-generator["LLM response generator"] recommendation-panel["Recommendation panel"] human-sales-agent["Human sales agent"] qa-llm["QA LLM"] quality-dashboard["Quality dashboard"] feedback-signals["Feedback signals"] digital-sales-chat-interface --> prompt-constructor prompt-constructor --> llm-response-generator llm-response-generator --> recommendation-panel recommendation-panel --> human-sales-agent human-sales-agent --> digital-sales-chat-interface human-sales-agent --> feedback-signals qa-llm --> quality-dashboard quality-dashboard --> feedback-signals feedback-signals --> prompt-constructor
Components
| Component | Role | Interacts with |
|---|---|---|
Digital sales chat interface |
Where human agents handle customer conversations. | Prompt constructor, Human sales agent |
Prompt constructor |
Assembles task description, guidelines, policies, product information, and conversation history. | LLM response generator |
LLM response generator |
Generates live recommended chat responses. | Recommendation panel |
Recommendation panel |
Shows suggested response text to the sales agent. | Human sales agent |
Human sales agent |
Accepts, edits, or rejects recommendations before customer delivery. | Digital sales chat interface, Feedback signals |
QA LLM |
Evaluates Co-pilot responses and supports quality monitoring. | Quality dashboard |
Quality dashboard |
Tracks instruction adherence, factual accuracy, handle time, conversion, adoption, and edit distance. | Feedback signals |
Feedback signals |
Drive prompt and retrieval improvements. | Prompt constructor |
Data flow
The prompt includes task description, guidelines, policies, product information, and conversation history; the LLM recommendation is then presented to the human sales agent for sending or editing.
Why this architecture
Quality monitoring is central because factual product or policy errors would undermine agent trust and customer service.
Models used: large language model · QA LLM
Scale
- Initial tests showed a 10% handle-time reduction, with additional tracking for conversion, adoption, and edit distance.“Initial test results of Co-pilot are very encouraging and show a 10% reduction in handle time, allowing our customers to be served more quickly.”article, stated“In addition to AHT, we are also tracking order conversion rate, adoption rate (both contact-level and response-level), and the edit distance between our recommended responses and the text sent by the agent”article, stated
- Initial tests showed a 10% handle-time reduction.“Initial test results of Co-pilot are very encouraging and show a 10% reduction in handle time, allowing our customers to be served more quickly.”article, stated
Alternatives considered (roads not taken)
Fully autonomous customer-facing sales AI
Rejected because: Wayfair keeps final message responsibility with sales agents while Co-pilot supplies live recommendations.
No independent quality monitor for generated responses
Rejected because: Wayfair uses a QA LLM plus logs and feedback to assess response quality.
Prompting without product, policy, and conversation context
Rejected because: The prompt explicitly assembles task, guideline, policy, product, and conversation-history sections.
Patterns
human-in-the-loop-gate (safety)
The LLM drafts response recommendations, but the sales agent decides whether to send or modify them.
prompt-chaining (orchestration)
The prompt is explicitly assembled from task, guideline, policy, product, and conversation-history sections.
llm-as-judge (evaluation)
A second LLM evaluates Co-pilot response quality alongside human feedback and conversation-log review.
eval-driven-development (evaluation)
Wayfair tracks instruction adherence, factuality, edit reasons, adoption, conversion, and handle time to refine the assistant.
Tradeoffs
How much autonomy to give customer-facing sales AI.
Chose copilot recommendations reviewed by agents over fully autonomous customer chat responses.
Rationale: Human agents preserve judgment and quality control while still getting speed and context benefits from AI.
How to measure whether the assistant is useful.
Chose business and behavior metrics together over only model-quality scores.
Rationale: Wayfair tracks handle time, conversion, adoption, and edit distance because value depends on workflow behavior as well as output quality.
Gotchas (what bit them)
Response quality failures have multiple forms.
Root cause: A suggestion can violate prompt instructions, include factual errors, miss product information, or require style edits.
Resolution: Track quality dimensions separately, including prompt instruction adherence, factuality, edit reasons, and message purpose.
Factual product and policy errors would undermine agent trust.
Root cause: Generated responses may hallucinate or misstate product information, policy details, or other customer-facing facts.
Resolution: Evaluate factuality and compare recommendations with product and policy data before relying on broad rollout.
Evaluation
Wayfair evaluates Co-pilot through AHT, conversion, adoption, edit distance, instruction adherence, factuality, edit reasons, message purpose, agent feedback, logs, and a QA LLM.
Metrics: 10% reduction in handle time in initial tests · average handle time · order conversion rate · contact-level and response-level adoption · edit distance between suggested and sent responses
Outcomes
- Initial Co-pilot tests reduced handle time by 10%.
- The system surfaced product, policy, and conversation context to agents.
- Wayfair identified future RAG improvements to enrich conversational context.
Company-authored engineering blog; results are initial and focused on AHT rather than long-term customer conversion.