TimeSlotX uses one engine for every team. Each team picks the models it needs, and they all share the same controls.
By team
| Team | What they coordinate | Models |
|---|---|---|
| Sales | Buyer meetings routed by intent and ownership | Team routing, 1:1 meetings |
| Recruiting | Candidates, interview panels and rooms | Team routing, resource booking |
| Customer success | Onboarding, reviews and support sessions | Team routing, workflows |
| Professional services | Specialists, expertise and delivery capacity | Service appointments, resources |
By organization
| Organization | Start with | Add later |
|---|---|---|
| Small business | Meetings and appointments | Team routing, payments, groups |
| Service business | Appointments with staff, locations and payments | Resources, workflows |
| Education | Group sessions and programs | Waitlists, attendance |
| Growing team | One shared scheduling standard | Team-level routing |
| Platform | APIs and webhooks for embedded scheduling | MCP tools |
| Enterprise | Governance, permissions and policy across units | Integration planning |
Tip
Every row starts small and grows on the same setup. You never need to move to a different tool as you add teams.