Paste any message. Pick a context and tone. Get 3 ready-to-send replies, free.
Four common situations and the kind of reply this tool writes for each, from a quick work email to a sales inquiry.
A customer asking whether a feature is included in their current plan.
"Does your Pro plan include API access, or do I need to upgrade further?"
Great question. API access is included on the Pro plan, no upgrade needed, you can generate a key from Settings > API. Let me know if you'd like a hand setting up your first request.
A colleague asking if a deadline can move.
"Any chance we could push the Friday deadline to Monday? Still finishing QA."
Monday works on my end. Let's plan for end of day Monday so we still have a buffer before the release. Ping me if QA turns up anything that needs a bigger conversation.
A friend checking on weekend plans.
"Are we still on for Saturday or did that fall through?"
Still on. Does 1pm still work for you, or is there a better time now?
A prospect asking about pricing before a call.
"Can you send pricing before we book a call? Want to make sure it's in range first."
Happy to. Plans start at [price] and scale with usage, I'll send the full breakdown over now. If it's in range, grab a time that works here: [link], and we can dig into your specific setup.
The tool applies these automatically. Written out, they work just as well typed by hand.
Whatever else the reply covers, the first sentence should address what was actually asked, not a side detail.
A casual message deserves a casual reply. Mirroring the sender's register reads as attentive rather than automated.
If you need something from them, name exactly what and by when, rather than a vague "let me know."
End with what happens next, and who does it, instead of trailing off after answering the question.
For a support inbox, that means every incoming message gets read, answered, and acted on, not just drafted, then handed off to your team only when a person is genuinely needed.