Support that feels like a superpower.
Batch support into two daily windows, keep saved answers for the ten questions that make up most of your volume, fix the cause after the third repeat, and let speed, not length, be what impresses.
How do I handle support alone?
- 1Batch it: two windows a day (morning and late afternoon), inbox closed in between. Same-day beats instant, and batching protects your build time.
- 2Write saved replies for your top ten questions, in your voice, not boilerplate. Personalize the first line, paste the rest.
- 3Track repeats. The third time you answer the same question, the answer belongs in the product: a tooltip, a better empty state, a renamed button.
- 4Keep replies short. Three friendly sentences that solve it beat a formal page that doesn't.
What makes support feel exceptional?
Speed and name-use. A two-hour reply that opens with their name and quotes their actual problem feels like magic, even if the answer is "not yet."
Closing the loop is the superpower move: when you ship the fix someone asked about, email them personally. That's how customers become evangelists.
How do I say no in support?
Fast and warm: "We're not building that this quarter, here's the workaround, and I've noted your vote." A quick honest no builds more trust than a slow maybe. There's a whole guide on this, see "Saying no to feature requests kindly."
Quick answers.
Do I need a help desk tool?
Not until volume hurts. A shared inbox with labels handles the first few hundred customers fine.
Should I publish a help center?
Once you have ten saved replies, yes, they're your first ten articles. Written once, answered forever.
What response time should I promise?
Promise one business day, deliver same-day. Under-promising is the cheapest customer delight available.
Build the thing this guide is about.
Stencil turns your idea into working subscription software — no code required.