OOO parser with regex fields
Write extraction rules like 'contact ({name}) at ({email})' or 'until ({date})'. The parser runs against every OOO and writes structured rows into the list.
Read moreIndustries — Recruitment & Staffing
Every OOO reply is a lead. We turn them into a list.
Autoresponders from busy hiring managers routinely name the actual decision-maker. Capture them automatically.
OOO = the whole point
Recruitment & Staffing
Four sendrules capabilities mapped to the pain that defines this segment. Every one of them is on the free plan.
- OOO parser with regex fields
- Reply/bounce/OOO classification
- Webhook delivery
- Ignore list + suppression
The pain
What you deal with today.
Recruiters spend the day chasing hiring managers and candidates who are always in interviews. Their OOO replies say things like 'I'm out until Friday, please contact Sarah at [email protected] in the meantime' — pure gold for a recruiter, and completely invisible to any sequencing tool that just marks them as an auto-reply.
How sendrules answers
What changes when you route through us.
sendrules classifies inbound replies and runs your rule-based parsers over the OOO ones. The parser extracts the delegate address (plus any regex fields — name, phone, escalation contact) and writes it into a named list, delivered by webhook or CSV. Every OOO becomes a fresh contact.
The four capabilities
Feature per pain, not the other way round.
Reply/bounce/OOO classification
Inbound receive splits every reply into reply / bounce / OOO / other. Only OOO goes to the parser — reply goes to your ATS, bounce to suppression.
Read moreWebhook delivery
Each new list row fires an HMAC-signed webhook. Wire it into Bullhorn, Vincere, Loxo, or your own outreach tool — the contact is in your sequencer within seconds.
Read moreIgnore list + suppression
Never re-add a delegate you already have. Global suppression + per-list ignore rules keep your parsed contacts clean.
Read moreWhere it lands
Concrete scenarios you can wire in this week.
- Placement outreach with the parser building a 'covering hiring manager' list from every OOO reply that week
- Candidate re-engagement with the quality gate weeding out the stale addresses from your ATS
- Client outreach for retainer pitches with per-sender affinity so the same recruiter always follows up
- Multi-branch agency setup — one tenant per branch, each on their own domain and DMARC, one endpoint
- Weekly share-link report to hiring managers showing exactly which of their inbox mail landed
Also relevant
Other segments with similar shapes.
B2B SaaS
Transactional and product notifications across every provider you already pay for — with automatic failover.
E-commerce & Retail
Route Gmail buyers, Yahoo buyers, and Outlook buyers each through their best-fitting provider — from the same store.
Marketing Agencies & MSPs
Manage sending for thirty clients on their own provider accounts — one endpoint, per-client rules, no shared credentials.
Sales Development & Outbound
Verify every recipient in-line. Then parse every autoresponder reply for the person actually handling the account.
Real Estate & Lead Gen
Property inquiry mail flowing both ways — outbound quality-gated, inbound classified and parsed for the buyer's real coordinates.
Financial Services
Statements, alerts, and regulator-facing correspondence with DMARC monitoring, signed webhooks, and a full audit log.
Recruitment & Staffing teams start on the free plan.
Five thousand messages a month. Every feature above included. Attach your existing provider and see whether the numbers move.