Every SaaS ships bugs. The customers who churn over bugs aren't the ones who hit them - they're the ones who felt ignored while they waited.
The three-line reply
A great support reply has three lines and only three:
- Acknowledge with specificity. Name the exact thing that broke, in their words. "The filter chips reset on refresh" beats "the issue you mentioned."
- Set the next update time. Not a fix ETA - a next-update time. "I'll come back to you by end of day Thursday."
- Ask for the one missing thing. Not a form. Not "please provide more details." The one specific thing you actually need.
Why "please provide more details" is the killer
It puts the work back on the customer, who is already frustrated. It's the enterprise equivalent of "have you tried turning it off and on again."
The triage tell
If your first reply doesn't include a severity call the customer can feel (not the S1-S4 number, the treatment), the customer assumes S4 and starts looking at competitors.
Draft yours with the Bug Report Triage tool.