The Quick Answer
✅ If you're sending email through TNZ, delivery status is tracked (including bounces), and email replies are sent to your normal email inbox.
When you send an email using TNZ, the email is sent from "yourinbox@yourdomain.com" - the recipient will email you back directly.
If an email bounces, the bouncing email server will report the bounce directly to TNZ and will be made available in reporting and webhooks.
How Email Replies Work on TNZ
When you send an email through TNZ, the FROM header is set to your email address, not a TNZ address. That's deliberate. It means:
- The recipient sees your address on the message.
- When they hit Reply, their mail client sends to your address.
- The reply is routed by DNS to your domain's primary MX record, landing in your mailbox or mail server.
- TNZ is not in the path. We don't see or log the reply.
There's no email reply webhook to subscribe to. There's no inbound email infrastructure on the TNZ side to fire one. The reply is in your inbox the moment it arrives.
What is Supported on Email Webhooks
The TNZ email service reports on outbound results in detail:
- Delivery success webhooks: fired when the receiving mail server accepts the message (typically an SMTP
250 OK).
- Delivery failure webhooks: fired when the receiving server rejects the message (e.g.
550 No Such User, 552 Mailbox Full, SPF/DKIM/DMARC failures).
- Automatic bounce tracking: soft bounces (initial
250 OK followed by a later bounce notification) are caught and the result is updated. You don't need to parse bounce emails yourself.
- Result code detail: webhook payloads include the SMTP code or TNZ-internal reason. See the Email Delivery Result Codes guide.
For payload format, retry semantics and configuration, see the REST API webhook spec and the Configuring API Webhooks guide.
What is Not Supported
- Inbound email webhooks: not offered; recipients reply directly to your mailbox.
- Forwarding replies to a third-party endpoint via TNZ: if you need replies routed somewhere other than your normal mailbox, you can change your From address in TNZ to match.
Email vs SMS: Why the Difference
TNZ supports inbound SMS webhooks but not inbound email webhooks because of where the receiving infrastructure lives.
| |
SMS |
Email |
| Receiving infrastructure |
TNZ manages the mobile number; the carriers route inbound SMS to us. |
Your domain owns the MX record; the receiving mail servers route replies to your mail host. |
| Inbound webhook available? |
Yes. See Configuring API Webhooks. |
No. Replies don't pass through TNZ. |
| Delivery status webhook available? |
Yes. |
Yes, including automatic bounce tracking. |
Practical Setup
1. Set the right FROM address on your TNZ user
The FROM address used by TNZ is set against your TNZ user. Make sure it points to a mailbox you actually monitor. See Adding a New Email Address for Sending.
2. Configure delivery webhooks
To capture send results and bounces in your own system, configure a webhook callback URL in the dashboard or pass WebhookCallbackURL on each send. Details in Configuring API Webhooks.
3. (Optional) Route replies on your side
If you want replies handled by a ticketing system, helpdesk or automation tool, set that up on your mail server. Examples: a shared inbox, a Microsoft 365 rule, a Gmail filter forwarding to a webhook endpoint, or a tool like Zapier's Email Parser.
FAQ
Can I set TNZ as the FROM and have replies come to TNZ?
No. TNZ doesn't accept inbound email, so even if a TNZ-controlled FROM was used, the reply would have nowhere to go. Keeping your own address as the FROM is the right answer. Recipients reply directly to you.
|
How do I know if an email bounced?
Bounces are processed automatically. The Result field on the message will update to reflect the bounce, and a delivery-failure webhook fires if you've configured one. Soft bounces (where the receiving server initially accepted the message and later bounced it) are caught and reflected in the same way.
|
Can TNZ forward replies to my CRM or helpdesk?
Not via TNZ, because we never see the reply. Set up an email address to receive these replies, and use it in the From field in TNZ.
|
Will SPF, DKIM or DMARC issues affect replies?
SPF/DKIM/DMARC are outbound authentication controls. They affect whether your TNZ-sent emails get accepted by the recipient's server. Replies travel in the opposite direction and are governed by your own domain's MX configuration. See Email Delivery Result Codes for outbound deliverability detail.
|
For the SMS-side analogue, see Configuring SMS Reply Email Notifications. That article covers how SMS replies (which TNZ does receive) can be emailed to you.