When managing your Actions to create the perfect communication with your customers, define the type of each reminder you want to send through your cash collection cycle. Combine multiple channels to serve your goals—escalating from emails to phone calls—and get better results!
You will be able to choose between automatic and manual actions. The first type will roll in the background with nothing else but their setup to do, while the second requires their owner to complete them.
Set this from any Workflow's configuration panel, either by clicking on an existing action or creating one from scratch...
The only automated reminders you can set, they will be sent out following the conditions you defined and your organization's rules.
Trigger- time elapsed (in days) since the carrying invoice's issue/due date
Minimum contact delay- time elapsed since the execution of the workflow's previous action
Schedule- Your desired time of the day for automatic actions to be sent
They are convenient for your least formal communications—like the first stages of your cash collection process, where the interaction cannot easily become sensitive.
Displayed on their owner’s Actions tab from their due completion date, these actions must be validated or skipped. The workflow remains stuck at this step until then. They can be entirely reviewed and updated from a type change to a content update, including document attachments or notes logging.
Almost set up like their automated version, except you won't need to fill in a sender. Emails are emitted from the address of the member who completes the action.
With a higher opening rate than emails, they enable a less formal contact as thoroughly tracked.
❗This is a paying feature.
Calls work as reminders. They do not allow you to phone from your organization but display a script for their owners to complete with their notes.
Formalize the conversation tone. You can also send registered letters—for past due notices, for instance.
❗This is a paying feature
Destined to the assigned owner and not the client. The former are reminded of the expected behavior (limit access to a service, notify another team...) and can log their feedback before completing.