Use service status tags when you need to mark operational outcomes on a booking, such as completed or no-show style outcomes.
These tags are separate from the booking's basic details, but some terminal tags can move the booking into a completed state.
Where status tags appear
In List view, each active booking row can show a Mark Status control. The available status tags come from the location's active booking service status tags.
If a status tag is already applied, the row shows the tag name and colour. You can also clear the status.
One status tag at a time
Speako enforces a single service status tag per booking through this workflow. If a booking already has a status tag and you choose another one, treat the result as replacing the operational status.
Completed and no-show outcomes
Some status tags are terminal, including completed or no-show style tags. Applying a terminal status can set the booking to completed.
Completed bookings are no longer treated like ordinary active confirmed bookings. For example, cancellation is blocked for completed bookings, and applying new status tags to completed bookings is restricted.
💡 Note: You can clear tags in cases where the workflow allows it, such as reverting a completed status before applying something else.
When not to use status tags
Do not use service status tags to store customer notes, booking changes, or resource changes. Use booking details, notes, edit, reschedule, or cancellation for those tasks.
Status tags are best for operational workflow states: what happened, what needs attention, or how the booking should be treated by the team.
If the status option is missing
Check that the booking is not cancelled and that active service status tags exist for the location. If there are no active tags, the status filter and selector will not have useful options.
How this helps reporting and follow-up
Consistent status tagging helps the team review what happened after bookings were scheduled. For example, completed and no-show style outcomes are useful when reviewing attendance patterns or following up with customers.
Because terminal outcomes can affect what actions are allowed later, apply them only when the outcome is known.