The AI Colleague Catalog
You don't build an AI Colleague from a blank page — you hire one from a catalog of ready-made roles. Each role is a managed colleague: it runs on an expert playbook we build and maintain, so all you do is pick the role, name it, and fill in a few business details. It's live from there.
Overview
The catalog opens when you click Hire a colleague. Every card is a role shaped for a specific job — answering guests, qualifying leads, screening calls, or helping your own team. You pick the closest match; you can hire more than one and adjust each afterwards.
Because the roles are managed, the hard part — the wording, the escalation rules, the edge-case handling — is already done for you and kept up to date. You supply the facts that are specific to your business, and the colleague does the rest.
Where the catalog appears
Go to AI Agents → AI Colleagues and click Hire a colleague in the top-right. The catalog opens as a grid of role cards; picking one takes you to a short "name your colleague" step and then straight to its detail page.
Which roles appear depends on your workspace type:
| Workspace type | Roles in the catalog | Default |
|---|---|---|
| Short-term rental — bookings, Hostaway, channels | Guest Relations, Customer Support, Sales, Personal Receptionist, Internal Team Ops | Guest Relations |
| Long-term property management | Tenant Relations, Customer Support, Sales, Personal Receptionist, Internal Team Ops | Customer Support |
| Any other business (dental, vet, beauty, car rental, etc.) | Customer Support, Sales, Personal Receptionist, Internal Team Ops | Customer Support |
The roles
Pick the role whose "Best for" line matches the job. The four flagship roles below are fully managed. Two more — Customer Support (knowledge-base-anchored answers for any business) and Tenant Relations (long-term rentals) — appear based on your workspace type and give you an editable starting point you can tune.
- Airbnb / Booking.com operators on Hostaway
- Holiday lets and vacation rentals
- Co-hosts managing other people's STR units
- Anyone whose messages and calls are primarily inbound guest questions
- Long-term rentals (use Tenant Relations)
- Businesses with no reservation system (use Customer Support)
- Inbound sales lines for SaaS / B2B
- Product-info lines (“Tell me about your service”)
- Owner-acquisition and lead-qualification first touch
- Support questions about existing accounts (use Customer Support)
- Anything operational (use Guest Relations or Tenant Relations)
- A founder's or executive's private number
- Screening callers and capturing who, why, callback, urgency
- Anyone who wants messages taken, not calls put through
- Answering product or property questions (use Sales or Guest Relations)
- Putting callers through or making commitments — it never does either
- Answering your team's questions about reservations, properties, and guests
- Creating tasks and following your SOPs
- Internal-facing help — connect it to Slack in Settings
- Talking to guests or customers (it's internal only)
- Guest messaging or hotlines (use Guest Relations)
You fill in details, not a prompt
Managed colleagues don't ask you to write instructions. After you hire one, its Instructions tab shows a short Your details form — a handful of structured fields such as:
- Your business / company name
- Check-in and check-out times
- Access instructions (how guests get in)
- Where to escalate, and any policies specific to you
Fill them in and save. The colleague merges your answers with the expert playbook, the live reservation/listing data it reads each conversation, and your knowledge base — no prompt writing, no <!-- TODO --> markers to chase.
After you hire
A newly hired colleague lands on its detail page. The Instructions tab shows three things:
- Your details — the form above, saved as you type.
- How this colleague behaves — a plain-English summary of what it will and won't do, so you can check the playbook fits before it goes live.
- Live data — read fresh each conversation — a read-only panel showing exactly which reservation and listing fields it reads, and what it never sees.
From there, set the colleague's knowledge base access, then use the Test button in the header to try it before enabling it for real guests.
Hiring more than one
You aren't limited to a single colleague. Most operators hire a few — for example a Guest Relations colleague for guest messages and a Sales colleague for inbound leads — because each stays sharp when it's focused on one job.
Each colleague is independent: its own details, its own knowledge base access, its own enable / disable toggle. If you picked the wrong role, just disable it and hire the right one — nothing else is affected.