Skip across the chapter
Quota Playbook

SDR outreach checklist: 6 checks before setting targets

Quota Playbook Editorial Team · Published · 12 min read

Before setting SDR outreach expectations, managers should check applicable calling restrictions, SMS classification and registration, recipient suppression and Canadian consent evidence.

SDR outreach checklist: the checks before setting targets

The six checks separate channel-specific legal and technical constraints from general activity goals. Managers must verify call eligibility, timing, opening and exit protocols, message classification, SMS registration and suppression, and Canadian consent evidence before assigning targets.

Key takeaways: what managers should check before setting SDR outreach expectations

  • Verify call eligibility before assigning targets. Confirm whether your team’s specific prospecting calls fall within the scope of Washington’s telephone solicitation rules, which apply to covered solicitations rather than every business call.
  • Enforce strict timing and exit protocols. For covered calls, reps must identify themselves and their purpose within the first 30 seconds and end the call within 10 seconds if the recipient indicates they want to stop.
  • Classify SMS traffic correctly. Under the Twilio Messaging Policy | Twilio, all messages transmitted through their services are treated as application-to-person (A2P) traffic, regardless of content.
  • Prohibit person-to-person messaging. The same policy explicitly prohibits transmitting person-to-person (P2P) messages through Twilio Messaging Services, even if the conversation appears to be a two-way exchange between two humans.
  • Distinguish channel rules from activity quotas. Channel restrictions define what is permitted and how it must be executed; they do not establish safe daily activity quotas or guarantee compliant outreach outcomes.

Before assigning calls: Washington scope, registry and timing

Check whether your team’s prospecting calls fall under Washington’s definition of telephone solicitation before setting daily activity targets. RCW 80.36.390 defines this term as the unsolicited initiation of a telephone call by a commercial or nonprofit company or organization to a person for the purpose of encouraging the person to purchase property, goods, or services, wrongfully obtaining anything of value, or soliciting donations of money, property, goods, or services, according to the Washington State Legislature. Do not assume every B2B call falls within this scope; verify the specific purpose of the call against this definition. If the call matches the definition, you must check the recipient’s number against the federal do-not-call registry. No person may initiate, or cause to be initiated, a telephone solicitation to a telephone number registered on the do not call registry maintained by the federal government pursuant to telephone consumer protection act, 47 U.S.C., as stated by the Washington State Legislature. This registry bar applies to covered solicitations, so your team must screen numbers before dialing.

Timing restrictions also apply to covered calls. A telephone solicitor shall not place calls to any person which will be received before 8:00 a.m. or after 8:00 p.m. at the call recipient's local time, according to the Washington State Legislature. This requirement uses the recipient’s local time, not the caller’s time zone. When setting expectations for a team that calls across different time zones, ensure reps understand they must adjust their dialing windows based on where the recipient is located. The following table summarizes these three specific checks for solicitation calls to Washington recipients.

Check Item Publisher Requirement Detail
Call eligibility Washington State Legislature Unsolicited initiation of a telephone call by a commercial or nonprofit company or organization to a person for the purpose of encouraging the person to purchase property, goods, or services, wrongfully obtaining anything of value, or soliciting donations of money, property, goods, or services
Registry restriction Washington State Legislature No person may initiate, or cause to be initiated, a telephone solicitation to a telephone number registered on the do not call registry maintained by the federal government pursuant to telephone consumer protection act, 47 U.S.C.
Timing window Washington State Legislature A telephone solicitor shall not place calls to any person which will be received before 8:00 a.m. or after 8:00 p.m. at the call recipient's local time

Review your team’s current dialing lists and confirm that all numbers have been screened against the federal registry. Verify that your dialing software or process enforces the 8:00 a.m. to 8:00 p.m. local time window for recipients in Washington. If your team does not make unsolicited calls for the purposes defined in the statute, these specific Washington restrictions may not apply, but you should still document that determination.

During outreach: call openings, exits and message classification

When a rep picks up the phone for a covered solicitation, the first thirty seconds set the tone for compliance. Under RCW 80.36.390, the person making the call must identify themselves, the company or organization on whose behalf the solicitation is made, and the purpose of the call within the first 30 seconds of the telephone call Washington State Legislature. This requirement applies specifically to telephone solicitations as defined by that statute. Managers should ensure their scripts and coaching notes reflect this timing constraint so reps do not spend the initial window on pleasantries or lengthy introductions that delay the mandatory identification.

Equally critical is the exit protocol. If, at any time during the telephone contact, the called party states or indicates they want to end the call, the telephone solicitor must end the call within 10 seconds Washington State Legislature. This is not a suggestion to pause or ask for clarification. A rep who hears "no thanks" or "stop calling" must end the call within 10 seconds of that signal. Training should focus on recognizing verbal and non-verbal cues that indicate the recipient wants to stop, and reps must practice ending the call cleanly without attempting to override the request.

For SMS and messaging channels, the rules differ significantly from voice calls. Twilio treats any and all messages transmitted through the Twilio Messaging Services as non-consumer or application-to-person (A2P) messages, regardless of the actual content of the message or the type of message recipient Twilio. This classification applies to every message sent through their platform. You are prohibited from transmitting person-to-person (P2P) messages through the Twilio Messaging Services Twilio. P2P messaging is generally defined as a two-way (back and forth) messaging conversation between two humans Twilio. Therefore, a human-to-human conversation does not establish permission to use person-to-person traffic through Messaging Services. All traffic there is treated as application-to-person. For a related guide on texting limits, see Check 5 text-message caps before a seller texts a buyer.

Action Step Publisher Specific Constraint
Identify caller, organization, and purpose Washington State Legislature Within the first 30 seconds of the telephone call
End call upon recipient request Washington State Legislature Within 10 seconds of indication to stop
Classify message traffic Twilio All messages are application-to-person (A2P)
Prohibit P2P transmission Twilio Person-to-person messages are prohibited

Review your team's messaging platform documentation to confirm whether it follows similar A2P classification rules. If your reps are using Twilio, ensure they understand that even casual-looking messages are subject to A2P regulations. Do not assume that a friendly tone converts a message into P2P traffic; the platform's technical classification governs the compliance requirement.

When your team targets Canadian recipients, verify the consent basis before assigning message volume. Implied consent is only recognized in certain circumstances under subsection 10(9) of CASL, according to Innovation, Science and Economic Development Canada. Do not assume a business contact implies permission for all future outreach. If you rely on an existing business relationship for implied consent, you must ensure the message is sent within the appropriate time frames defined in subsection 10(10) of CASL.

Beyond anti-spam rules, businesses must comply with both CASL and PIPEDA. This requires familiarity with PIPEDA’s Fair Information Principle 3, which covers Consent and Guidelines for meaningful consent. Your documentation should reflect both obligations. If asked, senders should be ready to provide proof of this consent. Record the specific basis for each recipient’s consent and the supporting evidence in your activity log. For a related email check, see Check these 10 CAN-SPAM lines before the sales email.

Consent Type Publisher Evidence Requirement
Implied consent Innovation, Science and Economic Development Canada Certain circumstances under CASL subsection 10(9)
Business relationship Innovation, Science and Economic Development Canada Appropriate time frames under CASL subsection 10(10)
Privacy consent Innovation, Science and Economic Development Canada PIPEDA Fair Information Principle 3
Proof of consent Innovation, Science and Economic Development Canada Ready to provide if asked

Review your current consent records against these four categories. Identify any gaps where the basis or timing is unclear. Update your team’s expectation sheet to require this evidence before any Canadian campaign launch.

Publisher reference table for registration and channel restrictions

Use this table to verify the specific registration and suppression mechanics documented by Close for its A2P 10DLC feature.

Publisher Registration/Channel Rule Source Page Title
Close Registration is approved by a 3rd party board, namely the Campaign Registry A2P 10DLC - Close Help Center
Close If your account is already approved for A2P 10DLC, any new numbers you buy will be automatically added to your approved campaign A2P 10DLC - Close Help Center
Close The process can take up to 24 hours, as the change has to propagate across several stakeholders/carriers A2P 10DLC - Close Help Center
Close Future attempts to message a blocked recipient will fail with Error Code 21610 because the customer has replied with STOP A2P 10DLC - Close Help Center

Confirm your campaign registration approval status before assigning SMS activity targets. According to Close, your registration is approved by a 3rd party board, namely the Campaign Registry. Verify that your account holds this approval before expecting any messaging volume.

Check approved account numbers to understand how new inventory integrates with existing campaigns. If your account is already approved for A2P 10DLC, any new numbers you buy will be automatically added to your approved campaign. This automatic addition applies specifically to accounts that have already received approval for the A2P 10DLC standard.

Allow for carrier propagation time when scheduling outreach windows. This process can take up to 24 hours, as the change has to propagate across several stakeholders/carriers. Plan your team’s messaging activities with this propagation window in mind to avoid gaps in deliverability.

Recognize recipient suppression errors to manage team expectations around failed messages. Once they have a block list entry for a particular recipient phone number, any future attempts to message them will fail with Error Code 21610 - Message cannot be sent to the ‘To’ number because the customer has replied with STOP. Review this error code in your reporting tools to distinguish suppressed numbers from other delivery failures.

Illustrative example: setting one call target

A manager plans a target of 20 calls a day for 5 SDRs calling Washington recipients. Before assigning it, she checks whether the calls are covered solicitations. If they are, each number is screened against the federal registry, calls are placed only between 8:00 a.m. and 8:00 p.m. in the recipient's local time, and each rep identifies the company and purpose within the first 30 seconds. The 20-call figure is illustrative only: the checks set the limits, and the target is adjusted to fit them.

Record each outreach expectation

For one proposed SDR activity expectation, record the applicable restrictions and constraints from the sources cited above, then note the evidence your team will retain.

Record one entry for each channel your team plans to use. For call eligibility, note whether the activity falls under the definition of telephone solicitation as described in the Washington State Legislature source. For call timing, record the local time window constraints if applicable. For call opening and exit, document the identification and termination requirements. For message classification, specify how the platform treats the traffic type. For SMS registration and suppression, list the registration status and suppression handling. For Canadian consent evidence, detail the basis and supporting proof for any consent relied upon. Review the record today before assigning the expectation to the team.

FAQ: applying outreach checks to your team's channels

What belongs in an SDR outreach checklist?

The checklist covers six specific checks: call eligibility, call timing, call opening and exit, message classification, SMS registration and suppression, and Canadian consent evidence. These items separate channel-specific restrictions from general activity goals. Managers should verify each item against the applicable source before setting targets.

Does Washington's telephone solicitation definition cover my team's calls?

RCW 80.36.390 defines telephone solicitation as the unsolicited initiation of a telephone call by a commercial or nonprofit organization to encourage the purchase of property, goods, or services. It also covers calls intended to wrongfully obtain anything of value or solicit donations. Keep this scope tied to the Washington State Legislature's definition, which applies to commercial or nonprofit entities making unsolicited calls for these specific purposes.

When can covered solicitation calls reach Washington recipients?

According to Washington State Legislature, telephone solicitors shall not place calls received before 8:00 a.m. or after 8:00 p.m. at the call recipient's local time. This window is based on the recipient's local time, not the caller's time zone. Managers must ensure their team's dialing schedules respect this specific local time constraint for covered solicitations.

Can reps send person-to-person messages through Twilio Messaging Services?

No, Twilio prohibits transmitting person-to-person (P2P) messages through its Messaging Services. The policy states that Twilio treats any and all messages transmitted through these services as non-consumer or application-to-person (A2P) messages. This classification applies regardless of the actual content of the message or the type of message recipient.

According to Innovation, Science and Economic Development Canada, senders should be ready to provide proof of consent if asked. Keeping a record of each recipient’s consent basis is sound internal practice. This requirement applies when relying on consent to send commercial electronic messages under Canadian regulations.

Sources

  1. Seller login removal: 4 data clocks to check first
  2. Sales paycheck deductions: 4 steps for pay talks
  3. Pay a departing rep's commission in 3 steps (Minnesota)
  4. Seller wage complaint: 5 steps before a claim
  5. New Jersey seller leave requests

More plays