Monday morning, forty emails
You open your support inbox on Monday. Forty new messages. Twelve are about logging in: forgotten passwords, a different email at checkout, a magic link that expired. Eight ask where last week's replay is. Six want an invoice with their company name. Four want to change their card. Three ask for refunds. The rest are real questions about the course, which are the ones you actually want to answer.
Each routine email takes a few minutes, because you have to look the student up in two or three tools before you can reply. By the time you reach the real questions, it is lunchtime.
Why the same questions keep coming
Most support questions in a course business are caused by the joins between tools: the checkout and the platform, the platform and the email tool, the payment tool and the invoice. Each answer needs a look-up in the right tool, which is quick for the person who knows where to look and slow for everyone else. Help pages exist, but students email anyway.
- Buyers use different emails at checkout and login.
- Replays and resources are harder to find than you think.
- Invoices with company details need manual editing.
- Card changes and refund requests arrive as free text.
- Every answer needs a look-up in another tool first.
What the inbox costs you
Your time, or an assistant's, spent on routine look-ups. Slow replies to simple problems annoy students more than slow replies to hard ones, because they know the answer should be easy. And the real course questions, which build loyalty and give you ideas for content, get the leftover time.
An inbox assistant that does the looking up
- Your support inbox, in Gmail, Outlook or a help desk such as Help Scout, is connected to a service that reads new messages.
- A language model such as OpenAI's or Anthropic Claude recognises the type of request: login, replay, invoice, card, refund, course question or something else.
- For routine types, the assistant looks the student up in your checkout, course platform and email tool, and finds the facts: which email they bought with, whether they are enrolled, which replay they mean.
- It drafts a reply with the right link or action: a login link to the correct email, the replay URL, an invoice with their company details, a card update link.
- You approve drafts with one click, or allow certain types to send automatically once you trust them.
- Refund requests are drafted against your policy, with the purchase date and progress shown, and always left for you to approve.
- Real course questions are left untouched for you, marked so they stand out.
| Request | What the assistant finds | Draft reply |
|---|---|---|
| Cannot log in | Bought with a different email | Login link to that email, with an explanation |
| Where is the replay? | Last Thursday's call | Direct link to the lesson |
| Invoice with company name | Payment in Stripe | Invoice with their details attached |
| Change card | Active subscription | Card update link |
| Refund | Purchase date and progress | Draft for your approval |
Mornings spent on the course
The routine emails are handled in minutes, with accurate answers because the assistant looked the student up. You spend your support time on the course questions. Students get quick answers to simple problems. And the monthly summary of request types shows you where the joins between tools are causing trouble, so you can fix the causes too.
Is your inbox like this?
- Most support emails are about login, replays, invoices or cards.
- Every reply needs a look-up in another tool.
- Real course questions wait behind routine ones.
- You are considering hiring just for support.
- Students wait for answers to simple problems.