When you sell something online, people will have questions. Where's my download? Does this work on my phone? Can I get a different format? You're the help desk now, and also the owner, the janitor and the guy who fixes the printer.
That sounds like a lot. It isn't, if you set up a few habits early.
By the end of this, you'll have one place where customer messages land, a reply rhythm you can keep, a set of saved replies for common questions, and a plan for the occasional grumpy message.
The short version
- Send every customer question to one inbox and check it on a schedule you can actually keep.
- Write saved replies for the questions you get over and over, then make each one sound like a person.
- Stay calm and kind, fix the real problem, and set limits when someone crosses a line.
Set up one place for questions
Customer support just means helping people who bought from you, or are thinking about it. The first job is making sure their messages don't get lost.
Pick one email address for support. It can be a simple address on your own domain, like help@ or hello@, or a separate free account in a tool like Gmail. Don't use your personal inbox, where a customer's question sits between a dentist reminder and a coupon for tires.
Then put that address everywhere a buyer might look:
- Your sales page
- Your checkout page
- Your receipt and delivery emails
- Inside the product itself, on the first or last page
If people have to hunt for a way to reach you, some will give up. Others will go straight to their bank and dispute the charge, which is a much worse conversation. The lesson on getting paid covers how those disputes work.
Pick a reply rhythm you can keep
You don't have to answer in five minutes. You're one person with a life. But you do need a rhythm, and you need to stick to it.
Choose your check-in times
Decide when you'll check your support inbox. Maybe once in the morning before work and once in the evening. Maybe once a day on weekdays. Write it down and treat it like a short appointment.
Checking on a schedule beats checking constantly, which eats your focus and makes you jumpy.
Tell people what to expect
Put a plain line near your contact address: "I'm a one-person shop. I answer messages within a business day or two." Use whatever window is true for you.
That one sentence does a lot of work. People are patient when they know what to expect and nervous when they don't. A clear promise you keep beats a fast reply you can't repeat.
Send a quick "got it" when needed
If a question needs real digging, don't go silent while you dig. Send a short note first: "Got your message. I'm looking into it and will get back to you by tomorrow evening." Then do it.
Build a set of saved replies
A saved reply, sometimes called a canned response or template, is a message you write once and reuse. Many email tools let you store these and drop them in with a click. If yours doesn't, a plain document you copy and paste from works fine.
Find your common questions
You probably already know a few. Most small digital shops hear versions of these:
- I didn't get my download.
- The file won't open.
- Can I get a refund?
- Does this work on my phone or tablet?
- I bought the wrong thing.
Start with these. Every time a new question shows up twice, write a saved reply for it.
Write them like a person
Here's a saved reply for a missing download:
"Hi [name], thanks for buying. Sorry the download didn't come through. Here's your link again: [link]. If it lands in spam, mark it as not spam so future emails get through. If it still doesn't work, reply here and tell me what you see, and I'll sort it out."
Notice what it does. It thanks them, says sorry without groveling, gives the fix right away, and offers a next step. No blame, no lecture about checking spam folders like they should've known.
Always edit before you send
A saved reply is a starting point, not a robot. Read the customer's message all the way through, then adjust your reply to fit. Use their name. Answer the exact thing they asked.
Nothing annoys a customer more than a template that answers a different question. It tells them you didn't read their message, and they're usually right.
Staying kind when it's hard
Most customers are polite. A few will be short, stressed or flat-out rude. Often they're not mad at you. They're mad that something didn't work and they have a deadline and their kid is yelling.
Slow down before you reply
If a message makes your face hot, don't answer it right then. Step away. Get coffee. Come back in an hour. Your first draft of an angry reply is almost never the one you want on the record.
Answer the problem, not the tone
Look past the sharp words and find the actual issue. Then fix that.
If someone writes "This is garbage and I want my money back," you don't need to defend your work. Something like this works: "Sorry it didn't work out for you. I've processed your refund, and it should show up in a few days depending on your bank. If you're willing, I'd like to know what fell short so I can improve it."
You followed your refund policy, stayed polite and skipped an evening of arguing with a stranger.
Own your mistakes
If you messed up, say so plainly. "That's my fault. The link was broken. I've fixed it, and here's your file." People forgive mistakes fast when you admit them fast.
Keep it from taking over your life
Support should be a small, steady part of your week. If it's eating whole evenings, something upstream needs fixing.
A few ways to shrink the load:
- Add a simple FAQ. An FAQ is a list of frequently asked questions with answers. Put it on your sales page or in your delivery email.
- Improve your setup instructions. If people keep asking how to open the file, put clearer steps inside the product.
- Fix the product. If several people trip over the same thing, change the thing.
Also keep a simple log. A spreadsheet with the date, the question and what you did is enough. It helps you spot patterns and gives you a record if a dispute ever comes up.
Do this next
Answer the door, be decent, fix what's broken. That's most of customer support.
Veteran. Gen Xer. Thirty-plus years building things on the web. I write these so you can skip some of the expensive mistakes.