Email delivery overview
Helpin Support can receive customer email and send replies. Receiving and sending are configured separately. Complete both parts before announcing a support address.
Receive customer email
A forwarding route gives you a Helpin inbound address. Keep the public address your customers know, such as support@example.com, and configure that mailbox to forward incoming messages to the Helpin address.
A route can send conversations to a specific inbox. Use separate routes when addresses such as support, billing, and partnerships should reach different teams.
Set up a forwarding route
Open Settings → Inboxes & routing.
Open Email Forwarding.
Create a route and select the destination inbox when required.
Copy the generated Helpin inbound address.
Configure forwarding with your existing email provider.
Complete the verification flow shown in Helpin.
Send a test message from an external address and confirm that the conversation reaches the expected inbox.
See Support email forwarding & routes.
Choose the sender customers see
Helpin chooses the sender according to the available configuration:
A sender configured for the conversation's inbox.
The workspace default sender.
A Helpin-managed sender when no verified custom sender applies.
A per-inbox sender is useful when different teams need distinct identities, such as product support and billing.
Send from your own domain
To use a custom sending domain:
Open Settings → Inboxes & routing → Sender Addresses.
Add the domain.
Publish the DNS records Helpin provides.
Wait until Helpin reports the domain as verified.
Add or select the sender address.
Send a test reply to an external mailbox.
The generated records can include:
DKIM for outbound message signing.
Return-Path for bounce processing.
DMARC guidance when your domain does not already publish a policy.
Do not remove required DNS records after verification. Delivery and bounce processing can stop working if the records are changed.
See Custom sender addresses & domains.
Delivery status
Email messages can report states such as sent, delivered, opened, or bounced when the provider supplies the corresponding events. A bounce or complaint can include a reason that helps you diagnose the problem.
Email fallback for chat visitors uses the configured sender rules. See Email channel & email fallback for offline visitors.
Test before launch
Use an address outside your company to test the complete path:
Send a message to the public support address.
Confirm that Helpin creates the conversation in the correct inbox.
Reply from Helpin.
Confirm the visible From address and Reply-To behavior.
Check SPF, DKIM, and DMARC results in the received message headers.
Test a bounce with a safe test address if your email provider supports it.
Troubleshooting
If inbound email does not arrive, check the forwarding rule and route verification.
If a reply uses the Helpin-managed sender, check custom-domain verification and sender selection.
If a message bounces, review the message status, recipient address, and domain DNS records.
If replies reach the wrong team, check the route's destination inbox and any routing rules.
Was this article helpful?