Summary: A helpdesk centralizes all support channels into one queue, tracks ticket status, enforces SLAs, and routes tickets to the right agent. Without one, support breaks down above 100 tickets per month. This guide covers what a helpdesk does, a 7-step setup process, how to configure SLAs and routing, and how AI transforms the helpdesk from a queue into a deflection system.
What a helpdesk does (and what it does not do)
A helpdesk aggregates support requests from all channels: email, live chat, Instagram DMs, WhatsApp, and Facebook Messenger into a single inbox. Every ticket has a status, an assigned agent, and a history. Nothing gets lost in a personal inbox or a shared Gmail account.
What a helpdesk does not do: it does not replace AI-powered deflection. A helpdesk manages the tickets that reach your team. AI deflects the tickets before they get there. The two systems work together. The helpdesk handles the 15 to 30% of tickets that AI escalates.
This article is part of the ecommerce customer service hub.
Calculate your ROI — See how much Zipchat saves your support team. Try the ROI calculator →
Signs you need a helpdesk
You are missing tickets. If customers report they sent a message and never received a reply, tickets are falling through the cracks. This happens when support runs from a shared inbox without ticket tracking.
You do not know your response time. If you cannot answer “what is our average first response time this week,” you have no data. A helpdesk tracks this automatically.
Agents are duplicating effort. Two agents replying to the same ticket, or two agents looking up the same order for the same customer on the same day, signals no shared queue.
You are growing past 100 tickets per month. At this volume, shared inbox support breaks. Tickets get missed, response time becomes inconsistent, and measuring anything accurately is impossible.
7 steps to set up an ecommerce helpdesk
Step 1: Connect all your channels.
Add email, live chat widget, Instagram, Facebook Messenger, and WhatsApp to the helpdesk inbox. Every channel should funnel into the same ticket queue. If WhatsApp is excluded, you will still have a split inbox problem.
Step 2: Connect your Shopify store.
The helpdesk should pull order data directly into the ticket view. Agents should see the customer’s last 3 orders, current order status, and return history without leaving the ticket. Gorgias and Zipchat do this natively. Zendesk and Freshdesk require a plugin.
Step 3: Set up ticket routing rules.
Write routing rules before tickets arrive. Minimum set: WISMO tickets go to AI first; refund requests go to returns queue; complaints tagged with “urgent” go to senior agent queue; VIP customer orders go to a priority queue.
Step 4: Configure SLA alerts.
Set SLA time windows per channel. Example: chat tickets unresponded to after 2 minutes trigger an alert; email tickets unresponded to after 4 hours trigger an alert. SLA alerts prevent tickets from aging invisibly.
Step 5: Build your canned responses library.
Write pre-approved replies for your top 20 ticket types: WISMO, return initiation, refund status, wrong item received, product question, sizing question, payment failure. Canned responses cut handle time by 40 to 60% for agents.
Step 6: Train AI on your knowledge base.
If your helpdesk includes AI (Zipchat, Gorgias, or a connected AI layer), upload your FAQ content, return policy, shipping policy, and product catalog. AI trained on this content deflects WISMO and policy questions before they reach agents.
Step 7: Set up reporting dashboards.
Configure weekly reports for: total ticket volume, first response time by channel, deflection rate, CSAT score, and ticket volume by category. Review these weekly in the first 90 days. Adjust routing and canned responses based on what you find.
Ticket routing: the logic that determines your response time
Routing rules determine which tickets reach which agents and in which order. Poorly configured routing means agents see tickets out of priority order, VIP customers wait longer than standard customers, and WISMO tickets reach agents when AI could have handled them.
Routing logic by priority:
| Ticket type | Route to |
|---|
| WISMO | AI first, escalate if unresolved |
| Return request | Returns queue |
| Complaint with “cancel” or “chargeback” | Senior agent |
| VIP customer tag | Priority queue |
| Product question | AI first, escalate if unresolved |
| Payment failure | Billing queue |
| Standard inquiry | General queue |
Build these rules on day one. Add exceptions as you discover edge cases. Review routing monthly: if the same ticket type keeps escalating from AI to humans, the routing rule or the AI training needs updating.
SLA configuration for ecommerce
SLAs work differently by channel. Chat customers expect responses in seconds. Email customers expect responses in hours. Configure SLAs to match each channel’s expectation.
| Channel | Response SLA | Resolution SLA |
|---|
| AI chat | 10 seconds | 10 minutes |
| Human chat | 2 minutes | 30 minutes |
| Email (standard) | 8 hours | 24 hours |
| Email (complaint) | 4 hours | 12 hours |
| WhatsApp | 30 minutes | 4 hours |
| Instagram DM | 30 minutes | 4 hours |
Set escalation paths for SLA breaches: a ticket breaching the first SLA triggers an agent alert. A ticket breaching the second SLA escalates to a supervisor. Without these escalation paths, SLA alerts are noise that agents ignore.
How AI changes the helpdesk
The traditional helpdesk model assumes every ticket enters a human queue. AI changes this by intercepting tickets before they reach the queue.
With AI deflection at 75%, a helpdesk that previously managed 3,000 tickets per month now manages 750. The queue empties faster. Response time on escalated tickets drops because agents have fewer tickets competing for their attention.
The helpdesk in 2026 is not a queue management system. It is an escalation management system. AI handles the routine 75%. The helpdesk manages the escalated 25% with full context from the AI interaction already visible.
Family Nation automated 80% of inquiries and reduced their human support queue to a manageable size for 2 agents. Read the Family Nation case study. CFS reduced support workload 75% using the same model. Read the CFS story.
Helpdesk failures to avoid
Not connecting all channels. A helpdesk with 4 out of 5 channels still has a split inbox problem. The fifth channel (usually WhatsApp or Instagram) generates tickets in a separate system that agents check separately.
Skipping Shopify integration. Agents who cannot see order data in the ticket view spend 30 to 90 seconds per ticket looking up the order in Shopify separately. At 50 tickets per day, that is 25 to 75 minutes of wasted time per agent per day.
No routing rules. Every ticket landing in a general queue with no prioritization means VIP complaints wait as long as product questions. Urgency is invisible.
Over-routing to AI. AI routed tickets it cannot handle confidently generates wrong answers at scale. Configure AI routing with confidence thresholds. Below a defined confidence level, the ticket goes straight to a human.
No CSAT measurement. A helpdesk without CSAT data cannot tell you whether fast tickets are good tickets. Speed and accuracy are both required. Measure both separately.
Set up your helpdesk in one session
Book a demo to see how Zipchat connects to Shopify, configures routing rules, and deploys AI deflection in one onboarding session. Book a demo or start a free trial.
Return to the ecommerce customer service guide for the full cluster.
