Log in
Documentation menu

How replies work

Reply as you normally would. Waribox sends it to the right people.


When a contact writes

Every confirmed member gets a copy in their own inbox. The copy’s Reply-To is a special address for this conversation, such as support+t_k3v9x2m7q1ab@mail.waribox.app. That code is how Waribox knows which conversation a reply belongs to, so leave it in place.

When a member replies

Just press Reply. The reply goes to the contacts in the conversation, from the pipe’s address, and every other member gets a copy so the team knows it has been answered. You don’t get a copy of your own reply.

If a teammate answered the same message a few minutes before you, your reply may be held instead of sent. See Hold duplicate replies.

A member who writes to the pipe’s address outside a conversation reaches only the other members. This is handy for an internal note.

Conversations

When someone new writes into the conversation, for example a colleague the contact copied who then replies, they join it and get later replies too, up to 20 people. If a contact’s mail app replies to the pipe’s address instead of the Reply-To, Waribox still finds the conversation from the message’s headers.

A conversation is forgotten after 90 days without activity. A later message then simply starts a new one.

Sender names

In the pipe’s settings, choose the name people see on mail from the pipe. For a message written by Jane Doe through a pipe named Support:

  • Jane Doe via Support: who wrote it, and through which pipe. The default.
  • Support: only the pipe name, so every message looks like it came from the team.
  • Jane Doe: only the person who wrote it.

The address is always the pipe’s, so replies come back through Waribox whichever you choose.

NextSend as your own domain