How to run customer support as a solo founder without it eating your week
By The Relay team · Published · 4 min read
The short answer
Run support from one inbox, in one or two fixed windows a day, with four statuses so you always know what's waiting on you. Turn every question you answer twice into a help article, put the articles behind a search box and a bot, and keep a human path open. This is a method, not a case study: it's what the product is designed around, and you should adapt it to your own volume.
The three-part setup
- One inbox. Chat and email both land in one place. If you have to check three tools, you will skip one.
- One help center. Every question you answer twice becomes an article. This is the only thing that makes support get smaller as you grow.
- One or two fixed windows a day. Support is interruptive work; batch it. Tell customers when to expect a reply.
Set expectations once, in writing
Customers are patient when they know what to expect and angry when they don't. Say it where they ask: "We reply within a working day" in the widget greeting and your email signature. Under-promise. A reply that arrives early beats an apology.
Use four statuses and clear the open view
Open means you owe them. Pending means they owe you. Resolved means done. Your only daily job in the inbox is to take the open count to zero. See support ticket statuses explained. A keyboard-driven inbox makes this fast: move, reply, resolve, next.
Write the answer once
- First time: answer the customer by hand.
- Second time: write a help article, answer with its link, and keep a saved reply that points to it.
- Third time: it shouldn't reach you. The help center search or the bot should have answered, and if it didn't, fix the article's title or first paragraph.
Saved replies are for the human tone that surrounds an answer ("Thanks for flagging this"); articles are for the answer itself. Keep both short. For the article-writing rules, see how to train an AI chatbot on your help center.
Decide what to automate and what not to
| Automate | Keep for you |
|---|---|
| How-to and where-is-it questions | Refunds, double charges, cancellations |
| Login and password help | Bugs, outages and anything marked broken |
| Plan and pricing questions | Angry or upset customers |
| Install and setup steps | Feature requests worth a real conversation |
Close the loop with the product
A solo founder has an advantage no support team has: you are also the person who can fix the cause. Tag what you answer, and each week look at the top two tags. The best way to reduce support is to change the product so the question stops being asked. The four-week method for reducing tickets shows how.
What it costs
Relay Pro is $19 a month for 3 seats, with the widget, inbox, help center, AI answers, email channel and feedback board included. There is no free plan or trial, so try the live demo first. If you only need a basic inbox, several tools have free plans, and the pricing index lists them.
Questions
Common questions
- How much time should a solo founder spend on customer support?
- It depends on volume and stage. A fixed window once or twice a day keeps it from fragmenting your day. Tagging what you answer shows which questions to turn into articles, which is how the time shrinks.
- What tool should a solo founder use for customer support?
- Something with one inbox for chat and email, a help center, and a way to hand off from a bot. If you only need an inbox, free plans on Help Scout, Chatwoot, Crisp and Tidio are worth trying first. Relay is built for this case, at a flat price, with no free plan.
- Should I use a chatbot as a solo founder?
- A bot that answers from your own articles and hands off cleanly can take repeat questions off your plate. It needs good articles first, and a visible way to reach you.
- When should I hire my first support person?
- There is no universal number. Watch for open conversations that stay open past your promised reply time, and for support taking more hours than you can spare from building. Before hiring, check how many tickets articles could remove.
Sources and how we wrote this
Relay is made by the team that wrote this post. Figures for other tools come from their own public pages, listed under Sources, and are list prices in US dollars that can change. If something here is out of date, tell us on the feedback board and we'll correct it.