Bug Report Response
Templates for acknowledging, investigating, and resolving customer-reported bugs.
Bug Report Acknowledgment
Hi there,
Thank you for reporting this issue. I have logged it in our system and our team is looking into it.
To help us investigate faster, could you confirm a few details?
- What device/browser/OS are you using?
- When did you first notice the issue?
- Does the issue happen every time or intermittently?
- Are there any error messages displayed?
Your report reference is: {{clipboard}}
We will keep you updated as we make progress. Thank you for helping us improve.
Best,
{{cursor}}Bug Confirmed - Fix in Progress
Hi there,
Good news - our engineering team has confirmed the bug you reported and a fix is now in progress.
Here is what we know:
- Issue: [Brief description]
- Impact: [Who is affected]
- Expected fix timeline: [ETA]
We will notify you as soon as the fix has been deployed. In the meantime, here is a workaround you can use:
[Workaround steps]
Thank you for your patience and for helping us catch this.
Best,
{{cursor}}Bug Fixed - Deployed
Hi there,
I am happy to let you know that the issue you reported has been fixed and the update is now live.
What was fixed:
- [Description of the fix]
What you need to do:
- [Refresh the page / update the app / no action needed]
If you run into any further issues, please do not hesitate to reach out. We really appreciate you taking the time to report this - it helps us make the product better for everyone.
Best,
{{cursor}}Cannot Reproduce Bug
Hi there,
Thank you for the detailed report. Our team has attempted to reproduce the issue you described, but so far we have been unable to replicate it in our environment.
To help us dig deeper, could you provide:
1. A screen recording or screenshots of the issue
2. Your exact browser version (you can find this in your browser's "About" section)
3. Any browser extensions you have installed
4. Your internet connection type (Wi-Fi, Ethernet, mobile)
5. The exact steps you take before the issue occurs
This additional information will help us narrow down the cause. We want to make sure this gets resolved for you.
Best,
{{cursor}}Known Issue Acknowledgment
Hi there,
Thank you for reaching out. The issue you are experiencing is a known bug that our team is actively working to resolve.
Current status: [In progress / Scheduled for next release]
Expected resolution: [ETA]
Workaround:
[Steps for the workaround]
You can track the status of this issue on our status page at [URL]. We will also send you a notification once the fix is deployed.
We apologize for the inconvenience and appreciate your understanding.
Best,
{{cursor}}Bug Report - Need More Info
Hi there,
Thank you for reporting this. I want to make sure we address it properly, but I need a bit more information to investigate.
Could you help me with the following?
1. What were you trying to do when the issue occurred?
2. What did you expect to happen?
3. What actually happened instead?
4. Can you reproduce the issue consistently?
5. Any screenshots or error messages?
The more detail you can provide, the faster we can track this down. Thank you for your patience.
Best,
{{cursor}}Bug Report - User Error
Hi there,
Thank you for reaching out about this. After investigating, I believe the behavior you are seeing is actually expected, though I can understand how it might seem like a bug. Let me explain.
[Explanation of the expected behavior]
Here is how to achieve what you were trying to do:
1. [Step 1]
2. [Step 2]
3. [Step 3]
I have also attached a link to our help article on this topic: [URL]
If you are still experiencing unexpected behavior after trying these steps, please let me know and I will take another look.
Best,
{{cursor}}Bug Workaround
Hi there,
While our team works on a permanent fix for this issue, here is a workaround that should help you get past it:
Workaround steps:
1. [Step 1]
2. [Step 2]
3. [Step 3]
Important notes:
- [Any caveats or limitations of the workaround]
- This is a temporary solution until the fix is released
I know workarounds are not ideal, and I appreciate your patience. We are prioritizing this fix and will let you know as soon as it is deployed.
Best,
{{cursor}}When to use this template
- Initial bug acknowledgment within minutes of the customer reporting. Tells them you've seen it, sets investigation expectations.
- Mid-investigation update when you don't have a fix yet but want to prevent the customer from feeling forgotten.
- Resolution confirmation when you've shipped the fix. Includes 'here's what to do to verify on your end' so they don't have to ask.
Customize for your workflow
- Include a ticket reference number in every reply. Customers reference these in follow-ups, and it saves you searching by email.
- Match the bug template to your engineering process. If you use Linear or Jira, the snippet should produce the format your devs expect on the internal handoff.
Common questions
Should I commit to a fix timeline?
Only if you can keep it. 'We'll have an update by EOD Friday' beats 'we'll fix this soon' if you're confident about Friday. Otherwise stay vague rather than promise and miss.
What if the bug is actually user error?
Phrase it as 'here's the expected behavior' not 'you misunderstood'. Helps them save face and prevents the same misunderstanding in 50 future tickets.
Related reading
More Customer Support Templates
Failed Payment Response
Professional responses for handling failed payments, billing issues, and payment retry guidance.
15 snippetsTicket Escalation
Templates for escalating support tickets to senior agents, managers, or engineering teams.
10 snippetsRefund Request
Professional templates for processing, approving, and declining refund requests.
12 snippetsOnboarding Welcome
Welcome messages, setup guides, and first-steps templates for new customers.
18 snippetsFeature Request Response
Templates for acknowledging, tracking, and responding to customer feature requests.
10 snippetsAccount Cancellation
Retention-focused templates for handling cancellation requests with empathy and alternatives.
14 snippetsService Outage
Communication templates for planned maintenance, unexpected outages, and incident resolution.
9 snippetsFeedback Thank You
Templates for thanking customers who share feedback, reviews, or suggestions.
10 snippetsSatisfaction Survey
Follow-up templates for sending satisfaction surveys and collecting customer ratings.
13 snippetsUse these snippets in TypeFire
Download the template pack, drop the .md files into your TypeFire snippets folder, and start expanding with abbreviations instantly.