Actions
Move from a clear customer request to the next useful action.
Book a time in your calendar, collect details for your team or take another step you have agreed.
- Trigger
Customer asks to book a time
“Thursday afternoon works.”
Request received
- Look up
Check free times in the calendar
Google Calendar
3 times found
- Rule
30-minute slots, opening hours only
Your booking rules
Rule met
- Action
Book once the customer confirms
Control point: customer
Booked
- Notify
Tell the team in Slack
With the conversation attached
Sent
Choose how much happens on its own.
For each action you decide whether it happens straight away, after the customer confirms, or after someone on your team approves.
Straight away
Collect the order number and contact details.
After the customer confirms
Book a time in the calendar once the customer has chosen one.
After your team approves
Order changes and payments stay with a person.
What an automation means here
An automation connects the conversation to a tool: a booking in a calendar, a lead in your CRM, a message in Slack. Your rule decides whether it runs.
An action needs a tool, a rule and an owner.
- 01
Your tools
Calendar, CRM, payments or Slack: the tool your team already uses.
- Google Calendar
- Outlook Calendar
- Calendly
- Bokadirekt
- TimeCenter
- SimplyBook
- Muntra
- Stripe
- Swish
- HubSpot
- Pipedrive
- Zoho CRM
- Slack
- Zapier
- 02
A clear rule
For example: offer 30-minute slots, ask for the order number first, never promise a refund.
- 03
Someone who owns the follow-up
A person or inbox that gets what the agent cannot finish.
Questions people ask before they start
Can the agent change an order or take a payment on its own?
Only what you have agreed. Order changes and payments are typical examples your team can keep behind an approval step.
Do we need a developer?
No. Our team sets up the connection for you during onboarding.