The rules run before the dial, not after the complaint
Outbound calling and texting is regulated, and the consequences land on the brokerage. So consent, suppression, calling windows, attempt caps, and AI disclosure are enforced inside the platform core — server-side, on every outbound action, with no per-account override.
This page describes how the platform behaves. It is not legal advice, and it does not replace your own brokerage’s obligations or your counsel’s guidance.
Consent
Before any outbound call or message, the platform checks the consent recorded for that contact on that channel — where it came from, when it was captured, and whether it still stands. Contacts without the consent a channel requires are not dialled or texted by automation, and imported lists cannot be turned into an AI cold-calling campaign.
Suppression & do-not-contact
Opt-outs are recorded centrally and enforced for every channel and every automation. Once a contact opts out, no campaign, sequence, or AI agent in the account can reach them again. Suppression is checked on the outbound path itself, not only when a list is built.
Calling windows
Outbound calling and texting respects permitted local hours for the contact's location, plus the operating hours the brokerage sets. Work queued outside the window waits for the window instead of going out late.
Attempt caps
Per-contact limits cap how many times a lead can be called or messaged over a period, so no automation can grind the same person down. Caps apply across campaigns, not per campaign.
AI disclosure & recording notice
When a caller asks whether they are speaking with a person, the assistant answers honestly that it is an AI assistant. Recording notice is handled on the call. Outbound AI calls carry disclosure.
Enforced in the core, server-side
These checks live in the platform core and run server-side on every outbound action, in production and in development alike. They are not tenant-configurable, are not exposed as an editable setting, and there is no bypass flag.
How calls and messages are sent on this platform
Written for recipients, carriers, and messaging providers who want to know exactly what traffic from our numbers is.
How consent is collected
Our customers are real estate brokerages and agents who collect consent directly from their own leads and clients — through a form on their website or listing page, a written agreement, an inbound call or text to their number, or an existing business relationship recorded in the platform. The source and timestamp of that consent are stored on the contact record. We do not buy, rent, or supply contact lists.
Opting out
Recipients can stop messages at any time by replying STOP, UNSUBSCRIBE, CANCEL, END, or QUIT. The reply is processed automatically, the contact is suppressed platform-wide for that account, and a confirmation is sent. Replying HELP returns the sender's identity and this contact information. Callers can ask to be removed on a call and the same suppression is applied.
Message frequency and content
Messages are conversational and transaction-related — replies to an inquiry, appointment confirmations and reminders, follow-up on a property the recipient asked about, and updates on an active deal. Frequency depends on the conversation. Messages identify the sending brokerage. Message and data rates may apply from the recipient's carrier.
Prohibited use
Accounts may not use Pyng for messaging unrelated to their real estate business, for any category prohibited by carriers or messaging providers, or for outreach to contacts who have not consented. We suspend accounts that do.
Stop messages or report traffic from our platform
Reply STOP to any message to be removed immediately, or contact us and we will suppress the number across the platform and investigate the account.
Callers are never told the AI is a person
An AI assistant answers and places calls on behalf of the brokerage. If a caller asks whether they are talking to a human, the assistant says plainly that it is an AI assistant and offers to connect them to a person. It does not claim a human identity, and it will not pretend to be a licensed agent giving advice it is not authorised to give.
Calls are recorded so the brokerage can review its own conversations, with notice handled on the call, and every recording and transcript is attached to the contact record inside that brokerage’s account only.
United States and Canada
Voice, SMS, and email are provisioned for North American numbers, and the calling-window and consent rules are built around US and Canadian requirements. Pyng is operated by SPACEMINE PVT LIMITED.
- Conversation data — recordings, transcripts, and message history — belongs to the brokerage whose account it was created in, and is scoped to that account on every query.
- Phone numbers are masked in operational logs, and transcripts are not written to logs at ordinary logging levels.
- Secrets and provider credentials are held in the platform's server environment and are never exposed to the browser.
- Recordings and transcripts exist so a brokerage can review its own calls; they are not sold or shared for advertising.
- Customers can export or request deletion of their account data. See the Privacy Policy for how to ask.
Questions from your compliance reviewer?
Send them to us directly. We will answer in writing, including how a specific control is enforced.
This page explains how the controls behave. The messaging policy and AI disclosure are the formal, dated versions — those are the ones to send to a carrier or a compliance reviewer.