Notification Sending Rules

Daily

These notifications are generated every day at a specific time and sent according to the send_at field in the mailing rules

• birthDay - Birthday
• beforePay{days} - Payment notification. To send a notification 25 days before the payment, specify beforePay25
• payDelay{days} - Overdue notification. To send a notification on the 25th day of delay, specify payDelay25
• todayPay - Payment notification for the current day
• extAutoInsuranceBefore{days} - Notification about upcoming CASCO payment
• custom - Custom notification

Event-Based

These notifications are sent after receiving a specific event from the core

• contractClose - Contract closure
• contractOverpayment - Contract overpayment, after closure
• contractIssue - Contract issuance
• contractCreate - Contract creation
• contractProlongation - Contract prolongation
• contractRestructuring - Contract restructuring
• ddsIncome - Incoming payment
• ddsOutcome - Outgoing payment
• leadDenied - Lead denial
• leadClientRefusal - Client refusal
• leadApproved - Lead approval
• passportReUpload - Passport re-upload
• signOffer - Contract signing
• ruleTask[{RULE_TASK_CODE}] - Start of BPE step execution with code {RULE_TASK_CODE}.
• newClient - New client registration. This event is sent through the Personal Account

Delayed Sending of Event-Based Notifications

For notifications contractClose, contractOverpayment, contractIssue, contractCreate, leadDenied, leadClientRefusal, leadApproved, passportReUpload, signOffer, ruleTask[{RULE_TASK_CODE}] and newClient you can configure delayed sending.

To send a notification with a delay, specify the delay duration after the rule.

For example: To send a notification for the start of the BPE step FILE_UPLOAD 20 hours after the event occurs, specify the rule ruleTask[FILE_UPLOAD](20h)