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
Sharing helper profiles
Sent when a consultant decides a household should see someone. The rule behind it is locked, so this can never go out on its own.
When matching produces a ranked list — share helper profiles with the employer.
Sending a profile to a household is an external disclosure about a person. Someone has to decide it is warranted.
Preview
Rendered against a real case, not a mock-up.
Hi Mrs Serene Lee, this is Michelle Wong from Demo Maid Agency.
I have {{shared_helper_names}} for you to look at. Each profile shows what she has actually done, and where we do not yet know something we have said so rather than guessed.
You can see them here, compare them side by side, and tell me what fits and what does not. No rush — I would rather you take a few days than meet someone who was never right.This message must not be sent as it stands
No data for {{shared_helper_names}} 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
- {{agency_name}}The agency's namefilled
- {{shared_helper_names}}The helpers already shared with this householdemployer onlyempty