The reality of running CX for a global D2C beauty brand
Modern beauty and skincare brands don't operate in one place. They sell on Shopify, run support out of Zendesk, field DMs across a dozen regional Instagram accounts, answer emails from retailers and collaborators, and try to keep a consistent brand voice across every single touchpoint.
We recently sat down with the CX leadership team at a fast-growing global skincare brand. Their setup will sound familiar to anyone running support at a D2C company today:
- ~1000 emails per day flowing into Zendesk
- ~1500 Instagram DMs per day still being answered manually, even with automation "turned on"
- A small team of 40 people covering global, CIS, and MENA regions
- Multiple regional Instagram accounts, plus website forms via Shopify
- Three dominant inquiry types — pricing, collaboration requests, and retailer questions — making up 70–80% of all volume
On paper, Zendesk should handle most of this. In practice, the team described it as "finicky" — the automation doesn't fire reliably, there's no single dashboard that surfaces what matters, and the manual workload keeps creeping back in.
Where the cracks show up
Three patterns kept coming up in the conversation, and they're patterns we see at almost every growing D2C brand:
1. The same questions, asked over and over, still answered by humans.Pricing inquiries, "do you ship to my country," "are you available at this retailer," "how do I collaborate" — these aren't complex tickets. They're high-volume, low-variance, and almost entirely scriptable. But generic chatbots answer them badly, so the team ends up handling them anyway.
2. Channel sprawl with no unified intelligence.Instagram DMs, Instagram comments, email, Shopify forms, regional accounts — each channel has its own quirks. A DM needs a short, casual reply. An email from a retailer needs something formal. A collaboration request needs a form link. One AI configuration can't serve all of them well.
3. Escalations that disappear into a black hole.When a ticket needs help from another team — the vendor, the warehouse, a regional manager — the support agent becomes a human relay station. They chase Slack messages, follow up on emails, and try to remember to circle back to the customer. This is where SLAs quietly die.
How AI agents change the math
The fix isn't "add a chatbot." It's rethinking the support stack as a layer of specialized AI agents working on top of Zendesk, not replacing it.
Here's what that looks like in practice for a brand like this:
Specialized agents, not one generic bot
A pricing agent answers pricing questions using live product data from Shopify. A collaboration agent recognizes the intent and sends the right form. A retailer agent pulls from a stocklist. A shipping agent escalates to humans because that's where judgment matters. Each agent is tuned for its job — the way you'd staff a real team.
Channel-aware responses
The same underlying knowledge, expressed differently per channel. Short and friendly on Instagram DMs. Structured and professional on email. Form-first on the website. The brand voice stays consistent; the format adapts.
Multi-language out of the box
For a brand selling across global, CIS, and MENA regions, this matters. Customers write in Korean, Arabic, Russian, English — the agent responds in the same language without separate configuration.
Escalations that close their own loop
When an AI agent can't resolve something, it doesn't just dump the ticket on a human. It identifies who needs to be looped in, follows up with that internal team, and then circles back to the customer once it has an answer. The "human relay" work disappears.
Knowledge gaps surfaced automatically
The system flags new questions customers are asking that aren't covered in existing content — so the team knows exactly what FAQ, product page, or help article to write next. Deflection rates compound week over week instead of plateauing.
The realistic impact
For a CX team handling ~100 emails and ~150 DMs per day, here's the math that matters:
- 70–80% of inquiries are pricing, collaboration, or retailer questions — almost all of which an AI agent can fully resolve
- The remaining 20–30% (product authentication, shipping issues) still reach a human, but with full context and pre-categorization
- A 4–5 person team stops spending its day on repetitive replies and starts focusing on the cases that actually need a human
- Time-to-live is measured in weeks, not months — a working chat widget can be deployed in days, with workflows refined iteratively
The team we spoke with isn't looking to replace their people. They're looking to stop drowning in DMs so their people can do better work — handle the nuanced cases, build the knowledge base, expand into new regions without doubling headcount.
What this looks like for your brand
If you're running CX for a D2C brand on Zendesk and Shopify, the questions to ask yourself are simple:
- What percentage of your tickets are repeat questions you could write a script for?
- How much of your team's time goes into relaying information between customers and internal teams?
- Are you confident your current automation actually works, or are you quietly doing most of it manually?
If any of those land, there's a better way to run this. AI agents that sit on top of your existing stack, speak your brand voice, work across every channel, and get smarter every week — without ripping out the tools your team already knows.
Want to see what this looks like for your brand? We build a working AI agent on your actual website content in under a week, so you can evaluate it on real questions before committing to anything. [Get in touch].
