Draft customer support replies faster with Crade
Crade reads the ticket on your screen and drafts a reply that addresses the actual issue, in the right tone, with the right next step. You stay in the loop on what to send.
Hi,
I signed up for the Pro plan over a month ago and honestly, I just can't get the integration to work the way our marketing team needs it. We've tried customer support twice and it's still missing key features for our workflow.
Can I get a refund please? I think we're going to look at a different solution that fits us better. I know it's past 30 days but the issue is your product, not us changing our mind.
Thanks,
Maria
Draft a reply. User is asking about a refund. Empathetic but firm — policy is no refunds after 30 days.
Hi Maria, Really sorry the workflow didn't end up being what you needed . I can hear the frustration. I checked your account and the purchase was on April 12, which puts us just past our 30-day refund window. I'm not able to issue a full refund at this point, but here's what I can do: . Apply a 50% account credit for your next month (no expiry) . Walk you through the integration that was tripping things up . often a 15-min screen-share is faster than written back-and-forth Let me know which works, or if there's something else I can help with. . Tom Customer Success, Acme
Support is volume work. The bottleneck is not writing. It is reading. Each ticket needs you to figure out what the user actually wants (often not what they wrote), find the right answer, and respond in a tone that matches the situation. Crade reads the ticket on your screen and drafts a reply that solves all three problems at once.
What you put on your screen
- The customer ticket in your support tool (Zendesk, Intercom, Help Scout, Front)
- The customer's full message thread if there is back-and-forth
- Any internal notes from previous agents
- Your knowledge base or docs in another window if you want Crade to pull canonical answers
What you say to Crade
Specify the tone and the policy. Crade reads the ticket for what they actually want and shapes the answer accordingly.
What you get back
- A reply that addresses the real issue (often different from the stated complaint)
- Empathy that does not sound scripted
- The actual answer or next step, clearly stated
- A polite but firm tone where needed (refunds, abuse, edge cases)
- A short close that leaves room for follow-up if needed
Tips for better support replies
- Tell Crade the policy upfront. "No refunds, but we offer credit." Sets the boundary.
- Ask Crade to identify the real issue first: "What is this person actually asking?". Often surfaces something hidden in their message.
- For angry customers, ask for the de-escalation version. "How do I respond without making this worse?".
- Reuse approved templates by pasting them on screen. Crade adapts the template to the specific ticket.
- For technical issues, include the user's debug info or environment in your prompt. Crade tailors the answer.
Frequently asked questions
Does Crade send the reply for me?
No. Crade drafts; you review and send. Support replies have brand and legal weight, so the human-in-the-loop boundary matters.
How does Crade compare to canned responses?
Canned responses are fast but generic. Crade is fast and specific. It reads the actual ticket and writes the reply that fits it. For repeat issues, canned responses are still faster; for one-off issues, Crade wins on quality.
Can Crade integrate with my support tool?
Not directly. Crade reads what is on screen, so it works with any tool. You copy the reply into the support tool yourself.
What about multi-language support?
Crade reads tickets in any major language and replies in whatever language you specify. "Reply in German" works.
Can Crade escalate tickets it cannot handle?
Crade does not have integration with your routing rules, so escalation is on you. But Crade flags tickets that look unusual: "This sounds like a security report, you may want to route to your security team."
The whole loop in one sentence
Ticket on screen, one prompt with the tone and policy, reply ready to send. Support volume becomes a writing problem, not a reading problem.
Most of the time spent on email is not the typing. It is the reading. Crade reads the thread on your screen, gets the actual ask, and drafts a reply you can send or tweak. Here is exactly how it works.
An email you typed too casually. A Slack message that came out blunter than you meant. A first draft that lacks polish. Crade reads what you wrote and rewrites it cleaner without losing your voice.
Crade reads the person's profile on your screen and drafts a cold message that mentions something specific from their work. Not generic outreach.