Trigger: A LatePoint booking’s status changes (LatePoint)
- Action: Send Email (Email)
Invite customers who cancel to book again
When a LatePoint booking is cancelled, the customer gets a kind note asking them to pick another time.
Start workflows from LatePoint bookings, status changes, reschedules and payments, and update bookings and customers.
Triggers and actions
Every step LatePoint adds to FlowWP, named and described as it appears in the editor, with the plan that includes it.
Events in LatePoint that can start a workflow.
Booked by a customer, or added by staff. Optionally only for one service or agent.
Booking
Customer
Approved, cancelled, completed, a no-show… Optionally only when it becomes one status, or only for one service or agent.
Booking
Customer
Moved to another date or time, by the customer or by staff. The time it had comes with it.
Booking
Customer
Booked before for
When someone books for the first time, or staff add them.
Customer
Paid online, or recorded by staff. Card holds and failed payments are left out.
Payment
Order
Customer
What a workflow can do in LatePoint.
As LatePoint’s bookings screen does, so its notifications go out as usual.
Booking
Customer
If one already has that email address, it is returned as it is.
Customer
Its date, status, service, agent and customer, for the steps after.
Booking
Customer
LatePoint steps run inside WordPress, on your own server. FlowWP only contacts an outside service when you add a connection to one or use a step that needs it.
Nothing runs until you activate a workflow, and every run is recorded step by step.
Templates
When a LatePoint booking is cancelled, the customer gets a kind note asking them to pick another time.
When a customer or your staff move a LatePoint booking, its agent gets the old time and the new one side by side.
Start with a template or a blank canvas. Nothing runs until you activate it.