Resources

FAQ

Common questions about TimeSlotX, calendars, teams, integrations, security and enterprise use.

TimeSlotX coordinates more than a host and a calendar. It can handle routing, services, resources, capacity, registration, payments, waitlists and attendance as one connected scheduling flow.

Can different teams use different scheduling models?

Yes. A team can combine personal meetings, routed conversations, service appointments, resources, groups and programs while keeping shared controls. See Use cases.

Does TimeSlotX replace our calendars?

No. Calendars remain important sources of availability. TimeSlotX is the orchestration layer that evaluates additional rules and coordinates the outcome.

Can we integrate TimeSlotX into our product?

Yes. The developer platform is designed for embedded scheduling experiences, API-driven workflows and event-based integrations.

Is enterprise governance available?

TimeSlotX is built with permissions and operational controls in mind. Contact the team to discuss your security, governance and deployment requirements.

How is security handled?

Security is part of the architecture: access, permissions and data handling stay visible. Review the security overview or ask the team about your requirements.

How much does it cost?

Pricing depends on what you schedule. Tell the team what you need and they will help you scope the right setup.

Last updated 2 November 2026