Out-of-office parser with pattern fields
Write extraction rules like 'contact {name} at {email}' or 'until {date}'. The parser runs against every out-of-office reply 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.
- Out-of-office parser with pattern fields
- Reply, bounce, and out-of-office classification
- Webhook delivery
- Ignore list and 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 parsers over the out-of-office ones. The parser lifts the delegate address, plus any pattern-matched fields — name, phone, escalation contact — and writes them into a named list, delivered by webhook or CSV. Every out-of-office becomes a fresh, sequenceable contact.
The four capabilities
Feature per pain, not the other way round.
Reply, bounce, and out-of-office classification
Inbound receive splits every reply into reply, bounce, out-of-office, or other. Only out-of-office reaches the parser; replies go to your ATS, bounces go to suppression.
Read moreWebhook delivery
Each new list row fires a signed webhook. Wire it into Bullhorn, Vincere, Loxo, or your own outreach tool — the contact is in your sequencer within seconds of the reply landing.
Read moreIgnore list and suppression
Never re-add a delegate you already have. Global suppression plus per-list ignore rules keep your parsed contacts clean and your sequences on-topic.
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 out-of-office reply that week
- Candidate re-engagement with the quality gate quietly weeding stale addresses out of your ATS as you send
- Client outreach for retainer pitches with sender affinity so the same recruiter always follows up on the same conversation
- Multi-branch agency setup — one tenant per branch, each on its own domain and DMARC posture, 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.