Import the roster
Upload Rent Manager or spreadsheet exports, map the right headers, and keep old residents disabled instead of erased.
Explore MercuryReachOpenClose
Resident notices that property managers can actually use.
MercuryReach gives property teams one calm place to import contacts, send urgent texts or calls, translate resident notices, and keep replies tied to the original message.
Know exactly who will receive the notice.
The delivery contract keeps audience, channel, language, timing, and live status together before the send.
- Channels
SMS + voice
Send texts, calls, or both from one notice.
- Language
EN + ES
Auto Spanish translation with preview.
- Operations
Inbox + tickets
Replies and support requests stay attached.
Simulation is explicit: no resident is contacted until live delivery is enabled.
See the notice workflow before you ask for a workspace.
This public demo shows the core promise: write the notice once, preview translation, and keep the send flow simple for day-to-day staff.
The live demo is here to prove the workflow, not to introduce every product setting at once.
Public demo
Interactive notice preview
Red Rock Park342 contactsChecking limit...
Spanish preview
Waiting for translationClick Translate when the English notice is ready.
Spanish will be generated after you click Translate to Spanish.
Quiet hours safe
Write the notice, translate it once, then preview both voices.
The daily workflow, without the admin fog.
The product is built around the job property teams repeat every week: keep rosters current, send clear notices, and answer residents without losing the thread.
Write once
Create the English notice, preview Spanish, and keep the simpler flow on when staff do not need every option.
Send and track
Send SMS, voice, or both with quiet hours, opt-outs, delivery history, and reply handling already attached.
What the workflow keeps attachedShow detailsHide details
Mass notices for emergencies, maintenance, inspections, rent reminders, and routine updates.
Simple mode hides admin clutter so non-technical property staff can stay focused on the send.
Every owner workspace keeps its own contacts, branding, billing, users, templates, and support history.
Launch packets show what is live, what is simulated, and what still blocks a real customer rollout.
Built like an operating system, not a blast tool.
MercuryReach keeps the boring but critical parts close: permissions, support tickets, billing state, delivery recovery, audit logs, and launch readiness.
Opt-out safe
STOP handling, contact preferences, and no-call/no-text states stay visible during every send.
Tenant isolated
Owner data, branding, staff, and billing settings stay scoped by workspace instead of becoming a shared mess.
Support ready
Ticket IDs, reply threads, and internal help desk routing are already part of the operating model.
Pick the size of the operation.
Start with the closest package. We can adjust the workspace with you as usage and support needs become clearer.
Starter
For smaller operators who mainly need urgent resident communication in one region.
$149.00/mo
3 parks, 1500 contacts, 7500 SMS segments
Mass SMS notices
Basic voice broadcasting
Two-way inbox
Growth
For owner groups running multiple parks and wanting predictable monthly operations.
$349.00/mo
12 parks, 7500 contacts, 15000 SMS segments
Everything in Starter
Live translation preview
Shared team inbox
Portfolio
For regional portfolios that need stronger governance, larger usage pools, and admin support.
$899.00/mo
40 parks, 25000 contacts, 60000 SMS segments
Everything in Growth
Priority onboarding
API and export access
Public-site answers should lower fear, not add more software words.
Do teams have to write the Spanish notice separately?
No. The workflow can reuse the English notice and generate the Spanish version automatically, with preview before sending.
Can this stay simple for non-technical staff?
Yes. The product already supports a simpler operating mode so day-to-day managers can focus on audience, message, and send decision.
Will live texting or calling turn on immediately?
No. Setup and rehearsal stay separate from live launch so your team can review the workflow before provider delivery is enabled.
Ready to give your team a calmer way to send notices?
Start with a setup request and give your team a workspace with a safer path to its first notice.