"We Have a Compliant Process" Is Not a Consent Record
Ask most staffing BD teams whether their outreach is TCPA-compliant and the honest answer is a general belief, not a specific, retrievable record. That distinction matters more than it sounds like it should. If a complaint or a suit ever arrives, "we believe our process was compliant" is a weak position. A specific, dated record for the exact contact in question is a fundamentally different one.
The Three Things a Defensible Record Actually Needs
When consent was given, for what type of contact, and from what number, that is the shape of a record that holds up. Not a general company policy document sitting in a compliance folder, a specific, retrievable entry tied to the exact prospect and channel being questioned. A staffing firm calling and texting dozens or hundreds of hiring managers a week needs this tracked per contact, not asserted in the aggregate.
SMS Carries the Same Consent Bar as Calls
This is the point most worth being precise about, given how much staffing BD is layering text messages into its cadences. Compliance-industry sources describe TCPA coverage of wireless numbers as applying "regardless of whether the recipient is a consumer or a business contact," and that coverage extends to calls and texts alike, per the same research. A staffing BD team that shifted part of its cadence to SMS specifically because it felt like a lower-friction, lower-risk channel is working from an inaccurate assumption. Texting is not a compliance workaround for the consent requirements calling already carries, it is a channel that carries its own version of the same requirement.
Why Multichannel Cadences Complicate This Further
A working staffing BD cadence, per the companion cadence guide, layers call, email, and LinkedIn touches over roughly two to three weeks. Each channel carries a different consent posture: email consent rules differ from TCPA's wireless-number coverage, and LinkedIn outreach sits outside TCPA entirely, while calls and texts share the same wireless-number standard. A single "we have consent" record that does not specify which channel it covers is not actually a record for any of them individually. Track consent per channel, not as one blanket assumption covering a whole multichannel sequence.
How VA Horizon Documents Consent on Every Booked Meeting
Every staffing conversation VA Horizon runs happens over SMS, between a Human + AI SDR and a prospect who opted into that conversation, built natively on the VA Horizon Private CRM. The full exchange is preserved as a transcript, and every booked, double-confirmed meeting ships with a 24-hour, 2-hour, and 15-minute confirmation log alongside it. That is a specific, retrievable, channel-specific record for every contact, the shape of documentation this guide describes as defensible, not a general assurance that the process is sound.
What this means for you
- A defensible consent record needs three specific things: when consent was given, which channel it covers, and what number it applies to, not a general policy statement.
- TCPA wireless-number coverage applies to texts the same way it applies to calls, per the research behind this guide. SMS is not a lower-risk compliance workaround.
- A multichannel BD cadence needs consent tracked per channel. A single blanket "we have consent" claim does not cover calls, texts, email, and LinkedIn equally, since each carries a different legal standard.
- VA Horizon's SMS-based model documents consent per contact by default: every booked meeting ships with a transcript and a structured confirmation log.
Sources
The external data in this guide draws on the sources below. Figures described in the text as estimates or industry triangulations are directional and are not attributed to a single dataset.
- Callshaper, B2B telemarketing compliance guide (2025)
- Haley Marketing, "Is Cold Calling Still Effective for Staffing Agencies?"