Verify the request before referring to it.

Before releasing a record, identify its source and the campaign’s applicable permission, registry and suppression review. A purchased lead or a “requested information” label is not sufficient evidence by itself.

When the script refers to a prior request, verify the actual request, its date, recipient or intended business, subject and permitted response. Do not use a generic vendor label to imply that the person asked your team for information.

If the necessary eligibility or provenance is unresolved, hold the record. A more honest cold opener does not make an otherwise unauthorized call permissible. The list workflow explains the release process.

Suggested wording only when the referenced request is verified and the response is permitted:

“Hi [name], this is [caller] with [business], in the role of [accurate role]. I’m responding to your [verified date and subject] request to [verified recipient]. Is this the information you intended to ask about?”

Do not substitute “you requested information” when that fact cannot be established. Do not infer the intended recipient from the business that purchased the lead.

For an independently approved campaign that does not rely on a prior request, the qualified reviewer should approve truthful wording for that campaign. This guide does not supply a fallback that bypasses the missing eligibility decision.

Define what the caller may say and ask under the approved role. Do not assume that describing someone as an appointment setter permits every screening question, product comparison or recommendation.

When the person asks about eligibility, suitability, premiums, benefits or exclusions, route the question to the appropriately qualified person. Do not promise an approval, a rate or a coverage result that has not been established.

Collect only the information necessary for the approved next step. Do not ask for unnecessary health, financial or identity details merely to make the lead note look complete. An AI summary should not become a substitute for the specialist’s assessment.

Confirm the approved recording process before the call. Permission to contact the person does not answer whether or when the conversation may be recorded. Use the recording-policy checklist with the responsible reviewer.

Where a recording is available and permitted, after-call AI can produce text that repeats sensitive information. Apply the agreed access and data-minimization process to those outputs. A recording or summary may be missing or incorrect; neither establishes product eligibility or exact consent.

When the person wants to speak with the qualified agent, confirm the subject, the actual availability and the permitted contact method. Do not mark a meeting confirmed simply because a caller offered a time.

“The question for [qualified person] is [the actual question]. Would [verified time, with time zone] work for that conversation? I’ll record what we agree and follow our confirmation process.”

Use the example only when the named person and time are real. If availability is not established, record a request and assign responsibility for confirmation. The calling tool does not itself establish that a separate invitation or email was delivered.

Denies making the request: do not argue from the list label. Record the discrepancy and hold the relevant provenance for review. Requests no more contact: acknowledge and use internal DNC, then coordinate other affected workflows.

Wrong number: record the mismatch and stop using that record under the incorrect identity. Asks a regulated product question: escalate rather than improvising. Wants information: identify the exact request and who owns the permitted delivery.

A person’s interest is not an eligibility finding. An appointment is not a policy sale. Keep those states separate in the outcome and reporting.

The completed record should identify the actual response, the approved next action and its owner, or the reason the record remains on hold. Review material uncertainties against available permitted source evidence.

Practice with test data before production. The sandbox trial does not call real people or establish real-list conversion rates. A paid production workflow requires a separate eligible list, customer-owned Telnyx configuration and the campaign’s professional review.