Alerts by schedule or by event
Run an alert on a schedule against your data, or when something happens, such as a contract changing status.
Communication management
Alerts and campaigns that reach the right people, once
One engine sends everything the platform needs to say: a work order that has gone quiet, a contract about to lapse, a notice to every resident of a building. Recipients, templates, schedules and delivery are controlled in one place.
Capabilities
One voice for the whole platform
When every module sends its own emails, nobody knows what was sent, to whom, or why it was sent twice. Here every message goes through one engine.
Campaigns with throttling
Send a message to a list, for example every resident of one building, in batches such as 30 emails every 5 minutes.
Recipient lists
Static lists of users, roles, organisations and addresses, or dynamic lists that are resolved when the message is sent.
Arabic and English templates
Subject and body per language with fields taken from your records. The recipient’s language decides the version.
Delivery you can trust
One message per recipient and record, retries on failure, and a message of unknown result is never resent without a person deciding.
A full delivery log
Every run, message and outcome is recorded and visible to those who may see it.
See it live
From a record to a delivered message
Follow one alert from the data to the recipient. Click a step, or let it play.
Step 1 of 5
Start from your data
An alert reads the contracts that end within 30 days. Sources are registered by each module, so only allowed data is used.
- Source
- Contracts
- Filter
- Ends within 30 days
- Scope
- Owner’s organisations
Also available
- Work orders
- Dues
- Tenants
- Users
Step 2 of 5
On a schedule, or on an event
The alert runs every morning at 08:00. A missed run is run late or skipped, as you choose.
- Schedule
- Daily 08:00
- Missed run
- Run late
- Repeat
- Once per record
Also
- Event alerts
- Every N minutes
- Weekly or monthly
Step 3 of 5
A bilingual template
The subject and body use fields from the record, such as the contract number and the end date.
- Languages
- Arabic and English
- Fields
- From the record
- Preview
- With real rows
Options
- Attachments
- Layout
- Digest per recipient
Step 4 of 5
Queued, de-duplicated and sent
The engine resolves the recipient, checks for duplicates and sends by email and in-app notification.
- Channels
- Email, in-app
- Throttle
- Global and per campaign
- Retries
- Automatic
Guarantees
- No duplicates
- No unknown resend
- Test mode
Step 5 of 5
Everything on record
The delivery log shows what was sent, to whom, when and with what result.
- Log
- Per message
- Reports
- Volume and failures
- Dashboard
- Communication overview
Also
- Failed messages
- Runs
- Per recipient
Illustrative example on sample data.
How it works
How the engine sends a message
- 01
Modules register
Each module offers its data sources and its ready alerts. Nothing sends email on its own.
- 02
Rules decide
Alerts and campaigns decide who is told, when and with which message.
- 03
The engine sends
It queues, finds recipients, fills the template, avoids duplicates and delivers.
- 04
You can see it
Runs, messages and failures are in the log, with reports and a dashboard.
Deep dive
Built so a message is never sent twice, or by the wrong person
Delivery
One logical message per recipient
Every message has a unique key built from the alert, the record, the recipient and the channel, so a retry or a second run never creates a duplicate. If the result of a send is unknown, a person decides.
- No duplicates
- Retries with limits
- Unknown results never resent automatically
A message is made once
RecordContractRecipientResponsibleCheckNot sent yetSendEmail
Campaigns
Reach many people without flooding the mail server
A campaign goes to a list or a filtered source, in batches. Draft, scheduled, running, paused and completed states let you stop it at any moment.
- Batch size and interval
- Pause and resume
- Test mode to a test address
Control
An alert runs with its owner’s rights
Alerts and campaigns run with the permissions and organisation scope of the person who owns them, checked at every run. Personal data in the log is shown only to those allowed.
- Rights re-checked at each run
- Sources limited by organisation
- Every change recorded
Who may do what
Manage alertsOwn organisationsAllowed
Send campaignsOwn organisationsAllowed
View all messagesNeeds the log permissionRestricted
Ready to use
Ready alerts from the modules you use
Modules ship their own alerts, such as idle or late work orders and the contract alerts. You switch them on, set recipients and adjust the message. They can be switched off, never lost.
- Work order alerts
- Contract alerts
- Edit schedule, recipients and message
Alerts you can switch on
Idle work ordersLate work ordersContract expiringNotice deadlineDues overdueMissing documentsWaiting approval
Business value
What reliable communication is worth
People act on what they hear in time. The value is fewer missed deadlines and fewer messages nobody needed.
The right person hears first
Alerts reach the responsible person while there is still time to act.
Reach many, calmly
Campaigns go out in batches with throttling and a full record.
No duplicates, no silent failures
Retries, unique messages and a log mean you always know what happened.
In their own language
Arabic and English templates, chosen by the recipient.
How it usually works
With Mintema
01Notifications
Each module sends its own.
One engine for everything.
02Duplicates
The same email three times.
One message per recipient and record.
03Mass mail
Sent all at once, from a personal account.
Throttled campaigns with a log.
04Follow-up
Unknown whether it was sent.
A delivery log per message.
FAQ
Communication management, answered
Have a question that is specific to your organisation? A solution engineer will answer it against your own assets, processes and data.
An alert is a standing rule that runs by schedule or when an event happens, such as an idle work order. A campaign is a message sent to a list or a filtered group, in batches, such as a notice to all residents of one building.
Email and in-app notifications are delivered. SMS needs a connector to your own provider.
Yes. Each template has an Arabic and an English version, and the recipient’s language decides which one is sent.
Yes. Test mode sends every email to a test address, and templates can be previewed with real rows.
Only users with the log permission, and only inside their organisation scope. Every administrative change is recorded.
SEE IT SEND
Your alert,
Your alert,
sent live.
Tell us one message your team sends by hand today. We will turn it into an alert and send a test during the call.