Multi-Vertical Outreach Routing: One Intake, Separate Tracks

Use one intake only for shared fields. Once a record enters a vertical program, route it to a distinct message track, owner, QA queue, and suppression state. Industry classification alone does not justify contacting someone; it is a routing input that must be paired with a relevant business signal and an allowed purpose.

Define the routing contract

At intake, capture source, organization, contact role, geography, purpose, consent or objection history where relevant, and the evidence supporting the vertical. The router should return a track and confidence value. If the data is missing or ambiguous, send the record to a review queue instead of a generic fallback sequence.

Each track should own its hypothesis, claims, template, sender identity, follow-up limit, and reply route. A global opt-out must suppress every track. A vertical-specific “not relevant” response may change routing, but it should not erase a broader objection. Test these cases with synthetic records before launch.

The FTC requires commercial messages to use truthful headers and a clear opt-out, and ICO guidance recommends do-not-contact screening for business objections [1] [2]. Keep the routing design aligned with those controls. RepMail can provide sending and suppression events; it cannot decide whether the source justifies outreach.

Run the router as a controlled queue

Treat routing as a decision with an audit trail, not as a permanent label. At intake, normalize the organization, contact, role, source URL, checked date, business signal, geography when relevant, purpose, suppression state, and reviewer. The router should write the selected track, rule ID, confidence or evidence note, owner, and review date. A missing role, conflicting company descriptions, stale source, or two equally plausible tracks goes to review. It must never silently fall back to a generic sequence.

Give each track a contract: approved audience definition, allowed claims, message version, sender identity, follow-up limit, reply owner, and escalation path. Before launch, test synthetic records for one clear match, no match, two matches, stale evidence, a global opt-out, and a vertical-specific objection. Confirm that a suppression written in one track is visible to every other track and to future imports. If a record changes companies or roles, re-evaluate the routing fields rather than carrying the old track forward.

For implementation, a RevOps owner can review the queue daily while each vertical owner approves its own evidence and copy. The system of record stores the decision and timestamps; the sender only receives records in the ready state. A record marked “not relevant to this track” can be reconsidered only under a documented rule, while a direct do-not-contact request remains a broad stop. Measure queue age, review outcomes, sends by track, cross-track duplicates, replies, positive replies, meetings, unsubscribes, and complaints. Investigate any send with no track or owner. Pair the routing SOP with the vertical ICP segmentation worksheet and the reply-rate measurement guide so the input definition and outcome denominator remain visible.

References

[1] https://www.ftc.gov/business-guidance/resources/can-spam-act-compliance-guide-business "FTC CAN-SPAM Act: A Compliance Guide for Business" [2] https://ico.org.uk/for-organisations/direct-marketing-and-privacy-and-electronic-communications/guide-to-pecr/electronic-and-telephone-marketing/electronic-mail-marketing/ "ICO Electronic Mail Marketing" [3] https://support.google.com/mail/answer/81126?hl=en-GB "Google Email Sender Guidelines"

Related resources

Continue with the related RepMail guide, the related RepMail guide, the related RepMail guide.

Related resources

Continue with the cold-email foundation guide, review the sequence quality checklist, and use the outreach academy when the workflow crosses into a neighboring concern.