// for cs managers

Handle inbound at scale, without losing tone.

Magistry's CS Specialist replies to inbound email end-to-end — refund, replace, escalate, follow up — in your brand voice, behind an expected-value gate, with a Reply Judge that holds anything off-policy before it ships.

See a reply in flight

Start free

Brand-voice embeddings Expected-value refund gate Reply Judge in front of every send

// why cs managers pick magistry

A teammate that closes tickets the way your best rep would.

Generic LLM CS bots cost you tone, trust, and refund discipline. Magistry's CS Specialist holds all three — because the policy and the voice are grounded against your own data, not the open web.

Brand-voice embeddings, not generic templates

Magistry indexes your best 500 replies and grounds every draft against them. The tone matches your top CS rep on a Tuesday afternoon, every single ticket.

Expected-value refund gate, not gut feel

Refund or replace? Magistry weighs item cost, LTV, refund-band history, and policy — then takes the action with the highest expected value, inside your refund ceiling.

Reply Judge catches off-tone or off-policy before it ships

Every draft passes a second pass: brand voice, policy grounding, escalation triggers. Off-policy drafts get held for you; everything else ships.

Proactive outbound on delays, stockouts, recalls

Tracking late by 3 days? Variant restocked? SKU recalled? Magistry drafts the outbound, queues it inside frequency caps, and only sends what you allow.

// this week

What the CS Specialist did for your inbox this week.

A real week from a Magistry tenant running the CS Specialist in live mode — every reply judged, every refund gated, every outbound capped.

Closed 312 inbound tickets end-to-end inside brand voice — 84% first-touch resolution, 11 escalated to you with the full thread + suggested reply.
Issued 47 refunds and 22 replacements via the expected-value gate — average refund €38, average replacement margin held at 41%, zero policy breaches.
Drafted 1,840 proactive outbound messages on 3-day late tracking and 2 restock events — only sent the 1,612 inside your frequency cap; the rest deferred to next window.

// from your dashboard

One ticket. One judged draft. One reply, in your voice.

Below: a replacement decision on a damaged-shipment ticket, scored by the expected-value gate and passed by the Reply Judge before it shipped.

decision_log #91,402   ── cs_specialist
ticket         #29,118   subject "arrived damaged"
customer       hannah.k@example.com   LTV EUR 412
sku            stone-vase-large
intent_class   damaged_on_arrival   conf 0.94
policy_match   refund_or_replace_30d  (RAG cite §4.2)

ev_gate    refund   value -EUR 64  cost  EUR 64
           replace  value +EUR 11  cost  EUR 53
action     REPLACE   (highest EV, within ceiling)

reply_judge    brand_voice 0.92 / 0.80 floor — PASS
               policy_grounded TRUE      — PASS
               escalation_signal none    — PASS

mutation       shopify.fulfillment.create + email.send
reverse_op     issue refund EUR 64 + cancel fulfillment
status         APPLIED

// the reply that shipped

In your voice. Inside your policy. With the receipt.

Hi Hannah,

That's not how a stone vase should arrive — I'm sorry. I've already sent a replacement; tracking will land in your inbox within the hour. Keep the original (or recycle it — it's heavy). Anything else, just reply here.

— Sam, on behalf of the team

Brand voice match 0.92 · Policy grounded · Reply Judge: PASS · EV: replace > refund

// what cs managers are saying

From an operator whose queue finally cleared by Friday.

“Our CS load dropped 40% the week we turned on the CS Specialist. The remaining 60% is the work humans should actually be doing — escalations, gnarly returns, real relationships. The bot handles the noise; we handle the signal.”

Ben Diamond

COO

Stoke Goods

// inbox, handled

Stop staffing for ticket volume. Staff for relationships.

Spin up a tenant, point Magistry at your CS inbox, and watch first-touch resolution climb — every reply judged, every refund gated, every send capped.

See it in action

Start free

Kill switch ON by default · Dry-run from day one