Team
The roster of every person the AI can mention, book to, or transfer to. Each member has hours, time-off, an optional direct calendar, and routing rules. Single source of truth — Bookings and Messages read from here.
The Team page is where you describe the humans your AI can hand work to. If someone's name might be spoken on a call, if someone takes appointments, or if someone's line might ring during a transfer — they belong here. Routing, Bookings, and Messages all read from this roster; none of them maintain a parallel list.
Where to find it
The Team editor lives inside the Receptionist workspace. Open the Receptionist page and pick the Team tab from the section list, or go straight to its standalone page at /dashboard/receptionist/team. The exact same editor is also surfaced as a Settings page under Settings → Workspace → Team. Every route renders the same roster and the same UI; edit a member in any of them and it's the same data.
What each row holds
- Name and role — what the AI calls them on a call ("I can put you through to Sarah, our office manager").
- Hours — when this person is bookable. Often narrower than business hours (part-time, alternating schedules). The Bookings calendar uses these directly when offering slots.
- Time-off — multi-day blocks for vacation or leave. While a time-off block is active, the member is unbookable and untransferable.
- Transfer settings — the phone number to ring (if any), whether voicemail-fallback is on, and whether transfers are currently enabled at all.
- Calendar connection — Google Calendar OAuth or an iCal feed URL. Once connected, busy events on that calendar block the member from being booked, in real time as the calendar feed propagates.
- "Transferable" toggle — quick on/off without removing the row. Useful for someone temporarily out without losing their config.
How to use it
- 1Add a row for each person the AI might mention or book to. Empty roster is fine for solo operators — the system degrades to a single-bay setup with no transfer offer.
- 2Set hours that match reality. If a stylist works Tue/Thu/Sat only, only those days should be set — the AI will refuse to book them on Wednesday rather than overbooking.
- 3Connect calendars for anyone who books elsewhere. The point isn't to import their full schedule — it's so a Google event they put on their own calendar blocks the matching slot here. Saves the "double-booked again" call.
- 4Use time-off for known stretches (vacation, surgery, conference). For one-off days, prefer a per-member blackout date in Bookings → Settings.
- 5Test transfers. Set a transfer number, call your AI yourself, ask to be put through to that person, and listen for the ring on their line.
Team is the single source of truth — not a copy
Bookings reads members directly to populate the calendar. Messages references them when routing inbound texts. Receptionist routing rings their lines. None of these tabs maintain their own parallel team list — edit a member here and every consumer updates immediately.
Never auto-create members
The system never invents a teammate for you. An empty roster means "solo operator" or "no team needed" — your AI handles every call and never offers a transfer. If you want transfers offered, you have to add at least one row.
Common questions
I added a team member but bookings still show "available" on their day off.
Check their hours row — if Wednesday isn't in their schedule, no bookings should generate. If you connected a calendar, only "busy" timed events block; "free" events and all-day events don't. For known multi-day gaps, use time-off in the member editor instead of relying on the calendar.
My AI keeps offering to transfer to someone who's not available.
Open the member, set "transferable" off until they're back, or set a time-off block covering the period. The AI re-reads the roster live, so the next call after you save uses the new state.
What's the difference between blackout dates and time-off?
Blackout dates (Bookings → Settings) are one-off days the whole business or a specific resource is closed — a single holiday, an emergency closure. Time-off (Team → member editor) is for multi-day stretches owned by one person — vacation, leave. Use whichever matches the shape of the absence.
Do I need a row for myself if I'm the only person?
Only if you want transfers offered (the AI rings your line) or if you want the AI to mention you by name. For pure AI-handles-everything mode with no transfer, the empty roster is correct — adding a row would make the AI start offering to "transfer you to me," which is awkward.
Can a team member log in to EMOR?
Not yet. Multi-user access is on the roadmap. Today the workspace has one login that covers all admin work. Members on this roster are entities your AI knows about, not separate users of the dashboard.
Bookings
How team hours and time-off feed into what the AI can offer callers.
Receptionist
Where the Team editor lives within the workspace IA.
Related articles
Still stuck? Email support — we usually respond within a business day.