Guidelines
The rulebook for EDesk — positioning, personality, audience, and the lines we don't cross. Hand this page to anyone creating on the brand's behalf.
Positioning
TaglineCommand center for customer support at scale
MissionWe build the infrastructure layer that lets e-commerce operators handle support like air traffic control — calm, precise, and always in command.
Market positionpremium
DifferentiationEDesk is positioned as the only helpdesk built from the ground up for multi-channel e-commerce operations, not a generic ticketing system retrofitted with marketplace integrations. Where Zendesk offers breadth and Gorgias offers Shopify-native depth, EDesk owns the complexity layer — the operational backbone for merchants managing 200+ marketplace integrations simultaneously, designed with the system rigor of infrastructure software rather than the feature-list thinking of traditional support platforms.
Essence & personality
Archetypecaregiver · ruler
PromiseWhen your support queue explodes, eDesk reduces 10,000 tickets to signal you can act on — no chaos, no guesswork, no tickets left behind.
StoryeDesk was built by e-commerce operators who'd spent too many nights manually triaging Shopify, Amazon, and eBay tickets across seven different inboxes. The founders weren't trying to reinvent customer service — they needed a control panel that could handle Black Friday volume without requiring a degree in systems engineering. What started as internal tooling for a multi-channel seller became the command center that enterprise merchants now trust when support volume spikes and every minute of downtime costs real revenue.
composedmethodicalattentiveunflappableclear-eyeddeliberate
Values
ClarityWe show you the 10,000 tickets as a solvable grid, not a wall of panic.
PrecisionEvery pixel, every label, every routing rule earns its place or gets deleted.
SteadinessWe don't sprint — we operate at the same reliable cadence whether it's Tuesday morning or Black Friday midnight.
CompetenceBuilt by people who understand triage logistics, not growth hacking playbooks.
RestraintWe subtract features, notifications, and visual noise until only the essential system remains.
Audience
WhoMid-level e-commerce operators and customer service managers at growing multi-channel retailers — people running 5-50 support agents across Amazon, eBay, Shopify storefronts who spend their mornings triaging ticket backlogs and their afternoons explaining missed SLAs to founders. They're former frontline agents who got promoted into operations roles, now responsible for keeping response times under 4 hours while the business doubles GMV every quarter.
Demographics28-45 years old, $55k-$95k salary, concentrated in US/UK/EU e-commerce hubs and remote
PsychographicsThey value systems that scale without requiring constant intervention — the relief of setting up a workflow once and watching it handle volume spikes autonomously. They fear being the bottleneck that caps company growth, the person who has to tell leadership 'we can't add another marketplace because support can't handle it.' They respect tools that treat complexity honestly rather than hiding it behind cheerful abstraction.
BehavioursAudits integrations and automation rules every Monday morning before tickets spike · Screenshots dashboard metrics to justify headcount requests in quarterly planning · Runs parallel trials of competing platforms in separate browser profiles before committing · Joins niche Slack communities and subreddits to troubleshoot edge cases other ops people have solved · Books demos only after reading full documentation and pricing pages · Exports data weekly to cross-reference platform reporting against internal BI tools
They valuereliability · transparency · efficiency · control · scalability · proof
Voice rules
Full voice samples live in Voice & MessagingEDesk speaks with the clipped precision of air traffic control — short declarative sentences, active verbs, zero filler. The tone respects the reader's technical fluency and time pressure: we acknowledge complexity honestly, then resolve it with operational clarity, never apologizing for power or dumbing down capability.
Do
- Use sentence-case headlines
- Lead with the operational outcome
- Write like dashboard labels: verb-noun
- Cut every adverb and qualifier
- Address 'you' when giving instruction
- Name the chaos before the solution
Don’t
- Never start with 'In today's…'
- No exclamation marks in body copy
- Avoid 'empower' and 'transform'
- Don't soften with 'just' or 'simply'
- Never use 'seamlessly' or 'effortlessly'
- No questions as headlines
Creative constraints
Don’t
- Visual: Cheerful illustration style with cartoon characters or anthropomorphized objects
- Visual: Abstract connection imagery: network nodes, linking lines, floating orbs
- Visual: Teal-to-purple gradients or any gradient overlays on data visualization
- Visual: Rounded friendly shapes: blob backgrounds, circular containers, soft organic forms
- Visual: Stock photography of diverse teams high-fiving or pointing at screens
- Visual: Glows, shadows, or depth effects that obscure information hierarchy
- Visual: Generic SaaS dashboard mockups with placeholder lorem ipsum data
- Visual: Oversized pull-quote testimonials with circular headshot crops
- Visual: Decorative geometric patterns or abstract background textures
- Visual: Emoji or playful iconography in UI or marketing materials
- Tonal: Aspirational founder-speak: 'empowering', 'transforming', 'revolutionizing'
- Tonal: Corporate jargon: 'synergy', 'leverage', 'best-in-class', 'next-generation'
- Tonal: Minimizing language: 'simply', 'just', 'easily', 'don't worry'
- Tonal: False urgency or FOMO tactics: 'limited time', 'don't miss out', 'act now'
- Tonal: Cheerful exclamation points or overly enthusiastic tone
- Tonal: Self-congratulatory language about awards, funding rounds, or growth metrics
- Tonal: Ironic distance or startup cuteness: puns, winking tone, self-aware meta-commentary
- Tonal: Vague benefit claims without operational specifics: 'better customer experience', 'improved efficiency'
- Tonal: Questions posed to the reader as engagement bait: 'Tired of messy inboxes?'
- Tonal: Tech buzzwords used as credibility signals: 'AI-powered', 'intelligent', 'smart'
EDesk occupies the intersection of high-stakes operational control and attentive service design — these constraints protect against the twin failure modes of looking either like generic cheerful SaaS (which undermines operational seriousness) or impenetrable enterprise software (which contradicts the Caregiver's accessible competence). The visual avoids flatten the brand into 'just another dashboard tool', while the tonal avoids prevent the copy from either patronizing users or hiding behind jargon when clarity is the entire value proposition.