Schedule a Task
Most of what an AI Colleague does is answer. This action lets it act: when a guest reports something broken, the colleague checks whether they want it dealt with, and then files a real task against the right property — dated today, ready for a coordinator to pick up. Nobody has to read the thread first.
The whole exchange. The guest reports, confirms, and is told it is handled — and a task exists at the end of it.
Turning it on
Open your colleague, go to the Overview tab, and click + Add action under “Actions it can take”. Pick Schedule a task.
It is available to every colleague, including managed ones — there is nothing to configure, no URL to point at and no schema to write. Once added it appears in the actions list and starts working on the next guest message.
To take it away again, click the card in the flow and choose Remove this action.
It always asks first
Your colleague will never file a task off the back of a passing remark. When it spots a report worth acting on, it asks the guest to confirm and then stops — it cannot create anything in the same reply.
Only when the guest actually answers can the task be created. That is enforced in the platform, not left to the colleague’s judgement, so “the tap drips a bit but honestly it’s fine” does not become a work order.
What lands in your task list
Each task the colleague files arrives with:
- A type — Maintenance for a repair, Custom for anything else needing a coordinator
- The right property — taken from the guest’s reservation, never guessed
- Today’s date — a guest report is same-day work, so it appears in today’s queue rather than sitting under Unscheduled
- No assignee — it is yours to triage and assign
- Notes describing what the guest reported and what needs to happen
- Links back to the reservation and the conversation it came from
Tasks from guests are marked as coming from a guest report, so you can tell them apart from work your team scheduled.
Where it does and does not run
Chat only. The action runs on guest messages — Airbnb, Booking.com, direct and any other synced channel. It does not run on phone calls: a caller reporting a fault is escalated to a person instead, because a live call deserves one.
Only when the guest is known. The colleague needs a reservation to know which property to file against. If a message cannot be matched to one, it will answer normally but will not file anything.
Trying it before it meets a guest
Add a case in the Test Suite tab, write what a guest would say, and assert that the colleague schedules a task. Test runs never create real tasks — they report what would have been created.
It is worth testing both directions: a clear report that should produce a task, and a passing complaint that should not.
Related
- Coordination Tasks — where the created work lives, and how to assign and track it
- Escalation Handling — the other way a conversation reaches a human
- How Guest Message Automation Works — the pipeline this action sits inside