E-commerce
June 28, 2026
A growing DTC brand quickly goes from the founder replying to DMs to 500 tickets per week, three agents, a bot, outdated macros, and contradictory responses across email, chat, and Instagram. Without a central document, every new hire reinvents support, and every seasonal peak turns into chaos.
The DTC customer support playbook is the single operational document: policies, processes, roles, SLAs, macros, escalations, the bot, KPIs, and review rituals. Decagon points out that 94% of low-effort interactions lead to a repeat purchase (Decagon, e-commerce customer service playbook 2026).
This guide #118 covers structure, organization for 1 to 20+ people, and peak-period modules. Distinct from team alignment (#113) and launch support (#114): here is the permanent DTC scale playbook.
Summary
Why is a support playbook essential for DTC growth?
A DTC support playbook formalizes how the brand handles each request at scale.
Symptoms without a playbook
Inconsistent answers: agent A vs B, different return policy
Slow onboarding: 3 weeks before autonomy
Founder bottleneck: systematic CEO escalation
Zombie macros: Black Friday promo active in March
Poorly managed peaks: BFCM = SLA in breach
What a playbook solves
Single source of truth, hiring/BPO scalability, delegation within a clear framework, 5-day onboarding vs 3 weeks, ticket loop → playbook update.
Playbook vs wiki vs macros alone
Wiki = passive documentation. Macros = execution. Playbook = process + policies + roles + KPIs + rituals. Policy foundation: support policy (#280). Creation threshold: 200+ tickets/month, 2nd agent, or preparing for paid scale. US Tech Automations estimates 30% deflection achievable in 60 days with self-service and macros (US Tech Automations, DTC deflection 2026).
How do you adapt the playbook to the stage of growth?
Adapting the support playbook to the DTC stage avoids over-engineering or delays.
Stage 1: solo founder (< 100 tickets/month)
Light playbook: 1 page of policies + top 10 hub conditions. Notion or Google Doc. Monthly review.
Stage 2: first hire (100-400/month)
Core playbook: policies, SLAs, 20 macros, escalation. J1-J5 onboarding focus. Notion + Gorgias.
Stage 3: team (400-1,500/month)
Complete 10-module playbook. QA, tagging funnel, bot governance. Notion + Gorgias + analytics.
Stage 4: scale (1,500+/month)
Playbook + BFCM modules, launch, international. BPO, multi-shift, head of support, LMS training. Transition signals: founder > 2 hours/day on support (1→2), agent CSAT variance > 0.5 (2→3), > 1,500 tickets/month or 3 countries (3→4).
What 10-module structure for the playbook?
Structure of the DTC support playbook in 10 Notion modules.
Brand support vision and principles
Customer policies (delivery, return, promo, warranty)
Team organization and RACI
Ticket process: sorting, SLA, closing
Escalation and exceptional cases
Macros and canned responses
AI Bot: intents, corpus, handoff
Tagging and analytics funnel
Training and onboarding
KPIs, rituals, and continuous improvement
Format and versioning
Notion workspace: parent page, sub-pages per module, Gorgias macro links, 5-min training videos. Header of each page: version, date, owner, changelog. Notion Search, A-Z intents index, quick emergency links (chargeback, press, VIP). Stage 3: 30-60 pages. Each module: objective, owner, procedure, examples, anti-patterns, module KPI.
How do you centralize policies and the source of truth?
The policies source of truth module is the heart of the playbook.
Six mandatory policies
Delivery: lead times, zones, fees, carriers
Return: window, fees, exchange, exceptions
Promo: stacking, exclusions, duration
Warranty: defect, duration, proof
Refund: processing time, method, partial
Data: GDPR, account deletion
Master promises table
Marketing claim | official website text | standard support response | ops capable Y/N. Aligned with guide #113. Decision tree: return D+35, policy 30 days → standard refusal + VIP/defect exception → manager escalation.
Exceptions and sync
Commercial gestures max 15% without manager if < €50. VIP override under conditions. Website policy change = playbook update within 24 hours. T&C validated by legal, playbook copies exact wording. Recharge/Skio module if DTC subscription.
How to scale your support team?
DTC support team organization documented in the playbook.
Stage 3-4 Roles
Head of Support: playbook owner, KPIs, staffing
Team lead: QA, coaching, scheduling
L1 Agent: standard tickets, macros, bot handoff
L2 Agent: disputes, exceptions, VIP
Bot admin: corpus, intents, unmatched review
Ops liaison: stock, carrier, fulfillment
Staffing and BPO
Ratio: 1 agent / 300-500 tickets/month blended. 40%+ bot deflection increases ratio. BFCM: temporary staff ×2. FR coverage: 9:00 AM - 7:00 PM minimum. BPO receives BPO-light playbook: policies, macros, exceptions forbidden. QA 10% of BPO tickets.
Which ticket process, SLA, and priorities should be documented?
The standardized ticket process eliminates agent hesitation.
7-step workflow
Receipt: auto-tag intent + funnel stage
Triaging: SLA priority according to type
Research: Shopify sidebar order context
Response: adapted macro or bot deflection
Escalation if outside playbook scope
Closure: resolution + tags + order note if action taken
CSAT: post-interaction survey
SLA and priorities
Checkout chat: 2 min
Standard chat: 5 min
Email / DM: 4 business hours
VIP: 15 min for all priorities
P0: checkout payment failure, press, chargeback. P1: VIP, defect, anger. P2: WISMO, return. P3: pre-purchase info. Gorgias Views: P0 urgent, SLA breach risk, VIP queue, bot handoff pending. Snooze max 48 hours with mandatory reason.
How to structure macros, response templates, and onboarding?
Macros and training: daily execution of the playbook.
Gorgias macro library
Naming REP-[CATEGORY]-[NUMBER]: SHIP, RET, PROD, PROMO, VIP, TECH. Review date in Notion. Remove macro < 5 uses/90 days.
Top 10 DTC launch macros
WISMO tracking, portal return, size guide, promo conditions, delivery times, photo defect + replacement, unshipped cancellation, address modification, refund processing time, VIP welcome.
5-day onboarding
Day 1: playbook overview + policies quiz (90% required)
Day 2: 20 tickets shadowing a senior
Day 3: supervised macros
Day 4: bot handoff + escalation
Day 5: solo with QA on 100% of tickets
Detailed real-case curriculum: agent training #299 (CONV-LIBRARY, 4 phases, clinics).
Bi-monthly 30-min training. New macro: draft → lead review → head approve → publish. Approval workflow documented in playbook.
See support templates.
How do you govern the AI bot in the playbook?
AI bot module: automation governance in the DTC playbook.
Governance
Named owner: bot admin, not "nobody"
Corpus sync: weekly hub terms + PDP changes
Intents map: intent → macro → escalation rule
Confidence threshold: < 80% = human handoff
Review unmatched: weekly top 10 → corpus
Core Intents and Limits
track_order, return_start, size_help, shipping_cost, promo_check, product_specs. Handoff: transcript, order, viewed products, confidence score, suggested macro. Bot never decides: refund > €50, policy exception, press, legal. Alhena cites Clove: 70% automated volume, 3 min response vs 1 day (Alhena, DTC AI customer service 2026).
Which pics modules should be activated in the playbook?
Playbook pics modules are activated on demand, without rewriting the core.
BFCM Module
Forecast ×2-4, temp staffing + BPO, BFCM-* macros, promo intents, daily Slack war room, D+3 debrief. Toggle Notion "BFCM Module ACTIVE" + head of support sign-off.
Product Launch Module
REP-LAUNCH sheet, LAUNCH-* macros, SKU corpus overlay. Pre-launch waitlist phase: pre-launch support (#306). See full guide #114.
Paid Scale and International Module
Before ads campaign ×2 budget: macros audit, bot load test, +20% staffing (#112). FR/US/UK markets: country policies, macros suffix _US _UK, bot language routing.
Crisis Module
Data breach, defective batch, carrier strike: 1-page crisis playbook. Comms template, CEO escalation, pause ads. Chargeback module: 48h response, evidence, macro CHARGEBACK-001.
See BFCM preparation (#32), launch support (#114), paid support prep (#112), international support.
Which KPIs and rituals keep the playbook alive?
KPIs and rituals prevent the playbook from becoming obsolete.
KPI dashboard
WoW volume by intent, SLA compliance 95%+, CSAT 4.3+, FCR 70%+, bot deflection 40-60%, macro freshness 100% reviewed < 90 days, agent quiz score 90%+ post-update.
Weekly rituals
Monday 15 min: support funnel review (#117)
Wednesday 30 min: unmatched bot + top 5 difficult tickets
Friday 15 min: weekly SLA + CSAT
Monthly review
Audit policies vs site vs macros. QA 5% of tickets (#116). Top 10 intents → hub conditions or bot. 30 min team training. 1-page executive report. Loop: recurring ticket for 3+ weeks without macro → create macro → update playbook → measure drop in recontacts.
See response quality (#116), segmenting funnel (#117), chatbot KPIs (#11).
How to integrate Qstomy into the DTC playbook?
Qstomy integrates into the DTC support playbook as a bot execution + analytics layer.
Integration
Corpus sync: playbook policies → bot knowledge
Intent library: playbook scenarios → bot intents
Macro suggest: agent receives matching playbook macro
Tags funnel: auto sync Gorgias (#117)
Quality scoring: tone accuracy audit (#116)
Gaps report: top unmatched = sections to add
Quantified DTC Scenario
DTC Beauty 1,200 tickets/month, 4 agents. Notion playbook 45 pages. Qstomy deflection 48%. Unmatched report adds 8 M2 intents. Agent onboarding 10 days → 5 days. CSAT 4.2 → 4.5 in 4 months.
Notion template 10 modules duplicate + corpus import. Explore AI support, AI sales agent, Shopify, request a demo.
Which operational playbooks should be used to create the document this week?
Playbook 1: 90-day audit
Export top 50 Gorgias tickets for 90 days. List 10 recurring intents. This is the basis of your policies and macros.
Playbook 2: Core policies 2 hrs
Draft shipping, returns, promo, warranty, refund, GDPR. 80% already exists in the founder's head.
Playbook 3: Notion structure 10 modules
Duplicate template. Fill modules 1-2-4-6 in week 1. Pin playbook link in Slack. Gorgias sidebar link.
Playbook 4: 10 REP-* macros
Publish WISMO, return, size, promo, shipping, defect, cancellation, address, refund, VIP. Link each macro to a playbook section.
Playbook 5: Rituals + BFCM toggle module
Weekly review calendar in Notion. Prepare deactivated BFCM module, ready to activate. Named playbook owner (head support or delegated founder).
Useful internal links
The playbook is never finished: it lives as long as the brand scales.
Enzo
June 28, 2026
