Ticket Deflection: How to Do It Without Losing Sales

Ticket deflection reduces support tickets by answering shoppers’ questions through self-service or an AI agent. Start with questions you can resolve reliably, keep a visible route to a person and measure whether shoppers need help again.

If your team has a ticket reduction target, protect the buying journey as you work towards it. A shopper who leaves with an unanswered sizing question can reduce ticket volume while also taking a sale elsewhere.

What Ticket Deflection Means

Ticket deflection means a support question is resolved without becoming a ticket for your team. A delivery policy, product guide or automated answer can do that when it gives the shopper enough information to act.

Consider two cases. Successful deflection answers whether a dress can arrive before an event, using the shopper’s location and your delivery rules. Failed deflection hides the contact button after showing a generic delivery page. The second shopper still needs an answer.

Count a resolved need only when you have evidence of resolution. A shopper confirming that an answer helped is stronger evidence than a page view. Silence alone leaves the outcome uncertain.

Containment Rate and How to Read It

Containment rate measures how many automated conversations end without a transfer to a person. Intercom’s Fin glossary defines it as the “percentage of conversations that a chatbot, IVR, or AI agent handles without transferring the customer to a human agent”.

That definition measures handover, not whether the answer worked. A shopper who closes a confusing chat can count as contained. Keep confirmed resolutions, handovers and unknown outcomes separate.

Use the following formulas with a defined cohort and reporting period. Here, a tracked support need is one distinct question or issue, counted once across channels.

Metric	Formula	What it tells you
Containment rate	Automated conversations with no human transfer / all automated conversations x 100	How much chat volume stays within automation
Deflection rate	Tracked support needs resolved through self-service without a staff ticket / all tracked support needs x 100	How much measured demand is resolved before staff need a ticket

In a hypothetical cohort of 100 tracked support needs, 30 are resolved through self-service and 70 need staff tickets. The deflection rate is 30%. Within that cohort, suppose an AI agent handles 50 conversations and transfers 15. Its containment rate is 35 / 50 x 100, or 70%.

These percentages use different denominators. They aren’t interchangeable, and help centre visits don’t establish the number of support needs resolved. If your tool labels a different calculation “deflection”, document that calculation before comparing reports.

Where Deflection Works and Where It Hurts

Self-service works best when a question has a clear answer your store can supply. Start with routine requests that have reliable source information.

• Order status needs an authorised lookup that returns the relevant order’s latest status.
• Sizing questions need the product’s measurements, size chart and any stated fit guidance.
• Delivery timing needs the destination, dispatch rules and delivery estimate for the available service.
• Returns-policy questions need eligibility conditions and the steps the shopper can take.

Keep complaints and faulty-goods cases easy to pass to staff. An agent can collect the order reference and explain the next step. A repeated policy answer doesn’t resolve a disputed decision or a customer’s request for a person.

Route an uncertain product question to staff before the shopper commits to a purchase. For example, if the catalogue doesn’t establish whether a spare part fits a particular model, the agent must avoid guessing.

Building Answers That Resolve Questions

Combine accurate policy pages, a searchable help centre and an AI agent with order lookup. Each source closes a different gap: policies explain your rules, while order data answers what happened to a specific purchase.

Before automating, assign someone to maintain the source material and someone to receive handovers. Confirm that the agent can retrieve only the order details the shopper is entitled to see.

1. Group recent tickets by the question shoppers need answered. Choose a routine group with clear information and a repeatable next step.
2. Write the answer with its conditions. A delivery answer must distinguish dispatch time from transit time and explain what changes by destination.
3. Connect the agent to the relevant documents and order lookup. Remove conflicting old policy versions from its answer sources.
4. Try the question with complete and incomplete details. Check that the agent asks for missing information and passes unsupported questions to a person.
5. Run a small rollout and inspect the outcomes. A successful conversation gives a correct answer or reaches staff with the information already collected.

If the agent keeps sending the same article, inspect whether the article answers the shopper’s actual question. Add the missing condition or connect the required lookup. If it gives contradictory answers, compare the source documents before adding more material. The AI knowledge base guide explains how to organise the information agents use.

Handing Over to a Person

A handover must pass the conversation history and the shopper’s unresolved question to the person taking over. Include the order reference when available, the information already checked and any action the agent attempted.

Keep the request for a person visible throughout the conversation. When staff are offline, explain how the shopper can leave the question and where the reply will arrive. Show the expected response time your team can meet.

Test the handover from both sides. The shopper must receive confirmation that the request reached staff. The receiving staff member must be able to continue from the history without asking the shopper to start again. Use the ticket escalation guide to define who receives cases that need specialist help.

Tracking Deflection Honestly

Pair containment with repeat contact rate and satisfaction for automated conversations. Review results by question type so strong delivery answers don’t conceal poor complaint handling.

Choose a repeat-contact window that fits the issue, such as seven days for a routine delivery question. Divide shoppers who contact you again about that issue by the shoppers whose automated conversations ended in the measured cohort. Include email and phone follow-ups when you can match them reliably.

Ask for satisfaction after automated conversations, then report the response rate beside the score. A high score from a small responding group can miss shoppers who left frustrated. Review unanswered conversations as well as rated ones.

Track the split between confirmed agent resolutions and conversations passed to staff. Keep unresolved conversations in a separate category. For presale questions, also compare purchase completion across equivalent cohorts to spot a buying journey that gets worse as ticket volume falls.

The guide to customer service metrics covers the wider measures to pair with ticket volume. Expand deflection to another question type when answers remain correct, repeat contacts stay controlled and shoppers can still reach your team.