What communication scenarios can Events handle?
Events support one-way automated communication in three directions:
- To customers — notify customers when a technician is scheduled, confirm order completion, or send service reminders. Messages go to the email or phone number on the customer's contact record.
- To Handyman Mobile users — notify field workers of new assignments, schedule changes, or upcoming tasks. Messages appear as push notifications or SMS on the mobile device.
- To office staff — alert coordinators or officials in charge when an order reaches a specific status, a deadline approaches, or approval you need.
What types of triggers can activate an Event?
Events can be triggered by conditions including:
- Order created, activated, completed, or invoiced
- A specific number of days before or after the planned order start or end date
- Service due date reached on a contract
- A previous Event being activated (chained Events)
- Manual activation by a coordinator
Can I combine Events for a complete workflow?
Yes. A typical multi-step workflow for service orders might combine several Events:
- Order created → notify preferred technician
- 3 days before planned start → send customer confirmation email
- Order completed → send customer completion summary
- Invoice created → notify accounts team
Each step is a separate Event template, all linked to the same order category and firing automatically as the order progresses.
See also: Events — an overview | Using Events for tracking SLA agreements