FAQ
Straight answers about SlotFlo booking pages, owner setup, customers, staff, clients, billing, privacy, localization, mobile QR, APIs, and AI-ready features.
SlotFlo is online booking software for service businesses. It combines a public booking page with an owner and staff workspace for services, booking units, working hours, bookings, clients, and daily booking management. It is not a marketplace and should not be used for emergencies or urgent regulated care.
SlotFlo is online booking software for service businesses. It combines a public booking page with an owner and staff workspace for services, booking units, working hours, bookings, clients, and daily booking management. It is not a marketplace and should not be used for emergencies or urgent regulated care.
SlotFlo is online booking software for service businesses. It combines a public booking page with an owner and staff workspace for services, booking units, working hours, bookings, clients, and daily booking management. It is not a marketplace and should not be used for emergencies or urgent regulated care.
SlotFlo is online booking software for service businesses. It combines a public booking page with an owner and staff workspace for services, booking units, working hours, bookings, clients, and daily booking management. It is not a marketplace and should not be used for emergencies or urgent regulated care.
SlotFlo is online booking software for service businesses. It combines a public booking page with an owner and staff workspace for services, booking units, working hours, bookings, clients, and daily booking management. It is not a marketplace and should not be used for emergencies or urgent regulated care.
SlotFlo is designed for appointment-based service businesses such as salons, beauty studios, barbershops, tattoo studios, clinics, and similar teams. The useful fit is any business that needs customers to choose a service, a bookable unit or staff member, a date, and an available time.
SlotFlo is designed for appointment-based service businesses such as salons, beauty studios, barbershops, tattoo studios, clinics, and similar teams. The useful fit is any business that needs customers to choose a service, a bookable unit or staff member, a date, and an available time.
SlotFlo is designed for appointment-based service businesses such as salons, beauty studios, barbershops, tattoo studios, clinics, and similar teams. The useful fit is any business that needs customers to choose a service, a bookable unit or staff member, a date, and an available time.
SlotFlo is designed for appointment-based service businesses such as salons, beauty studios, barbershops, tattoo studios, clinics, and similar teams. The useful fit is any business that needs customers to choose a service, a bookable unit or staff member, a date, and an available time.
SlotFlo is designed for appointment-based service businesses such as salons, beauty studios, barbershops, tattoo studios, clinics, and similar teams. The useful fit is any business that needs customers to choose a service, a bookable unit or staff member, a date, and an available time.
A SlotFlo booking page is the public client booking surface for a business location. Customers use it to select services and available slots, but product policy keeps tenant booking pages out of Google indexing. Businesses can share links directly, while customization and limits depend on the active plan.
A SlotFlo booking page is the public client booking surface for a business location. Customers use it to select services and available slots, but product policy keeps tenant booking pages out of Google indexing. Businesses can share links directly, while customization and limits depend on the active plan.
A SlotFlo booking page is the public client booking surface for a business location. Customers use it to select services and available slots, but product policy keeps tenant booking pages out of Google indexing. Businesses can share links directly, while customization and limits depend on the active plan.
A SlotFlo booking page is the public client booking surface for a business location. Customers use it to select services and available slots, but product policy keeps tenant booking pages out of Google indexing. Businesses can share links directly, while customization and limits depend on the active plan.
A SlotFlo booking page is the public client booking surface for a business location. Customers use it to select services and available slots, but product policy keeps tenant booking pages out of Google indexing. Businesses can share links directly, while customization and limits depend on the active plan.
The customer booking flow asks the customer to choose category, service, booking unit or staff, date, time, and contact details. Confirmation appears in the product flow, and email confirmation or a manage link depends on configured email behavior and the data the customer provides.
The customer booking flow asks the customer to choose category, service, booking unit or staff, date, time, and contact details. Confirmation appears in the product flow, and email confirmation or a manage link depends on configured email behavior and the data the customer provides.
The customer booking flow asks the customer to choose category, service, booking unit or staff, date, time, and contact details. Confirmation appears in the product flow, and email confirmation or a manage link depends on configured email behavior and the data the customer provides.
The customer booking flow asks the customer to choose category, service, booking unit or staff, date, time, and contact details. Confirmation appears in the product flow, and email confirmation or a manage link depends on configured email behavior and the data the customer provides.
The customer booking flow asks the customer to choose category, service, booking unit or staff, date, time, and contact details. Confirmation appears in the product flow, and email confirmation or a manage link depends on configured email behavior and the data the customer provides.
A manage link is a secure tokenized link for a specific booking. It can support cancellation or rescheduling when the business rules allow it. Because it protects private booking access, it should not appear in metadata, sitemap files, public content, or search results.
A manage link is a secure tokenized link for a specific booking. It can support cancellation or rescheduling when the business rules allow it. Because it protects private booking access, it should not appear in metadata, sitemap files, public content, or search results.
A manage link is a secure tokenized link for a specific booking. It can support cancellation or rescheduling when the business rules allow it. Because it protects private booking access, it should not appear in metadata, sitemap files, public content, or search results.
A manage link is a secure tokenized link for a specific booking. It can support cancellation or rescheduling when the business rules allow it. Because it protects private booking access, it should not appear in metadata, sitemap files, public content, or search results.
A manage link is a secure tokenized link for a specific booking. It can support cancellation or rescheduling when the business rules allow it. Because it protects private booking access, it should not appear in metadata, sitemap files, public content, or search results.
Owners configure the business profile, location, services, categories, resources or staff, working hours, and booking link before sharing the public page. The owner workspace is also where calendars, clients, staff invitations, billing, and advanced plan-gated capabilities are managed.
Owners configure the business profile, location, services, categories, resources or staff, working hours, and booking link before sharing the public page. The owner workspace is also where calendars, clients, staff invitations, billing, and advanced plan-gated capabilities are managed.
Owners configure the business profile, location, services, categories, resources or staff, working hours, and booking link before sharing the public page. The owner workspace is also where calendars, clients, staff invitations, billing, and advanced plan-gated capabilities are managed.
Owners configure the business profile, location, services, categories, resources or staff, working hours, and booking link before sharing the public page. The owner workspace is also where calendars, clients, staff invitations, billing, and advanced plan-gated capabilities are managed.
Owners configure the business profile, location, services, categories, resources or staff, working hours, and booking link before sharing the public page. The owner workspace is also where calendars, clients, staff invitations, billing, and advanced plan-gated capabilities are managed.
SlotFlo separates services from the bookable units that deliver them. A bookable unit can represent staff, rooms, chairs, tables, or similar resources. Staff invitations and access control exist in the owner workspace, while public visibility of names should be handled carefully by business configuration.
SlotFlo separates services from the bookable units that deliver them. A bookable unit can represent staff, rooms, chairs, tables, or similar resources. Staff invitations and access control exist in the owner workspace, while public visibility of names should be handled carefully by business configuration.
SlotFlo separates services from the bookable units that deliver them. A bookable unit can represent staff, rooms, chairs, tables, or similar resources. Staff invitations and access control exist in the owner workspace, while public visibility of names should be handled carefully by business configuration.
SlotFlo separates services from the bookable units that deliver them. A bookable unit can represent staff, rooms, chairs, tables, or similar resources. Staff invitations and access control exist in the owner workspace, while public visibility of names should be handled carefully by business configuration.
SlotFlo separates services from the bookable units that deliver them. A bookable unit can represent staff, rooms, chairs, tables, or similar resources. Staff invitations and access control exist in the owner workspace, while public visibility of names should be handled carefully by business configuration.
Availability is based on configured services, booking units, working hours, blocked time, and existing bookings. The calendar gives owners and staff a working view of upcoming appointments. If no slot is available, the customer should choose another date, time, service, or unit.
Availability is based on configured services, booking units, working hours, blocked time, and existing bookings. The calendar gives owners and staff a working view of upcoming appointments. If no slot is available, the customer should choose another date, time, service, or unit.
Availability is based on configured services, booking units, working hours, blocked time, and existing bookings. The calendar gives owners and staff a working view of upcoming appointments. If no slot is available, the customer should choose another date, time, service, or unit.
Availability is based on configured services, booking units, working hours, blocked time, and existing bookings. The calendar gives owners and staff a working view of upcoming appointments. If no slot is available, the customer should choose another date, time, service, or unit.
Availability is based on configured services, booking units, working hours, blocked time, and existing bookings. The calendar gives owners and staff a working view of upcoming appointments. If no slot is available, the customer should choose another date, time, service, or unit.
SlotFlo includes client records for operational booking history and customer management. Client CRM, import, export, and deeper customer workflows are plan-sensitive capabilities. Customer names, emails, phone numbers, notes, and booking history must stay out of SEO metadata, schema, and public indexing files.
SlotFlo includes client records for operational booking history and customer management. Client CRM, import, export, and deeper customer workflows are plan-sensitive capabilities. Customer names, emails, phone numbers, notes, and booking history must stay out of SEO metadata, schema, and public indexing files.
SlotFlo includes client records for operational booking history and customer management. Client CRM, import, export, and deeper customer workflows are plan-sensitive capabilities. Customer names, emails, phone numbers, notes, and booking history must stay out of SEO metadata, schema, and public indexing files.
SlotFlo includes client records for operational booking history and customer management. Client CRM, import, export, and deeper customer workflows are plan-sensitive capabilities. Customer names, emails, phone numbers, notes, and booking history must stay out of SEO metadata, schema, and public indexing files.
SlotFlo includes client records for operational booking history and customer management. Client CRM, import, export, and deeper customer workflows are plan-sensitive capabilities. Customer names, emails, phone numbers, notes, and booking history must stay out of SEO metadata, schema, and public indexing files.
SlotFlo can use email-based booking communication where configured, including confirmations and secure manage links. It should not currently be marketed as sending SMS reminders or push reminders. Email delivery can fail or be unavailable, so the on-screen booking state remains important.
SlotFlo can use email-based booking communication where configured, including confirmations and secure manage links. It should not currently be marketed as sending SMS reminders or push reminders. Email delivery can fail or be unavailable, so the on-screen booking state remains important.
SlotFlo can use email-based booking communication where configured, including confirmations and secure manage links. It should not currently be marketed as sending SMS reminders or push reminders. Email delivery can fail or be unavailable, so the on-screen booking state remains important.
SlotFlo can use email-based booking communication where configured, including confirmations and secure manage links. It should not currently be marketed as sending SMS reminders or push reminders. Email delivery can fail or be unavailable, so the on-screen booking state remains important.
SlotFlo can use email-based booking communication where configured, including confirmations and secure manage links. It should not currently be marketed as sending SMS reminders or push reminders. Email delivery can fail or be unavailable, so the on-screen booking state remains important.
Start with a 14-day free trial. Card required. Paid billing starts automatically unless you cancel before the trial ends. SlotFlo billing is Stripe-backed, invoices and plan management depend on the billing flow, and appointment payments or deposits are not currently a public product claim. Subscription charges are not automatically refundable after payment. Cancellation stops future renewals but does not refund the current billing period, unless required by law. SlotFlo may issue a voluntary refund through support at its sole discretion. Where a voluntary refund is not legally required, non-refundable Stripe or other payment processing fees may be deducted where legally permitted.
Start with a 14-day free trial. Card required. Paid billing starts automatically unless you cancel before the trial ends. SlotFlo billing is Stripe-backed, invoices and plan management depend on the billing flow, and appointment payments or deposits are not currently a public product claim. Subscription charges are not automatically refundable after payment. Cancellation stops future renewals but does not refund the current billing period, unless required by law. SlotFlo may issue a voluntary refund through support at its sole discretion. Where a voluntary refund is not legally required, non-refundable Stripe or other payment processing fees may be deducted where legally permitted.
Start with a 14-day free trial. Card required. Paid billing starts automatically unless you cancel before the trial ends. SlotFlo billing is Stripe-backed, invoices and plan management depend on the billing flow, and appointment payments or deposits are not currently a public product claim. Subscription charges are not automatically refundable after payment. Cancellation stops future renewals but does not refund the current billing period, unless required by law. SlotFlo may issue a voluntary refund through support at its sole discretion. Where a voluntary refund is not legally required, non-refundable Stripe or other payment processing fees may be deducted where legally permitted.
Start with a 14-day free trial. Card required. Paid billing starts automatically unless you cancel before the trial ends. SlotFlo billing is Stripe-backed, invoices and plan management depend on the billing flow, and appointment payments or deposits are not currently a public product claim. Subscription charges are not automatically refundable after payment. Cancellation stops future renewals but does not refund the current billing period, unless required by law. SlotFlo may issue a voluntary refund through support at its sole discretion. Where a voluntary refund is not legally required, non-refundable Stripe or other payment processing fees may be deducted where legally permitted.
Start with a 14-day free trial. Card required. Paid billing starts automatically unless you cancel before the trial ends. SlotFlo billing is Stripe-backed, invoices and plan management depend on the billing flow, and appointment payments or deposits are not currently a public product claim. Subscription charges are not automatically refundable after payment. Cancellation stops future renewals but does not refund the current billing period, unless required by law. SlotFlo may issue a voluntary refund through support at its sole discretion. Where a voluntary refund is not legally required, non-refundable Stripe or other payment processing fees may be deducted where legally permitted.
Start with a 14-day free trial. Card required. Paid billing starts automatically unless you cancel before the trial ends. SlotFlo billing is Stripe-backed, invoices and plan management depend on the billing flow, and appointment payments or deposits are not currently a public product claim. Subscription charges are not automatically refundable after payment. Cancellation stops future renewals but does not refund the current billing period, unless required by law. SlotFlo may issue a voluntary refund through support at its sole discretion. Where a voluntary refund is not legally required, non-refundable Stripe or other payment processing fees may be deducted where legally permitted.
Public SEO must never expose customer names, email addresses, phone numbers, booking tokens, internal IDs, private owner settings, staff private data, API secrets, or payment details. Owner, platform, auth, API, embed, manage, and public booking token pages are private or noindex surfaces.
Public SEO must never expose customer names, email addresses, phone numbers, booking tokens, internal IDs, private owner settings, staff private data, API secrets, or payment details. Owner, platform, auth, API, embed, manage, and public booking token pages are private or noindex surfaces.
Public SEO must never expose customer names, email addresses, phone numbers, booking tokens, internal IDs, private owner settings, staff private data, API secrets, or payment details. Owner, platform, auth, API, embed, manage, and public booking token pages are private or noindex surfaces.
Public SEO must never expose customer names, email addresses, phone numbers, booking tokens, internal IDs, private owner settings, staff private data, API secrets, or payment details. Owner, platform, auth, API, embed, manage, and public booking token pages are private or noindex surfaces.
Public SEO must never expose customer names, email addresses, phone numbers, booking tokens, internal IDs, private owner settings, staff private data, API secrets, or payment details. Owner, platform, auth, API, embed, manage, and public booking token pages are private or noindex surfaces.
SlotFlo supports localized public UI across the system locales, with English, Spanish, German, Catalan, Ukrainian, Arabic, Turkish, and Bulgarian selected as indexable launch locales. Other locales can render content but remain noindex until product approval. Arabic must remain right-to-left compatible.
SlotFlo supports localized public UI across the system locales, with English, Spanish, German, Catalan, Ukrainian, Arabic, Turkish, and Bulgarian selected as indexable launch locales. Other locales can render content but remain noindex until product approval. Arabic must remain right-to-left compatible.
SlotFlo supports localized public UI across the system locales, with English, Spanish, German, Catalan, Ukrainian, Arabic, Turkish, and Bulgarian selected as indexable launch locales. Other locales can render content but remain noindex until product approval. Arabic must remain right-to-left compatible.
SlotFlo supports localized public UI across the system locales, with English, Spanish, German, Catalan, Ukrainian, Arabic, Turkish, and Bulgarian selected as indexable launch locales. Other locales can render content but remain noindex until product approval. Arabic must remain right-to-left compatible.
SlotFlo supports localized public UI across the system locales, with English, Spanish, German, Catalan, Ukrainian, Arabic, Turkish, and Bulgarian selected as indexable launch locales. Other locales can render content but remain noindex until product approval. Arabic must remain right-to-left compatible.
Mobile and QR scanning should be described as advanced or plan-gated where enabled. The codebase contains QR scanning and mobile-facing flows, but public copy should not claim broad app-store availability or iOS availability unless the release evidence exists.
Mobile and QR scanning should be described as advanced or plan-gated where enabled. The codebase contains QR scanning and mobile-facing flows, but public copy should not claim broad app-store availability or iOS availability unless the release evidence exists.
Mobile and QR scanning should be described as advanced or plan-gated where enabled. The codebase contains QR scanning and mobile-facing flows, but public copy should not claim broad app-store availability or iOS availability unless the release evidence exists.
Mobile and QR scanning should be described as advanced or plan-gated where enabled. The codebase contains QR scanning and mobile-facing flows, but public copy should not claim broad app-store availability or iOS availability unless the release evidence exists.
Mobile and QR scanning should be described as advanced or plan-gated where enabled. The codebase contains QR scanning and mobile-facing flows, but public copy should not claim broad app-store availability or iOS availability unless the release evidence exists.
SlotFlo is agent-ready by design. In addition to human-facing owner tools, SlotFlo includes controlled API surfaces for automation and a separate Agent API designed for bots and AI agents. The Agent API is intended for permissioned booking workflows such as availability discovery, booking orchestration, and integration handoffs without scraping customer-facing pages. Runtime API access is authenticated, scoped, and not exposed as crawlable public content. The Human API is for owner-authorized business automation. The Agent API is separate from the human-facing workspace and is not an open unauthenticated API. Runtime access can be signed, scoped, and plan-gated or enabled by configuration. Public discovery for agents should use /llms.txt, /llms-full.txt, and /agent-api.txt. /api/* endpoints are runtime APIs, not crawlable public documentation pages. SlotFlo does not claim fully autonomous public web-chat booking.
SlotFlo is agent-ready by design. In addition to human-facing owner tools, SlotFlo includes controlled API surfaces for automation and a separate Agent API designed for bots and AI agents. The Agent API is intended for permissioned booking workflows such as availability discovery, booking orchestration, and integration handoffs without scraping customer-facing pages. Runtime API access is authenticated, scoped, and not exposed as crawlable public content. The Human API is for owner-authorized business automation. The Agent API is separate from the human-facing workspace and is not an open unauthenticated API. Runtime access can be signed, scoped, and plan-gated or enabled by configuration. Public discovery for agents should use /llms.txt, /llms-full.txt, and /agent-api.txt. /api/* endpoints are runtime APIs, not crawlable public documentation pages. SlotFlo does not claim fully autonomous public web-chat booking.
SlotFlo is agent-ready by design. In addition to human-facing owner tools, SlotFlo includes controlled API surfaces for automation and a separate Agent API designed for bots and AI agents. The Agent API is intended for permissioned booking workflows such as availability discovery, booking orchestration, and integration handoffs without scraping customer-facing pages. Runtime API access is authenticated, scoped, and not exposed as crawlable public content. The Human API is for owner-authorized business automation. The Agent API is separate from the human-facing workspace and is not an open unauthenticated API. Runtime access can be signed, scoped, and plan-gated or enabled by configuration. Public discovery for agents should use /llms.txt, /llms-full.txt, and /agent-api.txt. /api/* endpoints are runtime APIs, not crawlable public documentation pages. SlotFlo does not claim fully autonomous public web-chat booking.
SlotFlo is agent-ready by design. In addition to human-facing owner tools, SlotFlo includes controlled API surfaces for automation and a separate Agent API designed for bots and AI agents. The Agent API is intended for permissioned booking workflows such as availability discovery, booking orchestration, and integration handoffs without scraping customer-facing pages. Runtime API access is authenticated, scoped, and not exposed as crawlable public content. The Human API is for owner-authorized business automation. The Agent API is separate from the human-facing workspace and is not an open unauthenticated API. Runtime access can be signed, scoped, and plan-gated or enabled by configuration. Public discovery for agents should use /llms.txt, /llms-full.txt, and /agent-api.txt. /api/* endpoints are runtime APIs, not crawlable public documentation pages. SlotFlo does not claim fully autonomous public web-chat booking.
SlotFlo is agent-ready by design. In addition to human-facing owner tools, SlotFlo includes controlled API surfaces for automation and a separate Agent API designed for bots and AI agents. The Agent API is intended for permissioned booking workflows such as availability discovery, booking orchestration, and integration handoffs without scraping customer-facing pages. Runtime API access is authenticated, scoped, and not exposed as crawlable public content. The Human API is for owner-authorized business automation. The Agent API is separate from the human-facing workspace and is not an open unauthenticated API. Runtime access can be signed, scoped, and plan-gated or enabled by configuration. Public discovery for agents should use /llms.txt, /llms-full.txt, and /agent-api.txt. /api/* endpoints are runtime APIs, not crawlable public documentation pages. SlotFlo does not claim fully autonomous public web-chat booking.
SlotFlo is agent-ready by design. In addition to human-facing owner tools, SlotFlo includes controlled API surfaces for automation and a separate Agent API designed for bots and AI agents. The Agent API is intended for permissioned booking workflows such as availability discovery, booking orchestration, and integration handoffs without scraping customer-facing pages. Runtime API access is authenticated, scoped, and not exposed as crawlable public content. The Human API is for owner-authorized business automation. The Agent API is separate from the human-facing workspace and is not an open unauthenticated API. Runtime access can be signed, scoped, and plan-gated or enabled by configuration. Public discovery for agents should use /llms.txt, /llms-full.txt, and /agent-api.txt. /api/* endpoints are runtime APIs, not crawlable public documentation pages. SlotFlo does not claim fully autonomous public web-chat booking.
SlotFlo is agent-ready by design. In addition to human-facing owner tools, SlotFlo includes controlled API surfaces for automation and a separate Agent API designed for bots and AI agents. The Agent API is intended for permissioned booking workflows such as availability discovery, booking orchestration, and integration handoffs without scraping customer-facing pages. Runtime API access is authenticated, scoped, and not exposed as crawlable public content. The Human API is for owner-authorized business automation. The Agent API is separate from the human-facing workspace and is not an open unauthenticated API. Runtime access can be signed, scoped, and plan-gated or enabled by configuration. Public discovery for agents should use /llms.txt, /llms-full.txt, and /agent-api.txt. /api/* endpoints are runtime APIs, not crawlable public documentation pages. SlotFlo does not claim fully autonomous public web-chat booking.
SlotFlo is agent-ready by design. In addition to human-facing owner tools, SlotFlo includes controlled API surfaces for automation and a separate Agent API designed for bots and AI agents. The Agent API is intended for permissioned booking workflows such as availability discovery, booking orchestration, and integration handoffs without scraping customer-facing pages. Runtime API access is authenticated, scoped, and not exposed as crawlable public content. The Human API is for owner-authorized business automation. The Agent API is separate from the human-facing workspace and is not an open unauthenticated API. Runtime access can be signed, scoped, and plan-gated or enabled by configuration. Public discovery for agents should use /llms.txt, /llms-full.txt, and /agent-api.txt. /api/* endpoints are runtime APIs, not crawlable public documentation pages. SlotFlo does not claim fully autonomous public web-chat booking.
SlotFlo is agent-ready by design. In addition to human-facing owner tools, SlotFlo includes controlled API surfaces for automation and a separate Agent API designed for bots and AI agents. The Agent API is intended for permissioned booking workflows such as availability discovery, booking orchestration, and integration handoffs without scraping customer-facing pages. Runtime API access is authenticated, scoped, and not exposed as crawlable public content. The Human API is for owner-authorized business automation. The Agent API is separate from the human-facing workspace and is not an open unauthenticated API. Runtime access can be signed, scoped, and plan-gated or enabled by configuration. Public discovery for agents should use /llms.txt, /llms-full.txt, and /agent-api.txt. /api/* endpoints are runtime APIs, not crawlable public documentation pages. SlotFlo does not claim fully autonomous public web-chat booking.
SlotFlo is agent-ready by design. In addition to human-facing owner tools, SlotFlo includes controlled API surfaces for automation and a separate Agent API designed for bots and AI agents. The Agent API is intended for permissioned booking workflows such as availability discovery, booking orchestration, and integration handoffs without scraping customer-facing pages. Runtime API access is authenticated, scoped, and not exposed as crawlable public content. The Human API is for owner-authorized business automation. The Agent API is separate from the human-facing workspace and is not an open unauthenticated API. Runtime access can be signed, scoped, and plan-gated or enabled by configuration. Public discovery for agents should use /llms.txt, /llms-full.txt, and /agent-api.txt. /api/* endpoints are runtime APIs, not crawlable public documentation pages. SlotFlo does not claim fully autonomous public web-chat booking.
SlotFlo is agent-ready by design. In addition to human-facing owner tools, SlotFlo includes controlled API surfaces for automation and a separate Agent API designed for bots and AI agents. The Agent API is intended for permissioned booking workflows such as availability discovery, booking orchestration, and integration handoffs without scraping customer-facing pages. Runtime API access is authenticated, scoped, and not exposed as crawlable public content. The Human API is for owner-authorized business automation. The Agent API is separate from the human-facing workspace and is not an open unauthenticated API. Runtime access can be signed, scoped, and plan-gated or enabled by configuration. Public discovery for agents should use /llms.txt, /llms-full.txt, and /agent-api.txt. /api/* endpoints are runtime APIs, not crawlable public documentation pages. SlotFlo does not claim fully autonomous public web-chat booking.
SlotFlo is agent-ready by design. In addition to human-facing owner tools, SlotFlo includes controlled API surfaces for automation and a separate Agent API designed for bots and AI agents. The Agent API is intended for permissioned booking workflows such as availability discovery, booking orchestration, and integration handoffs without scraping customer-facing pages. Runtime API access is authenticated, scoped, and not exposed as crawlable public content. The Human API is for owner-authorized business automation. The Agent API is separate from the human-facing workspace and is not an open unauthenticated API. Runtime access can be signed, scoped, and plan-gated or enabled by configuration. Public discovery for agents should use /llms.txt, /llms-full.txt, and /agent-api.txt. /api/* endpoints are runtime APIs, not crawlable public documentation pages. SlotFlo does not claim fully autonomous public web-chat booking.
Import and export are practical operations features for moving client and booking-related data where supported by the plan and tooling. Public copy can mention client import/export and portability, but it should not promise unsupported formats, one-click migrations, or lossless migration from every legacy tool.
Import and export are practical operations features for moving client and booking-related data where supported by the plan and tooling. Public copy can mention client import/export and portability, but it should not promise unsupported formats, one-click migrations, or lossless migration from every legacy tool.
Import and export are practical operations features for moving client and booking-related data where supported by the plan and tooling. Public copy can mention client import/export and portability, but it should not promise unsupported formats, one-click migrations, or lossless migration from every legacy tool.
Import and export are practical operations features for moving client and booking-related data where supported by the plan and tooling. Public copy can mention client import/export and portability, but it should not promise unsupported formats, one-click migrations, or lossless migration from every legacy tool.
Import and export are practical operations features for moving client and booking-related data where supported by the plan and tooling. Public copy can mention client import/export and portability, but it should not promise unsupported formats, one-click migrations, or lossless migration from every legacy tool.
If checkout, a booking page, availability, or a manage link is unavailable, the safest public guidance is to retry, check the link, choose another slot, or contact the business or SlotFlo support path as appropriate. Do not expose tokens or private customer details when asking for help.
If checkout, a booking page, availability, or a manage link is unavailable, the safest public guidance is to retry, check the link, choose another slot, or contact the business or SlotFlo support path as appropriate. Do not expose tokens or private customer details when asking for help.
If checkout, a booking page, availability, or a manage link is unavailable, the safest public guidance is to retry, check the link, choose another slot, or contact the business or SlotFlo support path as appropriate. Do not expose tokens or private customer details when asking for help.
If checkout, a booking page, availability, or a manage link is unavailable, the safest public guidance is to retry, check the link, choose another slot, or contact the business or SlotFlo support path as appropriate. Do not expose tokens or private customer details when asking for help.
If checkout, a booking page, availability, or a manage link is unavailable, the safest public guidance is to retry, check the link, choose another slot, or contact the business or SlotFlo support path as appropriate. Do not expose tokens or private customer details when asking for help.