Set SoftReply up, and connect it to what you have.
Each guide is one job, in the order a new workspace meets them. The notes below them are why SoftReply works the way it does.
Guides
Keep your support address. Forward its mail to your mailbox's SoftReply address, and every message becomes a conversation.
Read the guide →Replies go out from the first day, from SoftReply's address. Connect your own Amazon SES account to send from yours.
Read the guide →One line in your page. Chats queue in the same inbox as your email.
Read the guide →The public board of what customers asked for, embedded in your own page, in your own colours.
Read the guide →Conversations, messages, notes, the files on them and your help centre, brought into SoftReply in three steps.
Read the guide →Send a website form into SoftReply, and file a roadmap request from your own system.
Read the guide →Let Claude, ChatGPT or your own agent read your inbox and draft replies. A person on your team sends every one.
Read the guide →Notes from the team
A named person approves every reply before it sends, and we think that constraint is the most valuable thing we ship.
Read the note →What residency actually means for a support inbox, where "EU region" stops being enough, and the concrete questions to put to any vendor.
Read the note →Get new essays in your inbox.
Occasional, and only when we have something worth your time.
Email us to subscribeOne email when a new piece is published. Unsubscribe anytime. No sharing, ever.