Skip to main content
GullySystem
Real estate and construction

WhatsApp, SMS and Email Notifications for Property management companies

Send business messages from approved events and recipient rules.

Platform

Does this function belong in your operation?

Use when people need consistent updates triggered by business records.

An order, payment, booking or task reaches a notification event.

Rent reminders, notice confirmations and announcements reach tenants without the manager typing each message individually.

Bring the records the workflow depends on.

  • Message events
  • Recipient permissions
  • Approved channel accounts and wording

Outputs to check

  • Message event and recipient log
  • Delivery and failure status
  • Retry or follow-up queue

Follow the whatsapp, sms and email notifications workflow.

Use this sequence to compare your current process with the proposed module. Agree the owner, permission and exception at each step.

  1. 1. Define the trigger

    Specify the business event and the message it justifies.

  2. 2. Select recipients

    Apply contact, permission and audience rules.

  3. 3. Prepare the message

    Use the approved content and required event details.

  4. 4. Submit through the channel

    Retain the attempt reference and distinguish queued from delivered status.

  5. 5. Resolve failures

    Correct invalid details or retry under the agreed duplicate-control rule.

Who uses the module, and who approves?

Keep responsibilities distinct even when one person holds more than one role.

Office assistant

Reviews event messages, checks recipient details and resolves failed or withheld submissions.

Accounts assistant

Checks financial message content and follows up delivery failures without changing the underlying ledger.

Owner

Reads what went out in the business’s name. Every word is on file.

Decide how exceptions are handled.

These business rules belong in configuration and testing. A normal transaction alone does not demonstrate that the workflow is ready.

Invalid recipient

Hold the message and request a corrected address or number.

Provider rejects message

Record the reason and retry only under the agreed rule.

Event repeated

Use the event reference to avoid unintended duplicate messages.

Can this work independently?

Notifications depend on a source event and an authorised delivery channel. They can use file or manual triggers, but order, booking or payment systems provide more reliable references. Provider acceptance, delivery and human reading are distinct outcomes and should not be treated as equivalent.

Systems and records it connects with

  • Collections and follow-up: Due balances, payment promises and follow-up outcomes.
  • Invoice management: Issued invoice references, line amounts and outstanding balances.
  • Appointment scheduling: Confirmed slots, cancellations and attendance outcomes.
  • Service reminders: Due-service triggers and follow-up outcomes.

Configure, test and introduce the workflow.

  • Gather the messages your staff type today. We write back which can come from records and which stay manual.
  • You approve wording and languages. Templates arrive for each channel, ready for the approval step WhatsApp requires. Sender details come from you. Share the WhatsApp number, SMS account and email, and a test message reaches your own phone before customers see any.
  • Go live small. A handful of customers receive live messages, staff check delivery status, and the office is trained.

Check the result before rollout.

Apply these checks to a sample from the agreed workflow, then repeat with an exception. Keep the expected result beside the test record.

  • A repeated event does not send unintended duplicates.
  • Recipient rules respect recorded permissions.
  • Failures are visible for follow-up.
Property management companies

How the business operates.

Owners judge you on one thing: did the money arrive on the fifth. Tenants judge you on another: did the plumber come. Both ask questions you should be able to answer from your phone, standing in a stairwell.

Lease register and rent roll

A custom piece for flat leases. It holds unit, tenant, rent, deposit, service charge, escalation, lock-in and notice dates together, with an alert before each date.

Rent collection and credit matching

Raise monthly demands and send reminders before the due date, as the paying guest product does for beds. Matching bank-transfer and card credits to flats is extra work we take on.

See the full industry workflow, reports and implementation plan →

The records that hold the operation together.

  • Owner, property, unit and lease version
  • Rent demand, tenant receipt and allocation
  • Repair ticket, approval, supplier bill and completion
  • Deposit, permitted deduction and move-out settlement

Operational bottlenecks to check

Nobody can tell who paid rent

A rent credit lands from an unknown sender with only a bank reference, and matching it to flat 4B takes days while the owner is already calling.

Renewals and escalations sneak up

Escalation dates, lock-in ends and notice windows sit inside scanned agreement PDFs, and the rent rise is noticed three months late. That income is gone.

How work flows across this business

This module sits within a wider operating process. Use the sequence to identify the other teams and records affected by a change.

  1. 1. Record the managed unit

    Identify the owner, unit and accepted management arrangement, then attach the current tenant and lease terms.

  2. 2. Raise and match rent records

    Create the agreed demands and allocate actual receipts, retaining unexplained payments for investigation.

  3. 3. Manage repairs

    Record the issue, responsibility, spending approval and supplier work. Keep the tenant update separate from approval of the supplier’s bill.

  4. 4. Reconcile the owner account

    Bring together collected rent, approved expenses and the agreed management fee. Explain unresolved items before recording remittance.

  5. 5. Handle renewal or move-out

    Record the agreed change or end of the lease, the unit condition and authorised deposit adjustments. Keep financial settlement distinct from readiness for the next tenant.

Industry reports to connect with

  • Rent demanded, received and unallocated
  • Repair tickets and supplier bills awaiting approval
  • Owner balances and remittance records
  • Lease milestones, deposits and vacant-unit readiness

Questions before implementation.

When should property management companies consider whatsapp, sms and email notifications?

Use when people need consistent updates triggered by business records. An order, payment, booking or task reaches a notification event.

What should we bring to the requirements discussion?

Bring anonymised examples of Message events; Recipient permissions; Approved channel accounts and wording. Show who creates, checks and changes each record. Use only records from an activity that meets the suitability conditions above.

Does this replace our existing business software?

The starting point is your current system and the gap you need to close. Send business messages from approved events and recipient rules. Configuration, a connected module or a custom build are evaluated against that gap before a replacement is proposed.

What is outside this module?

Messaging depends on provider availability, account permissions and current channel rules.

How are scope, price and rollout decided?

The proposal follows a review of your records, user roles, branches and existing software. Data migration, connections, training and support are scoped separately where needed. A repeated event does not send unintended duplicates. Use this check when reviewing the first working version.

Talk to us

Discuss whatsapp, sms and email notifications for your business.

Tell us which workflow needs attention and which systems your team uses. The next step is a requirements discussion and a written scope.

What happens after you share your requirements

  1. We review your brief and the systems you already use.
  2. We clarify the workflow, missing information and the work to consider first.
  3. The proposed scope sets out the deliverables, responsibilities and dependencies.
  4. Review the scope and commercial terms before deciding whether to proceed.

Start with your requirements

Describe your current process, the people involved and the change you need. Start with the details you know; we can clarify the rest together.

Share your requirements