Email: families and recipients
CRAnotify's email is transactional: it originates from a fact (a deadline approaching, a filing recorded, an invitation) and goes to whoever that fact concerns. There is no marketing email. The operational families leave a trace in the registry: an alert sent is itself evidence.
The families
| Family | Content | Registry trace |
|---|---|---|
| A · Identity | Address verification, welcome, password reset, email change, invitation. | No |
| B · Clock | Deadline started, reminders at 16/4/1 hour, no response, deadline missed, re-check reminder, change of the moment of awareness, taking charge. | Yes |
| C · Acts | Triage outcome, early-warning filing, 72-hour update, final report. | Yes |
| D · Portal | Acknowledgement to the reporter, notice of a new report to the security mailbox. | Yes |
| E/G · System | Setup to be completed, dossier retention expiring, an alert that could not be delivered. | No |
| F · Personal data | Export, deletion request, breach notice where applicable. | No |
Who receives what
Recipients are resolved against the escalation chain, not against a generic list:
Idempotency and retries
- One alert, once. Each dispatch is identified by organisation, case, type, phase and recipient: the same reminder never arrives twice, even if the scheduler runs repeatedly.
- Retries with backoff. A failed delivery is retried; after three failures the alert is declared undeliverable and administrators are told.
- Recording. For the operational families, the registry keeps the recipient, the moment and the message type used.
If email delivery is not configured on the installation, the application still works: alerts do not go out, but the flow, the deadlines and the registry are untouched. Integration status is visible in the Account area.
Behaviour in exercise mode
With exercise mode on, the legal representative is excluded from escalation and the system alerts about undeliverable mail are suppressed. The rest still goes out, so the rehearsal is realistic without disturbing people who should not be disturbed by a simulation.
Sender and content
Email comes from no-reply@cranotify.eu with the name «CRAnotify». It carries a title, the fact in a few lines, a direct link to the case and — where relevant — why you are receiving it. The footer holds the company details and the note that these are communications relating to a contractual obligation, not marketing.
Allow no-reply@cranotify.eu through your corporate spam filters before you need the reminders. A «1 hour left» alert sitting in the junk folder is an alert that does not exist.
Checking that it works
The Account area offers a test send to your own address (never to an address typed in: that is an anti-abuse measure). If the test arrives and the reminders do not, the problem is in the escalation addresses, not in delivery.
For the full picture of when each reminder fires, see Phases and deadlines.