We use optional, privacy-safe analytics to understand which pages help visitors. Nothing optional runs until you choose. Privacy policy

Skip to content
SendiMessage
Start Pilot
Property management

Tenant communication without the phone tag

Property teams spend hours on calls that could be two messages: the maintenance window, the viewing reminder, the rent receipt. Messaging moves routine communication to a channel tenants answer — and keeps a written record of every exchange.

Try the interactive demo

The communication problems

  • Phone tag around maintenance access windows
  • Missed viewings that nobody confirmed
  • Rent and renewal notices lost in email
  • No written trail of what was communicated when

Recommended workflows

Maintenance windows
Work-order systems announce access windows; tenants confirm by reply.
Viewing reminders
Reply-to-confirm cuts no-show viewings.
Payment notices
Rent reminders and receipts as transactional messages.
Building notices
Outage and works notifications to affected units.
Maintenance is scheduled for your unit Tue 9–11 AM. Reply OK to confirm access.Reminder: your viewing at 14 Oak St is tomorrow at 5 PM.Your rent payment was received — thank you.

Architecture

How it fits together: Property management system, then Workflow or middleware, then SendiMessage API, then Tenant, then System update.
  1. Property management systemUnits, tenants, work orders
  2. Workflow or middlewareFires on work-order and calendar events
  3. SendiMessage APIPOST /send-message with unit + work-order ids
  4. TenantNotification + confirmation reply
  5. System updateConfirmations recorded via webhook

The API request

send message
curl -sS https://api.sendimessage.com/v1/send-message \
  -H "X-API-Key: $SENDIMESSAGE_KEY" \
  -H "X-API-Secret: $SENDIMESSAGE_SECRET" \
  -H "Content-Type: application/json" \
  -d '{
    "number": "+15555550123",
    "content": "Maintenance is scheduled Tue 9-11 AM. Reply OK to confirm access.",
    "status_callback": "https://your-endpoint.example.com/status?unit_id=u_204&work_order=wo_5518"
  }'
# → {
#   "status": "QUEUED",
#   "message_handle": "4e828182-a640-483f-bfe9-17ffcaa51d48",
#   "to": "+14155550123",
#   "service": null,
#   "is_outbound": true,
#   "error_message": null,
#   "date_sent": null
# }

Channel behavior and replies

Routine notices work on any channel; "auto" simply maximizes the chance they're seen. iMessage delivery is available on supported messaging lines and destinations. Recipients without iMessage receive SMS when fallback is configured — never assume universal iMessage availability.

Confirmations return with the work-order id, so access windows are confirmed in the system — not in a voicemail box.

Line setup, availability, and pricing

One line per portfolio or management brand; large portfolios sometimes split by region.

Line availability varies by country and channel. Run a preliminary availability check, and the team confirms final availability during onboarding review. Check preliminary availability →

Pricing is per active line, billed monthly, with usage per your agreement — confirmed for your countries and volume during managed onboarding. How pricing works →

Frequently asked questions

Can tenants opt out?
Yes — STOP handling is part of consent review during onboarding, and your handler updates tenant preferences immediately.
Does this integrate with our PMS?
Any system that can fire webhooks or run scheduled jobs integrates through the REST API — the same pattern as the CRM guides.

Ready to build this?

Request the setup, or book an integration review and the team will map it to your systems.

Book an Integration Review