The Email, SMS and Letter nodes work the same way: they send a message based on a template and report the outcome through ports. The due date sets the payment term and the "no response" port. The bounce processing period sets how long a bounce is still linked to the message.
The ports
| Port | Fires when | Muting |
|---|---|---|
| Executed | Right after sending, whatever the result | No |
| not sent | Bounce, no valid address or number, print or processing error, blocked channel | Yes |
| no response after x days | The due date has passed without payment | Yes |
| paid | The collection order is paid, also during the respite period after the due date | Yes |
Due date
The due date is a number of days after sending. It decides:
- until when the paylink is valid (after that, respite may apply, see Paylink validity and respite);
- when the no response after x days port fires.
For letters there is a minimum of three days; if the sending falls on a weekend, it moves to Monday and the due date moves along with it. This rule is in the workflow settings, not in the node.
Bounce processing period
A bounce can come in days after sending (for example a letter that is returned). The bounce processing period decides up to how many days after sending a bounce is still linked to this message and fires the not sent port.
- The period is an advanced setting on the node and is filled in beforehand with the longest term of the outcome ports on the node (usually the due date).
- If no term can be derived, it is 14 days for email and SMS and 28 days for letters.
- If you change the due date, the period moves along with it, until you overwrite it yourself.
- A bounce after the period is logged on the case file, but no longer steers the workflow.
Send times
Messages from a workflow are only sent within the send days and send hours of the client. If the moment falls outside them, the message waits until the next allowed moment. See Send times, days and blocked dates.
Contact info and fallback
The node uses the first email address, number or address of the customer. If that bounces, the system tries the second one. If that also fails, not sent fires. If nothing is attached there, the collection order goes to the task list No contact data. Choosing which address the node uses (only the second one, or a custom address) will come later.