Communication
Message templates
Each template is bound to the workflow rule that would send it, so a message inherits that rule's autonomy. Nothing here sends itself.
Templates
8 in use
- Sharing helper profilesemployer · whatsapp
- Asking for a documentemployer · whatsapp
- Proposing interview timesemployer · whatsapp
- Check-in — the householdemployer · whatsapp
- Check-in — the helperhelper · whatsapp
- Arrival briefingemployer · whatsapp
- Payment reminderemployer · email
- Replacement decisionemployer · whatsapp
Check-in — the household
The household's half of a check-in. The helper is asked separately, and neither sees the other's answer.
When an aftercare check-in falls due — send the request to the employer and the helper.
Preview
Rendered against a real case, not a mock-up.
Hi Mrs Angeline Tan, it is Sarah Tan — this is the {{checkin_milestone}} check-in for Maria Santos.
How is it going? Anything that is not working, however small, is easier to sort out now than in three months.
I am asking Maria Santos separately. What each of you tells me stays with me unless you want it passed on.This message must not be sent as it stands
No data for {{checkin_milestone}} on this case. A blank would be worse than a gap — the braces stay so nobody sends it by accident.
Fields this message merges
A field belonging to one side can never be merged into the other's message.
- {{employer_contact}}Who to address in the householdemployer onlyfilled
- {{consultant_name}}The consultant handling this householdfilled
- {{checkin_milestone}}Which follow-up this isempty
- {{helper_name}}The helperfilled