25 September 2026 · 4 min read
How to run support for a digital product without a helpdesk
If you sell a template, course or small SaaS, most support email is some version of the same few questions. A helpdesk seat is more than that needs. Sort the mail into categories and write the common replies once, then decide in advance which messages jump the queue.
Short answer
Sort every message into five categories (download, how-to, refund, billing, other), keep one written reply for each of the first three, answer in a fixed daily block, and escalate anything that mentions a chargeback or a lawyer straight away. A shared Gmail inbox and one Notion database are enough until more than one person is answering.
1. Sort before you answer
Replying to each email as it arrives means every message costs a context switch. Sort first, then answer in batches. For a digital product, five buckets are enough:
| Category | What it sounds like | Answer within |
|---|---|---|
| Download | "Where's my file?", "the link expired", "I didn't get the email" | Same day |
| How-to | "How do I import this?", "which plan do I need?" | One business day |
| Refund | "Can I get my money back?", "cancel", "chargeback" | Same day acknowledgement |
| Billing | Invoices, tax, wrong plan, currency | One business day |
| Other | Feature ideas, partnerships, everything else | When you can |
Download problems come first because the buyer paid and has nothing. They're also the easiest to fix, usually by resending a link.
2. Write the replies once
Write the download, how-to and refund replies before launch, while you're calm and nobody is waiting on you. Keep them short and specific:
- Download: a fresh link, where the original email came from (so they can search for it), and a note to check spam.
- How-to: a link to the exact doc section, plus one sentence answering the question directly. If the doc didn't answer it, fix the doc.
- Refund: acknowledge, state your policy in one line, and say when they'll hear back. Decide the refund yourself. Don't automate it.
Paste them as Gmail templates or keep them in a Notion page you copy from. After that, most answers mean changing a name and a link.
3. Escalate the dangerous ones
A few words mean a message should skip the queue: chargeback, dispute, lawyer, scam, fraud. A chargeback costs you the sale plus a dispute fee, and a quick personal reply is the cheapest way to stop a buyer filing one. Set up a Gmail filter or an automation that stars or labels these messages so you see them first.
A second rule worth having: if the same person writes twice without a reply, move them up. Silence turns a how-to question into a refund request.
4. Answer in a block
Pick one or two fixed times a day, for example 9am and 4pm, and clear the queue in category order. Outside those times, the inbox stays closed unless something is escalated. Give the block a fixed length, say 30 minutes. If you regularly can't clear the queue inside it, that is one of the signals in the last section below.
5. Keep a record
A simple ticket database (subject, sender, category, status, date) shows you patterns: which question keeps coming back, and which doc or product screen should be fixed so it stops. If "where's my download" makes up a quarter of your mail, rewrite the delivery email before you change anything else.
The free Support Inbox Triage workflow does the sorting and logging automatically: it reads new Gmail messages, routes them by keyword to Download, How-to, Refund or Other, and files each one as a Notion ticket. Billing is a category in the database that you set by hand.
When to graduate to a helpdesk
The case for paying changes once a second person answers email. Two people working one Gmail inbox will sooner or later both reply to the same customer, or each assume the other did. Assignment and collision detection are what a helpdesk sells, and nothing in a Gmail and Notion setup gives you those. The other trigger is volume, when the daily block keeps running out before the queue does. Until one of those happens, the setup above costs nothing beyond tools you already use.
Questions
When should I switch to a real helpdesk?
When more than one person answers email, when you need shared assignment and collision detection, or when volume regularly passes what you can clear in a daily 30-minute block.
Should I auto-reply to support email?
Only with an acknowledgement that says when you'll answer. Auto-sending the actual answer risks sending a cheerful template to someone who is angry.