Free founder toolkit
Customer support email templates for startups
Six practical starting points for the conversations founders handle every day. Choose a situation, edit the reply, and copy it into your email or chat tool. No account required.
Drafts stay in this browser tab; we do not save or send their text. Your browser may preserve them when you navigate back. We measure template edit/copy events, never your draft text. These are written templates, not AI-generated answers; nothing is sent to a customer.
Before you send
- Replace every [bracketed placeholder] and remove optional lines you do not need.
- Check facts, product steps, and account permissions. Only promise a fix, refund, or update time if it is confirmed and you can deliver it.
- Read the customer's original message again. A useful reply answers their question, explains the next step, and sounds like a person.
REPLY 01
Acknowledge a bug report
Use this when a customer reports broken behavior but you have not yet reproduced it. Acknowledge the impact without calling the issue confirmed.
Check first: Keep only the diagnostic questions you still need. Ask for redacted screenshots, never passwords, API keys, payment details, or a full customer database.
REPLY 02
Respond to a feature request
Use this to understand the problem behind a requested feature before discussing a roadmap. A request is feedback, not a delivery commitment.
Check first: Do not say a feature is planned unless that is confirmed. If you suggest a workaround, test it in the customer's setup first.
REPLY 03
Send an investigation update
Use this when an issue is still open and the customer needs an honest status update. Separate verified facts from the next step.
Check first: Replace every status placeholder with something verified. Only include a workaround if it is safe, and a next-update time if someone owns that commitment.
REPLY 04
Follow up after a fix
Use this after a fix has actually shipped and you have checked the affected workflow. Invite the customer to verify their own result.
Check first: Confirm the release is live for this customer. Do not equate a code merge with deployment, or ask them to clear data unless that step is necessary and safe.
REPLY 05
Help a customer get started
Use this when a new customer is stuck on one task. Offer one clear path instead of sending an entire help center.
Check first: Check the steps against the current product and the customer's access. Use an official help link and explain what success looks like.
REPLY 06
Acknowledge a billing question
Use this to clarify a charge or billing question before promising an outcome. Keep refunds, credits, and cancellation decisions with an authorized person.
Check first: Verify identity through your established process before discussing account details. Do not request full card numbers, security codes, or payment credentials in a support message.
Make templates part of a better support workflow
A reusable reply helps with wording; it does not track the conversation for you. Keep the original report, the owner, and the next action together. When another teammate takes over, they should be able to see what was already asked and what you committed to do.
For website conversations, tkit.ai brings a live chat widget and a shared inbox into your team's workspace. You can use these replies as starting points while your team follows up with customers. Read the widget installation guide or follow the founder-led support workflow.
Create a tkit.ai account