Worked example · Inbox Copilot

One support morning, before and after.

A realistic walkthrough of what changes when a small-business support inbox is run through Inbox Copilot. Same tickets, same tone, same reviewer; the difference is how long it takes and how much ends up in the dropped-leads pile.

Disclosure: This is an illustrative example built from typical SMB support patterns, not a live customer case study. It reflects the flow Inbox Copilot implements and the kinds of time savings we target. Named case studies will replace this page as we publish them with customer consent.

The setup

A three-person studio runs a shared hello@ inbox. One owner does support between other work. An average weekday brings around 20 support emails: mostly repeat intent — invoices, status questions, reschedule requests, and the occasional complaint. The owner's target is a reply within one business day. Reality is closer to 36 hours.

Typical morning before

The owner sits down with coffee, opens the inbox, and starts triaging. Each ticket needs: read context, check two other tools (billing portal, calendar), decide intent, draft the reply, send. The first five take about 45 minutes. By the time the phone rings for an actual client, six are still waiting.

Same morning with Inbox Copilot

Inbox Copilot has already classified overnight arrivals by intent, pulled the relevant context from past threads, and drafted a reply in the owner's tone. The owner scans each draft, edits where it matters, approves, sends. No context-switching between tabs for billing and calendar lookups — the draft already includes them.

Walk through three real-looking tickets

Ticket 1 — before

Time to reply: ~6 min · tools touched: 3

Subject: Need invoice PDF for April

From: [email protected]

Hey — I can't find our last invoice in the portal. Can you send it over?

Open billing portal, find customer
Download April invoice PDF
Write reply from scratch
Attach, hit send

Ticket 1 — after

Time to reply: ~40 sec · tools touched: 1

Intent: invoice request Confidence: high Context pulled from billing

AI draft — human review required

Hi Jamie, Attached is the April invoice PDF. If it'd help, I can also resend the May invoice and turn on automatic monthly receipts so it's one less thing to chase down. — Morgan

Attachment pre-populated. Tone matches owner's last 200 sent emails.

Ticket 2 — before

Time to reply: ~4 min

Subject: Reschedule Wed session

From: [email protected]

Any chance we can move Wednesday to Thursday same time? Sorry for the short notice.

Check calendar for Thursday availability
Check Wednesday existing booking
Draft reply proposing Thursday slot

Ticket 2 — after

Time to reply: ~20 sec

Intent: reschedule Calendar checked Confidence: medium

AI draft — human review required

Hi Priya, No problem. Thursday at 2pm works on my side. I've tentatively held it. If you want me to just confirm the move, reply with "go" and I'll send an updated invite. — Morgan

Ticket 3 — before

Time to reply: 0 min (missed)

Subject: You never replied to my question

From: [email protected]

Last Thursday I asked about adding another seat. Haven't heard back. Is this still active?

Would have needed to dig for Thursday's thread
Sits in the pile while the owner triages easier ones
Retention risk

Ticket 3 — after

Time to reply: ~60 sec · flagged for priority

Priority: high · retention risk Original thread linked Intent: upsell (add seat)

AI draft — human review required

Hi Dana, Sorry for the delay — that one slipped. Adding a second seat is $29/month, billed to the card on file. If you reply "yes" I'll add it today and send a prorated receipt. — Morgan

Copilot surfaces the thread, detects the retention risk, and drafts with the upsell answer ready.

What the morning looks like in aggregate

~3.5 hrs → ~40 min

Owner time on support inbox

<1 business day

Response-time target, consistently hit

Replies auto-sent without review

How it's wired

Connection: OAuth into Gmail / Workspace (or IMAP for legacy hosts). Read + draft scope only; we don't auto-send.
Tone learning: Last ~200 sent messages from the owner's Sent folder, one-time import, embedded locally to the account.
Context pulls: Billing (Stripe or whatever's connected), calendar, past tickets. Configurable per integration.
Review surface: Gmail draft pane or Cserv review view — owner's choice. Drafts appear next to the original thread, never separately.
Safety defaults: Draft-only by default, PII redacted in logs, 30-day retention on full message bodies.

What you'd expect in the first 30 days

Week 1: connect inbox, import tone samples, review first drafts alongside normal replies.
Week 2: accept rate climbs as context coverage improves. Typical 70% accept-without-edit by day 10.
Week 3: FAQ Builder output gets folded in. Repeat-intent tickets (invoices, reschedules) run faster.
Week 4: operator-layer check-in. We tune anything that's off-tone, over-confident, or under-used.

Want this set up on your inbox?

Start with a $100 retainer. We'll book the kickoff call within two business days, scope your inbox, and either quote the implementation or refund you in full.

Request $100 retainer →

Secure checkout via Stripe · Fully refundable if we don't book in 30 days