By industry
Customer stories
See how our clients are using Zipchat and the awesome benefits it's bringing to their businesses!
Zipchat AI
Your AI Agent live in under 1 hour
No code. Trained on your catalog. Converts on every channel.
Create free Agent Book a demoLearn Agentic Commerce
Earn certification and merch rewards. No credit card needed.
Start now →Summary: Most ecommerce brands track customer service with four numbers: ticket volume, response time, CSAT, and some measure of cost. The brands that improve fastest track eight numbers, review them on a weekly cadence, and tie each metric to one action. This guide covers exactly what to track, how to pull it, and how to turn the data into changes that reduce cost and improve CSAT.
Ticket volume tells you how busy your team is. It does not tell you whether your team is solving problems or creating new ones. A team with 1,000 tickets per month and a 30% re-contact rate is effectively handling 1,300 problems. The extra 300 are customers who did not get their issue resolved the first time.
CSAT tells you whether customers felt good about an interaction. It does not tell you whether the interaction was necessary. A team with 4.8/5 CSAT and 70% human-handled tickets is running an expensive, happy support operation. The 70% human-handled tickets could be AI-deflected.
Track metrics that connect to cost and to resolution quality, not just volume and sentiment.
This article is part of the ecommerce customer service hub.
1. Ticket volume by category. Total volume is less useful than volume broken down by category: WISMO, returns, product questions, billing, complaints. Category breakdown tells you where to invest in deflection first. WISMO at 35% of volume is a clear directive: build WISMO deflection before anything else.
2. First response time (FRT) by channel. Average time from customer message to first reply, tracked separately for AI chat, human chat, email, WhatsApp, and Instagram. Benchmarks: under 10 seconds for AI chat, under 2 minutes for human chat, under 4 hours for email. One number averaged across channels hides poor performance on specific channels.
3. Deflection rate. Percentage of tickets resolved without a human agent. Formula: AI or self-serve resolutions divided by total support attempts, multiplied by 100. Target: 70 to 85% for AI-first ecommerce brands. Track deflection rate separately for each ticket category. A 50% overall deflection rate with 0% WISMO deflection means you have not yet connected order data to AI.
4. CSAT by ticket type. Overall CSAT masks where the problems are. An 85% overall CSAT with 60% CSAT on returns and 95% CSAT on product questions tells you the returns process needs work. Measure CSAT for each major ticket category, not just overall.
5. Re-contact rate. Percentage of customers contacting again within 72 hours of a resolved ticket. Target: under 10%. Above 15% on a specific ticket type signals that your resolution for that type is not actually resolving the issue.
6. Average resolution time (ART). Total time from first contact to full resolution, including all back-and-forth. Different from first response time. A ticket responded to in 2 minutes but taking 3 days to resolve has poor ART despite good FRT. Target: under 30 minutes for chat, under 24 hours for email.
7. Cost per ticket. Total support cost (platform + agent salaries + overhead) divided by total tickets resolved. This metric connects your support operation to the P&L. A cost per ticket above $15 for standard queries signals over-reliance on human handling for deflectable ticket types.
8. Knowledge base gap rate. Percentage of AI or self-serve searches that return no results. This is the leading indicator of deflection rate decline. If 20% of searches return no results this month, deflection rate will drop next month. Fill gaps before they affect the headline number.
Daily (only during high-volume events like BFCM):
Weekly (30-minute review every Monday):
Monthly (60-minute review, first Monday of the month):
Quarterly:
A weekly support review should take 30 minutes maximum. The format:
Do not try to improve everything at once. One metric, one action, one week. Teams that improve systematically over 12 weeks outperform teams that hold monthly “deep dives” and never act between them.
Tropicfeel tracks deflection rate and CSAT by ticket category weekly. They identify gaps and update AI training accordingly. The result: 85% automation with CSAT above 90%. Read the Tropicfeel case study.
Minimum viable stack:
When to add more tools: Add a dedicated analytics platform (Klipfolio, Geckoboard) only when you have more than 5 agents and a team leader who reviews dashboards daily. Below that threshold, a weekly spreadsheet review is faster and requires no additional software cost.
The metrics above have no value unless they drive decisions. Every metric below target should have one question attached: “What is the single most likely cause of this gap?”
FRT above target for email: cause is usually queue depth (too many tickets for available agents) or routing (tickets going to wrong queue). Fix: add routing rule or reduce human-handled tickets via AI.
Deflection rate below target: cause is usually missing knowledge base content or AI not connected to order data. Fix: identify top 5 categories not deflecting and add FAQ entries or connect order data.
Re-contact rate above 10%: cause is incomplete resolutions (agent closed ticket before customer’s issue was fully addressed) or incorrect AI answers. Fix: review a sample of re-contact tickets and identify the common resolution gap.
CSAT below 80% for a specific ticket type: cause is either resolution quality or resolution time. Review the last 20 low-CSAT tickets for that type. If agents are responding fast and correctly, the issue is the resolution itself (policy or product). If agents are slow or incorrect, it is a process issue.
Family Nation improved CSAT by tracking it per ticket category and identifying that returns CSAT was dragging down their overall score. Read the Family Nation story.
Book a demo to see Zipchat’s analytics dashboard showing deflection rate, CSAT, and AI confidence score by ticket type. Book a demo or start a free trial.
Return to the ecommerce customer service guide for the full cluster.
Agentic commerce explained: what it is, how it differs from conversational commerce, the 4 agent capabilities, 10 use cases, ROI benchmarks, and the 2026 platform shift.
Learn what agentic search is, how it differs from keyword and semantic search, and why it cuts zero-results rate to under 2% for ecommerce stores.
Should you build or buy an AI chatbot for ecommerce? True cost comparison, timeline reality, maintenance burden, and when building makes sense vs. when buying wins.
Discover how AI shopping assistants guide buyers from browsing to checkout, lift conversion 15-35%, and what to look for when choosing one for your store.
