These Communications Terms apply when you use Real Estate CRM Pro to send, schedule, automate, track, route, or log communications, including email, campaigns, listing alerts, video email, booking messages, course announcements, document requests, inbound replies, website lead follow-up, and farming outreach.
Consent and Lawful Basis
You are responsible for having consent, an existing business relationship, or another lawful basis required to contact each recipient. You must honor opt-outs, suppression lists, Do Not Call restrictions, brokerage policies, platform terms, and recipient preferences.
Email Compliance
For commercial email, you are responsible for accurate sender identity, non-deceptive subject lines, truthful content, required mailing address details, unsubscribe handling, suppression management, and any other requirements that apply to your messages. Real Estate CRM Pro may provide unsubscribe and suppression tools, but you remain responsible for your compliance program.
Calls, Texts, and Future Messaging
If you use phone, call logging, SMS fields, future texting features, reminders, or imported phone data, you are responsible for TCPA, DNC, state mini-TCPA, consent, quiet-hour, opt-out, and recordkeeping obligations. Farming and enrichment data should not be treated as consent to call or text.
Tracking and Analytics
The service can track email opens, clicks, replies, video views, watched duration, CTA clicks, listing-alert deliveries, website return visits, booking activity, and similar engagement events. You are responsible for providing notices and obtaining consent where required for tracking technologies or marketing analytics.
Farming and Prospecting
Expired, cancelled, withdrawn, likely-seller, FSBO, public-record, owner-enrichment, and farming workflows require careful review. You must verify relist status, ownership, contact rights, suppression status, MLS or vendor restrictions, and outreach legality before sending messages or mail. The service does not guarantee that a prospect may be lawfully contacted.
Inbound Email and Reply Routing
Inbound reply routing may store message headers, sender and recipient addresses, subject lines, bodies, HTML, and provider payload metadata so replies can be logged to contact files and forwarded to assigned users. You are responsible for informing your team and contacts as required by law and policy.
Service Protection
We may suspend, throttle, or block sending, tracking, lead-capture, API, or integration activity if we detect abuse, spam complaints, bounces, unauthorized use, provider risk, or legal risk.