Successful communication not only depends on the message itself but also on to whom it is sent. We enable you to determine whether a notification should be sent for a certain task or not and whether a notification should be sent to one or several recipients.
Overview
- Define if a notification should be sent or not
- Define multiple recipients
1. Define if a notification should be sent or not
Sometimes you might want to have contact details available in Urbantz but not send notifications to the recipient. For example, when you want to allow a driver or dispatcher to be able to reach out to a recipient if and when needed but the recipient does not wish to receive any automatic notification.
In that case, to make sure no notification goes out, you can set specific parameters to false (the default value being true).
- When creating a task manually
You will find three toggles in the Delivery tab.
You can either disable all notifications (left) or disable only SMS or only emails (right).
- When announcing by file
Below fields are available in the Field Mapping.
You can add a column to your file per field and for each task set the value to false if a notification should not be sent.
- When announcing by API
Two fields of type boolean have been foreseen (see our API documentation).
2. Define multiple recipients
You might want to inform several recipients of an upcoming delivery or pick-up. For example, the recipient and an invoicing team or you might simply want to receive copies of certain e-mails in your own mailbox.
Besides the contact details of the main contact, you can announce extra contact details. This information has to be added in separate fields.
- When creating a task manually
Two new fields will appear once the regular contact details are filled in.
- When announcing by API
Two new fields of type string have been foreseen (see our API documentation).