Every reply lands somewhere you can act on.

The replies your prospects sent are three folders deep.

Your ESP promised reply tracking. What you got was a forward to a shared inbox that filled up in a week, and a bounce classifier that flags every out-of-office as a hard failure. The replies your prospects actually sent are three folders deep — assuming they made it past the filter at all — and the addresses you now have suppressed as “bounced” are people who just took two weeks of leave.

Classify on the way in. Forward on rules you own.

Every inbound message is scored into one of four buckets the moment it arrives — reply, bounce, out-of-office, or unknown — and lands in the inbox for that rule with the classification and confidence recorded. Real bounces update your suppression list; out-of-office messages hold suppression until the return date the sender put in the message; genuine replies thread back to the outbound message that started the conversation.

Managed inboxes, classified as they arrive.

Forward to your own systems.

Every classified inbox can post inbound messages to an endpoint you own. Replies can land in the CRM record for the original recipient; bounces can update the record on your marketing platform; out-of-office messages can trigger a delay on the sequence step that produced them. The forward is signed and retried on the same contract as the outbound webhook stream, so your receiver can verify and dedupe with the same code it already has.

Every out-of-office is a contact you were about to lose.

When the classifier tags an inbound message as out-of-office, the Autoresponder Parser reads the body for the details that matter: the return date, the covering colleague, the alternative email address, the mobile number for urgent matters. Those fields land as structured data on the contact, so the next touchpoint reaches the right person on the right day — without a manual sweep of a shared inbox.