E-commerce
June 28, 2026
The customer is hesitating on your product page. They open the chat at 9:14 PM. Silence. They close the tab and order from a competitor. The first response time (FRT) is not just an ops metric: it is a direct lever for conversion and loyalty.
Gorgias Ecom Lab shows that the FRT varies from 1.6 h to 8.8 h depending on the vertical for identical GMV, which is a 5.5x difference (Gorgias, vertical benchmarks 2026). Heeya points out that a pre-purchase response in under 30 seconds with accurate information can trigger the purchase, whereas a 4-hour delay is equivalent to cart abandonment (Heeya, FRT and conversion 2026).
This guide #137 treats the FRT as a business KPI: revenue impact, retention, benchmarks by channel. Distinct from SLA support (#101) (internal delays by type) and FCR (#136) (first contact resolution).
Summary
Why does first response time impact conversion and loyalty?
E-commerce FRT (First Response Time) measures the delay between the customer's first message and the first substantial response from your brand, whether human or bot.
Two critical moments
Pre-purchase: the customer is comparing, doubting, seeking reassurance. Every unanswered minute increases the risk of cart abandonment.
Post-purchase: WISMO, delay, return. A long FRT fuels chargebacks, negative reviews, and lack of repeat business.
What the customer feels
On chat, a 3 to 5-minute wait = frequent abandonment (Lorikeet, 2026). On email, 46% of customers expect a response within 4 hours; the industry average often exceeds 8 hours (GreetNow, 2026 statistics). FRT is the first signal of trust after clicking "Buy".
DTC Example
Furniture brand, median pre-purchase chat FRT 4 min 20 s. GA4 analysis: 34% of pre-purchase chat sessions with no response under 2 min do not convert. Transition to instant bot + agent < 45 s during off-peak hours: assisted chat conversion down +22% in 8 weeks.
Convert over 2,000 customers on average per month with Qstomy.
The world’s 1st Shopify AI dedicated to customer conversion
Empowering 200+ e-commerce merchants
How does FRT differ from internal SLAs and FCR?
Three metrics often confused, three different uses.
FRT vs SLA (#101)
The support SLAs (#101) set your internal commitments by request type and channel. FRT measures the reality on the ground. A "4h email" SLA is only useful if you track median FRT and breach rate each week.
FRT vs FCR (#136)
FRT measures speed. FCR (#136) measures whether the issue is resolved. Replying in 30s with a vague reply improves FRT but degrades FCR. Goal: short FRT + complete answer from the very first message.
FRT vs resolution time
A "we have received your message" sometimes counts towards FRT but is not reassuring. Define internally: auto-ack ≠ first substantive response for management reporting.
How to define and measure FRT correctly?
A poorly measured FRT distorts staffing decisions and marketing promises.
Formula
FRT = timestamp of first substantive response − timestamp of first customer message. Exclude auto-closed spam tickets. Segment bot vs. human.
Median, not average
The average is skewed by a few tickets forgotten for 48 hours. Report the 50th percentile (median) and P80 to see the long tail. Gorgias calculates FRT by channel in native reports (Gorgias, optimiser FRT).
Business hours vs. 24/7
Email: SLA often in business hours. Chat bot: 24/7. Do not mix the two in a single dashboard without a channel filter. Weekends and BFCM: measure FRT separately, as this is where the competitive gap widens.
Useful tags
`frt_breach`, `pre_achat`, `post_achat`, `channel_chat`, `bot_first_reply`. See taxonomie tickets (#135), segment funnel (#118).
Which FRT benchmarks to target by channel and vertical?
2026 E-commerce FRT benchmarks vary heavily by channel and vertical. Compare yourself to your niche, not a global average.
By channel (performer targets)
Live chat / widget: < 30-40 s (leaders), < 2 min acceptable
Tier 0 AI bot: < 5 s effective
Email: < 1-2 h leaders, < 4 h good, 8-12 h industry average
Instagram / social DM: < 60 min, reputation risk beyond 4 h
WhatsApp / SMS: < 10-15 min, "urgent" channel
By vertical at similar GMV
Gorgias Ecom Lab: median hardware ~1.6 h, apparel ~8.8 h at $10M GMV. FRT is the ops metric that varies the most between verticals (x5.5), unlike CSAT, which varies very little.
Automation impact
Gorgias: brands at ~0% automation, average FRT ~736 min. At 30% automation, ~80 min. At 40%, ~12 min. AI does not replace all human FRT, but it clears the queue of repetitive intents.
What is the measurable business impact of FRT on revenue?
Linking FRT and revenue convinces management beyond just the support team.
Documented Correlation
Pre-purchase conversion: Heeya estimates +20% conversion on journeys where the issue is resolved quickly
CSAT: GreetNow cites ~1.7 CSAT points lost per hour of delay
Repeat purchase: customers who are well served quickly buy more again (Gorgias benchmarks)
Chargebacks: WISMO 24h+ with no response = risk of dispute
Simple Management Model
(Pre-purchase chat sessions/month) × (% lost if FRT > 2 min) × (assisted conv. rate) × (AOV) = recoverable revenue. Example: 2,000 sessions × 25% × 8% conv × €85 = €3,400/month if chat FRT drops from 3 min to 45 s. Document baseline before/after.
Cost of Inaction
GreetNow estimates that slow replies cost US businesses billions in lost leads. For a DTC with €2M in revenue, 12% of revenue at risk due to slow support is not uncommon during seasonal pre-purchase periods.
How does pre-purchase FRT influence conversion?
Pre-purchase FRT comes into play at moments of maximum friction: sizing, compatibility, lead time, promo, stock.
High-stakes journey
PDP: product question, the customer has one hand on the buy button
Cart: promo code, shipping costs, final hesitation
Checkout: payment declined, address, express delivery
Immediate levers
Chat widget visible on PDP and checkout with instant tier 0 bot (stock, lead time, return policy). Priority queue "pre_achat" in Gorgias: auto-tag if URL contains /products/ or /cart. Short macros with PDP link and purchase CTA. See pre-purchase questions, checkout widget, abandoned cart chatbot.
Assisted conversion measurement
UTM or GA4 event: purchase within 24 hours post-pre-purchase chat. Compare assisted conversion when FRT < 1 min vs > 3 min. The gap quantifies the investment in bots or evening staffing.
How does post-purchase FRT influence retention and NPS?
Post-purchase, the FRT conditions the global brand perception, often more than the product itself on logistical intents.
Delay-sensitive intents
WISMO: anxious waiting, target bot FRT < 5 s
Late delivery: FRT < 1 h, proactive update before ticket
Order modification: short fulfillment window, FRT = ops challenge
Return / refund: FRT < 4 h email, immediate portal link
Proactivity vs reactivity
Shipping email + late SMS reduces WISMO tickets by 20 to 35%. Each avoided ticket = effectively zero FRT and preserved NPS. See Post-purchase SMS (#130), due dates communication, NPS timing.
Repeat rate
A customer whose WISMO is answered in < 2 min repurchases 1.4x more often than a customer kept waiting 24 h (pattern observed on mid-market DTC cohorts). Track 90-day repeat rate by post-purchase FRT bracket.
How does the AI bot transform the effective FRT?
The AI bot is the most powerful FRT lever for high-volume intents and structured data.
FRT bot vs FRT human
Report separately. A blended flat hides a 3s bot and a 6h email queue. Open.cx cites 70 to 84% resolution on e-commerce tickets for top AI performers in 2026. The effective FRT bot on WISMO = almost instant.
FRT bot priority intents
WISMO with Shopify sync tracking
Return policy + Loop portal link
Variant stock availability
Delivery time by country
Current refund status
Handoff without FRT reset
When the bot escalates, the agent must reply in < 2 min with full context. The customer will not tolerate re-explaining their order. See helpdesk vs chatbot, choosing questions to automate.
How do you reduce human FRT without sacrificing quality?
Reducing the human FRT is achieved through queue structure, not through rushed responses.
5 Gorgias ops levers
SLA alerts: alert at 80% of target time, not after breach
Rules routing: VIP and pre-purchase at the front of the queue
Keyboard macros: /wismo, /return, /ship pre-filled with dynamic data
Unified inbox: chat, email, IG, SMS on the same screen
Intelligent auto-ack: "Marie is looking at your order #4521, reply within 3 min" counts as customer FRT if personalized
Staffing by time slot
Gorgias FRT export by hour: 7pm-10pm peak is often under-staffed. 2 hrs/evening support or reinforced pre-purchase bot. BFCM: FRT plan daily from D-7 to D+3.
FRT / FCR balance
Ban empty "thank you for waiting" macros as the sole reply. First response = minimum 1 actionable piece of info (tracking, link, ETA, decision). See response quality (#116), support templates.
How to manage the FRT by funnel and customer segment?
The segmented FRT dashboard guides bot budget, staffing, and training.
Funnel × Channel Matrix
Cross pre-purchase / post-purchase × chat / email / social. Example: pre-purchase × chat FRT P80 > 2 min = priority #1 conversion. post-purchase × email FRT > 4 h = priority retention.
Customer Segments
VIP / High LTV: Target chat FRT < 30 s, dedicated queue
First-time pre-purchase: FRT < 1 min, acquisition stake
International: Email FRT 8 h time zones, 24/7 bot compensates
Weekly 20-min Ritual
Median and P80 FRT per channel, top 3 breaches, 1 action (macro, rule, shift). Slack share #support-kpi. See conversational analytics, VIP escalation, DTC playbook.
How does Qstomy accelerate the first response time?
Qstomy aims for an almost instant FRT on data-driven intents and an accelerated human handoff for the rest.
FRT Features
Response < 3 s: WISMO, stock, policy, lead time
Native Shopify lookup: no "what is your order number?"
Pre_purchase prioritization: automatic funnel routing
Contextual handoff: agent responds in < 2 min with transcript
FRT report: bot vs human median by intent and channel
Quantified DTC Scenario
Apparel brand, 4,100 tickets/month, median blended FRT 5 h 20 (email 7 h, chat 3 min 40). Qstomy deployment widget PDP + checkout + email triage. After 12 weeks: bot FRT 2.8 s, human chat FRT 58 s, email 1 h 45. Assisted chat conversion +18%. 90-day repeat rate +12%. Email WISMO tickets -41% (bot + proactive shipping).
Explore AI support, Shopify, request a demo.
Which operational playbooks can help increase responsiveness?
Playbook 1: 14-day FRT baseline
Gorgias export: median FRT and P80 by channel + pre/post funnel. Identify the worst channel x intent combination. Team sharing. Timeframe: 2 h setup + 14 days collection.
Playbook 2: pre-purchase chat sprint
Tier 0 bot on top 5 PDP questions. Rule: URL /products/ → high-priority pre_purchase queue. Goal: pre_purchase chat FRT P80 < 60 s in 4 weeks. Measure assisted conversion in parallel.
Playbook 3: Gorgias SLA alerts
Create SLAs: chat 2 min, email 4 h, IG 60 min. Alerts at 80%. Review breaches on Friday 25 min. 1 fix rule or macro per week.
Playbook 4: evening peak staffing
Hourly FRT heatmap over 30 days. If 6pm-10pm FRT is 2x daytime FRT: add 1 agent backup or reinforced pre_purchase bot. Re-measure after 14 days.
Playbook 5: FRT / repeat correlation
Post-purchase customer cohort: FRT segment < 2 min vs > 6 h. Compare 90-day repeat rate. Present 1 slide to management for support budget.
Useful links
FRT is the most visible KPI for the customer and the most actionable for you. Start with pre-purchase chat: this is where every second counts for the cart.
Enzo
June 28, 2026
