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 helper
The helper's half of the same check-in. Deliberately says where her answer goes.
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 Cherry Mae Lorenzo, it is Michelle Wong from Demo Maid Agency. This is your {{checkin_milestone}} check-in.
How are you settling in? Is the work what we told you it would be, and are your rest days as agreed?
What you tell me comes to me, not to your employer. If something needs to be raised with them, we agree first how to do it.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.
- {{helper_name}}The helperfilled
- {{consultant_name}}The consultant handling this householdfilled
- {{agency_name}}The agency's namefilled
- {{checkin_milestone}}Which follow-up this isempty