08 / 10 · Events & communication
Event notifications
Events, templates and delivery status for operational notices.
The starting point
The right message, once and with context.
A status change may need a notification, but not ten duplicate emails. We link specific events to templates and log each attempt. Preferences and opt-outs are defined for the type of communication; final delivery also depends on the provider.
One event, one identifier, one notice
Event
status.changed
Rule
event_id
Notice
Template + log
The log is waiting for an example event.
No real email or message is sent.
Demonstration using fictional data. This is not a connected application or an actual client result.
What you are buying
A clearly defined
first handover.
Base prices for the stated starter scope, including applicable taxes. The final quote and external costs are confirmed before contracting.
- Up to three event types and three templates in one language.
- One channel and one provider with a documented API.
- Attempt logs, limited retries and duplicate control.
- Preferences or opt-out where appropriate, plus integration documentation.
Outside this scope
Bulk campaigns, purchased contact lists, paid SMS or email credits and guaranteed inbox placement are not included.
What we need
Events, intended recipients, message copy and the legal basis for communication.
What you receive
Event integration, templates, status log and retry test cases.
How we verify it
The same event identifier does not create two separate notices, and failures are logged.
Timing depends on materials, access and reviews. The date is confirmed in your quote.
Another part of the journey.
All solutions ↗
From the problem to the next version