Every autoresponder is a contact list. We parse them for you.
Ten to twenty percent of campaign replies are autoresponders — most carry the exact contact info you were trying to reach. sendrules extracts them into named lists you can trigger a webhook from or download as CSV.
Your best campaign lead is buried in a bounce folder.
The out-of-office reply says the contact is on leave until the 14th, hands you the assistant’s address, the alternate contact’s address, and a mobile number. Your ESP tags the message as a bounce and drops it in a reply inbox that nobody has opened in a month. The lead ages out. The campaign closes. Next quarter you pay to source the same contact again.
sendrules classifies every reply, runs your parser rules against the out-of-office ones, and drops the extracted contacts into a named list — ready for your CRM to pick up before the campaign is over.
Every OOO reply is a contact. Most senders throw them away.
Ten to twenty percent of campaign replies are autoresponders — and most of them carry the exact contact info you were trying to reach: “I’m on leave until Monday, please contact [email protected] for procurement questions.” sendrules parses every one, harvests every address, captures every named field, and drops the result into a list you can trigger a webhook from or download as CSV.
- Harvest emailsEvery address inside the body is extracted — new colleagues, forwards, referrals, procurement contacts.
- Named field captureRegex rules pull structured data — a name after 'Please contact', a phone number, an alternate ID.
- Ignore listSkip your own domain, common noise, and addresses you already have. Nothing duplicated, nothing polluted.
- Webhook or CSVPush new contacts into your CRM in real time, or download the list on demand.
Thanks for your note — I’m on parental leave until 15 January 2026. For procurement, please reach [email protected]. Legal + contracts: [email protected] (direct: +44 20 7946 0123).
- [email protected]procurement
- [email protected]legal
- [email protected]on leave
{
"event": "parser.contact",
"list": "acme-warm",
"email": "[email protected]",
"fields": {
"role": "procurement",
"return_date": "2026-01-15"
},
"source_msg": "01f9...abcd",
"ts": "2026-11-04T08:14:32Z"
}Rule-based, not a black-box classifier.
A parser is a named rule attached to an inbox or to the whole tenant. You pick what to extract — every email address in the body, or specific captures under field names you choose (return date, alternate contact, phone). Ignore rules skip your own domain, common no-reply patterns, and known-noise addresses. Contacts dedupe per parser, land in a named list, and can leave via signed webhook or CSV.
Runs on every classified out-of-office — nothing extra to invoke.
The parser runs automatically when the inbound classifier tags a message as out-of-office. No separate ingest, no manual review queue. Extracted contacts show up in your list within seconds, and any webhook you have registered gets a signed event per new contact.