Notification preferences
Notification preferences are the type × channel switch for the messages the system sends to the debtor. They answer questions like "I want reminders by email, but not by SMS" without touching any collection rule.
The type × channel matrix
Six message types, three controllable channels:
| Type | What it is |
|---|---|
Pre-due reminder (reminder) | Friendly notice before the due date |
Post-due collection (overdue) | Collection of an overdue debt |
Negotiation proposal (negotiation) | Agreement/discount offer |
Credit bureau warning (negativation_warning) | Prior notice of credit bureau registration |
Protest warning (protest_warning) | Prior notice of protest |
Payment confirmation (payment_confirmation) | Receipt for an identified payment |
Each type can be switched on/off per channel: email, SMS and WhatsApp. Voice calls and manual records do not pass through this filter.
Opt-out: everything on by default
The model is opt-out: without any configuration, all types go out through every channel the rule dictates. You only record a preference to turn something off (or turn it back on later).
Off does not mean silently discarded
When a rule step tries to send a disabled type, the system does not silently discard the message: it suppresses it with a recorded reason ("Notification type 'X' disabled for channel Y in the account preferences"). The reason appears on the Notifications screen and in the step's telemetry: you can always explain why something was not sent. It is the same philosophy as contact compliance: every non-send has an auditable why.
How the preference combines with the rest
The account preference is one of the layers evaluated before each send, together with:
- The debtor's suppressions (individual opt-out, "not me", dispute...): these always win;
- The legal contact window per state;
- The per-person contact limits.
In other words: a preference switched on does not force a send (the other layers still apply), and a preference switched off blocks that type×channel for the entire account.
Managing via API
GET /api/v1/notification-preferences(permissionsettings.show): returns the six types with the effective state per channel.PUT /api/v1/notification-preferences(permissionsettings.update): writes the matrix; each change goes to the audit trail asnotification_preferences.updated.
Do not confuse
- Notification preferences (this page): what the debtor receives, by type and channel, at account scope.
- Sending channels (Settings → Notifications): the technical email/SMS/WhatsApp providers that actually deliver.
- Operator notifications (the bell at the top): internal alerts for the team, described in Tasks and team.