A real local event. A clear reason to call.

A listing, sale or neighborhood question can make a conversation relevant. It does not establish permission to call everyone nearby. Use this guide only within an approved campaign and caller role.

Updated September 26, 2026 · An operational guide

Verify the event and the contact policy

Confirm the event, its date, the property and the facts your team is entitled to describe. Do not say “we sold” or “our listing” unless your team actually represented that transaction. Do not invent a buyer inquiry to make a neighborhood call sound urgent.

Review the list source, current eligibility, suppression and calling window before release. A geographic radius is a selection method, not a legal basis for contact. Keep unresolved records on hold rather than treating a nearby address as permission.

Prepare the information you can actually provide. If the caller plans to offer a market report, confirm that the report exists or that an accountable person has agreed to prepare it. Do not promise instant delivery from a tool that does not perform that action.

Use a truthful local reference

Suggested wording, with verified placeholders:

“Hi [name], this is [caller], a real estate [accurate role] with [brokerage]. I’m calling about [verified event] near [area]. We [accurate description of your role, if any]. Would information about that event be useful, or would you prefer no further contact?”

Use the required identity and purpose disclosures for the approved campaign. Do not imply that the person already requested information or that a public sale price establishes the value of their own home.

Let the question determine the next step

If the person wants information, ask which part matters. A question about the transaction, a broader neighborhood question and a request to discuss their own property require different responses.

Answer only from verified information and within the caller’s scope. A neighboring sale is a fact to explain, not a complete valuation. Route pricing, representation or transaction questions to the responsible agent when appropriate.

Do not turn a casual value question into a forecast of selling intent. Record what the person asked and what you actually offered. The next agent should not be handed a “hot seller” label that the conversation does not support.

Make a requested report an owned task

When the person requests a report or other information, confirm the item, the appropriate permitted channel and any relevant delivery expectation. Give the action to a named person in the team’s actual workflow.

“You’re asking for [specific information]. [Responsible person] will [actual supported action]. What is the appropriate way to provide that to you under our contact process?”

Use that wording only when the promised action is real. A call note saying “send report” is not evidence that a report was sent. Verify completion in the delivery system rather than allowing the task to disappear after the dialing session.

Respect the answer instead of forcing a cadence

No interest: record it and follow the approved policy; do not infer permission for ongoing updates. Explicit stop: use internal DNC and coordinate affected workflows. Wrong person: correct or hold the record.

Existing representation: update the context and ask the responsible broker to review further action. Wants an agent conversation: capture the actual question and agreed next step, distinguishing a requested meeting from a confirmed appointment.

A neighborhood campaign should not keep revisiting a contact simply because the geographic list is easy to regenerate. Preserve known preferences when lists are refreshed.

Measure the information flow, not invented future business

Track the work you can establish: eligible attempts, human answers, specific requests, agreed next steps and completed follow-ups. Keep appointment requests separate from confirmed or held meetings.

Review whether the team delivered what it promised. A high number of “interested” dispositions is not useful when no one can identify the requested information or the owner of the action. Use the measurement method rather than borrowing a conversion forecast.

Leave the contact with the right state

The final record should identify the verified event discussed, the person’s actual response and the next action—or the reason no further contact is appropriate. Check any material uncertainty against available, permitted audio.

Practice using test records before releasing a live list. The sandbox trial contacts no real person. Production calling still needs the customer’s own Telnyx account and a separately approved list.

Inspect the workflow before you commit.

Your 14-day trial runs on a Telnyx sandbox with test numbers; nothing reaches a real person. A human provisions the environment. The 14 days start when it is ready and we email you. No credit card is required. On conversion, you connect your own Telnyx account and real calling lists.

Operator workflow walkthrough
Captured test interface: choose a calling list.
1 of 4 · Prepare the list. Captured interface with test data; identifying details masked.