# Notification Recipient Rules
Recipient Rules define how the system finds who receives an outbound notification — customer mobile, customer email, employee, or a fixed contact — for use on Transaction Configs.
Overview & List View
Go to Settings → Notification System → Recipient Rules.
List columns: Id, Name, Status.
Quick filters: Active (default).
Filters: Name, Status.
List actions: New, View, Edit, Delete (multi).
Fields
General
| **Field** | **Description** |
|-----------|-----------------|
| Name * | Rule name referenced on Transaction Configs. |
Resolution Steps
Add one or more steps (processed in order):
| **Field** | **Description** |
|-----------|-----------------|
| Step Type * | resolve — look up contact from document. manual — use fixed contact if needed. |
| Recipient Type | Customer, Supplier, or Employee (when Step Type is resolve). |
| Recipient ID Field Path | Document field pointing to party ID (e.g. customerId) — when Step Type is resolve. |
| Manual Contact | Fixed phone or email — when Step Type is manual. |
| Order | Step sequence when multiple steps exist. |
Examples
Example A — Customer mobile for WhatsApp on Sale Invoice
| Order | Step Type | Recipient Type | Recipient ID Field Path |
|-------|-----------|----------------|-------------------------|
| 1 | resolve | Customer | customerId |
Links to customer phone on master for WhatsApp automatic sends.
Example B — Fallback manual number
| Order | Step Type | Manual Contact |
|-------|-----------|----------------|
| 1 | resolve | *(customerId → customer phone)* |
| 2 | manual | +919876543210 |
If customer phone is missing, send to fixed backup number (use carefully — compliance).
Example C — Manual Send Email
Recipient rules are optional when using Send Email on sale documents — the user sets To on the compose screen. Rules are required for automatic email and WhatsApp configs so the system can resolve the recipient on status change.
Actions
New, View, Edit, Delete.
FAQ
What can a recipient rule target?
Customer, supplier, or employee contacts resolved from document fields — typically phone for WhatsApp and email for Email channel.
Can one rule serve multiple transaction configs?
Yes. Reuse the same Recipient Rule when audience logic is identical.
Why did the customer not receive WhatsApp?
- Customer phone missing or wrong format on master.
- Rule field path incorrect (e.g. customerId).
- Check Transaction History Failed status.
Are recipient rules used for Send Email button?
Not required — user enters To on compose. Optional for default pre-fill. Required for automatic email configs.
Are recipient rules used for Send to Whatsapp on invoice?
No. That button uses customer phone on the invoice directly.
Can I send to multiple numbers?
Depends on rule design and channel — test with sample approved document and review History.
Do recipient rules apply to in-app notifications?
No. Only for Notification System outbound channels.
Can I delete a rule in use?
Deletion may be blocked when Transaction Configs reference the rule — reassign configs first.