Email

Every help desk has an inbound address like [email protected] (Settings, Channels). There are three ways to get email in.

1. Forward your support address

In your mail provider, forward [email protected] to your inbound address. Keep a copy if you like. Add the support address as the brand’s from address (Settings, Brands) so replies go out from it.

2. An inbound email provider

Create an inbound webhook source in Settings, Channels. It gives you a private URL like /inbound/email/in_.... Point your provider’s inbound parse at it. These formats are understood:

Provider formatHow it arrives
SendGrid Inbound Parsemultipart form: from, to, cc, subject, text, html, headers, attachments, or the raw message in "email"
Mailgun routesmultipart form: sender, recipient, subject, body-plain, body-html, Message-Id, In-Reply-To, References, message-headers, attachment files, or body-mime
Postmark inboundJSON: FromFull, ToFull, CcFull, Subject, TextBody, HtmlBody, Headers, Attachments
Raw MIMEa message/rfc822 body, or JSON with a raw field (raw_encoding base64 if encoded)
Generic JSON{ from, to, cc, subject, text, html, headers, attachments: [{ filename, content (base64), contentType }] }

Ignored messages (auto replies, bounces, loops, duplicates) answer 200 so providers do not retry them.

3. IMAP polling

For mailboxes that cannot forward, add an IMAP mailbox (server, port 993, user name, password). HelpBat checks it every two minutes for new messages and marks them read. The password is encrypted at rest. TLS is required.

Threading

Replies join the right ticket using, in order:

  1. Our own Message-ID in In-Reply-To or References (each reply we send carries the ticket in its Message-ID).
  2. Any earlier Message-ID of the ticket in those headers.
  3. The [#123] tag in the subject, when the sender is that ticket’s customer or a cc.

Otherwise a new ticket opens. Replies to a closed ticket open a linked follow up. Quoted history ("On ... wrote:") is cut off, and the line ##- Please type your reply above this line -## marks where it starts.

Sending

Replies go out from the brand’s from address and name, with In-Reply-To and References, the agent’s signature, attachments and a link to the request in the portal. Delivery runs through an outbox with retries. There is a short undo window after you press send.

To send from your own domain without landing in spam, add the SPF and DKIM records your email provider gives you for that domain. Sandbox workspaces never send real email.

Attachments

Images, PDFs, text, CSV, Office files, zip, audio and video are accepted up to 20 MB each. Other types are skipped with a note on the ticket. Inline images show in the message.