Що таке SlotFlo?
SlotFlo is online booking software for service businesses. It gives you a public booking page for clients and an owner workspace for services, staff or resources, working hours, bookings, clients and daily schedule management.
FAQ
Прямі відповіді про сторінки бронювання SlotFlo, налаштування власника, клієнтів, персонал, CRM, білінг, приватність, локалізацію, мобільний QR, API та AI-ready функції.
SlotFlo is online booking software for service businesses. It gives you a public booking page for clients and an owner workspace for services, staff or resources, working hours, bookings, clients and daily schedule management.
SlotFlo is built for appointment-based service businesses such as barbershops, salons, beauty studios, tattoo studios, small clinics and similar teams. It fits businesses where clients need to choose a service, a person or resource, a date and an available time.
No. SlotFlo is not a marketplace. Your business gets its own booking page and workspace. Clients book with your business, not through a shared public marketplace.
SlotFlo reduces manual booking messages. Instead of asking clients back and forth about services, dates and available times, you publish a booking page where they choose from real available slots.
No. SlotFlo should not be used for emergencies, urgent regulated care or situations where immediate human response is required.
Yes. Salons can use SlotFlo when clients need to choose a service, provider or resource, date and available appointment time.
Yes. Barbershops can use SlotFlo for bookable services, staff or chairs, working hours and client appointment scheduling.
Yes. Tattoo studios can use SlotFlo for appointment requests and scheduled sessions, as long as the business controls service details, availability and follow-up with clients.
Small clinics can use SlotFlo for ordinary appointment scheduling where appropriate. SlotFlo must not be used for urgent regulated care, emergencies or any situation that needs immediate clinical response.
Yes, if the business is appointment-based and clients need to choose a service, bookable person or resource, date and available time.
A SlotFlo booking page is the public page your business shares with clients so they can choose services and available appointment times.
Customers see the booking information the business publishes, such as services, bookable units, dates, available times and the details needed to complete a booking.
Yes. Once setup is ready, you can share the booking link directly with clients from your website, social profiles, messages or other business channels.
Public booking pages are intended for direct client booking, not as SEO pages. Demo and private booking surfaces should remain noindex, and booking pages must not expose customer data in metadata or search files.
The core public booking page is included. Deeper customization depends on the selected plan and enabled features.
A customer chooses a service, staff member or resource, date and available time, then enters contact details and optional notes. The business sees the booking in the owner workspace.
The booking flow collects the contact and booking details needed by the business, such as name, email or phone when requested, selected service, time and optional notes.
Yes. Customers choose from the categories, services, staff or resources and available times that the business has configured.
After confirmation, the appointment appears in the owner workspace. Email confirmation or a manage link can be sent when the configured booking communication supports it.
The customer should check that the link is correct, try again later or contact the business directly. Private booking tokens or customer details should not be posted publicly for help.
A secure manage link is a private link for a specific booking. It can let a customer view, cancel or reschedule that booking when the business rules allow it.
Customers can cancel through the manage flow only when cancellation is enabled and the booking state allows it. Otherwise they should contact the business.
Customers can reschedule through the manage flow when the business allows rescheduling and another suitable slot is available.
Manage links are private because they give access to a specific booking. They should be shared only with the customer or business users who need them.
No. Booking manage tokens should not appear in search results, metadata, sitemap files, public content or support screenshots.
Owners can configure the business profile, location, services, categories, staff or bookable resources, working hours and public booking link. The owner workspace also handles bookings, clients, staff access, billing and advanced plan-gated features.
Set the business name, location and public details before sharing the booking page so clients understand which business they are booking with.
Add categories and services with the details clients need, then connect them to the right staff or bookable resources and availability rules.
Set regular working hours and any blocked dates or time off so SlotFlo can show only times the business intends to offer.
Share the booking link after the business profile, services, bookable units and working hours have been checked in the owner workspace.
A service is what the client books. A bookable unit is who or what delivers it, such as a staff member, room, chair, table or other resource.
Staff access is managed from the owner workspace where enabled. Owners should invite only people who need workspace access and give them the appropriate role.
Staff access should be limited by role and workspace permissions where those controls are available, so users only see the tools they need.
Public names should match the business setup. If a business does not want to show a personal name, it can use an appropriate resource or display name where configuration allows it.
The business can model bookable units as people or resources depending on how appointments are delivered. Public wording should stay clear for clients.
Availability is based on configured services, bookable units, working hours, blocked time and existing bookings. Customers should only see slots that match those rules.
A staff calendar is a workspace view of appointments for a specific staff member or bookable unit, helping the business manage the day.
SlotFlo supports blocking time through availability setup so holidays, time off or unavailable periods are not offered as bookable slots.
If no slot is available, the customer should choose another date, time, service or bookable unit, or contact the business.
SlotFlo checks availability during booking. If another customer takes the same slot first, the later customer should choose a different available time.
SlotFlo includes client records for booking operations. Deeper CRM workflows, import and export are plan-sensitive capabilities.
Client records can include booking contact details and appointment history needed for operations. They must not be exposed in public metadata or indexing files.
Visit history is tied to bookings and client records where available, so the business can understand past appointments without exposing them publicly.
Client import is a plan-sensitive capability and depends on the supported tooling and format. It should not be treated as a guaranteed one-click migration from every old system.
Client export is plan-sensitive and depends on enabled capabilities. Exported data should be handled carefully because it can contain customer contact details.
SlotFlo can send email-based booking communication where configured, including confirmations. The on-screen booking result remains important if email delivery is delayed or unavailable.
Manage links can be delivered by email where configured. Because they access a specific booking, customers should keep those links private.
SMS reminders are not currently public launch claims. Do not rely on them unless they are explicitly enabled for your plan or configuration.
Push reminders are not currently public launch claims. Do not rely on them unless they are explicitly enabled for your plan or configuration.
If booking email is unavailable, the customer should use the on-screen result and contact the business if they need confirmation. The business can still review bookings in the workspace.
Start with a 7-day free trial. Card required. Paid billing starts automatically unless you cancel before the trial ends.
A card is required to start the 7-day trial. Paid billing starts automatically after the trial unless you cancel before the trial ends.
Yes. Cancel before the trial ends to avoid the first paid subscription charge. If you cancel after a paid period starts, access remains active until the end of the current billing period. 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.
Subscription invoices and billing management depend on the Stripe-backed billing flow. Client appointment invoicing is not currently a public product claim.
Appointment payments and deposits are not currently a public SlotFlo product claim. SlotFlo billing is for your software subscription.
If a plan limit is reached, the business may need to reduce usage, change configuration or move to a plan that includes the needed capability. The pricing page shows plan limits.
No. Customer names, emails, phone numbers, notes and booking tokens must not appear in public search metadata, sitemap files or structured data.
Owner and platform routes are private workspace surfaces. They require the correct account access and are not public SEO pages.
Manage booking pages are private token-based surfaces for specific bookings. They should remain outside public search and sitemap output.
Runtime API responses are not public marketing pages. API access must be authenticated and scoped where it exposes protected business or customer data.
Demo booking pages should remain noindex, and the demo workspace must stay auth-gated. Demo surfaces should not become anonymous public access points.
SlotFlo has localized public UI across the supported system locales. Translation depth can vary by surface, so launch-critical copy should be checked before ads.
Only approved launch locales should be indexable. Other localized routes can render but should remain noindex until product approval.
Legal pages are available through localized public routes. Legal wording should stay aligned with the approved source text and should not be rewritten casually.
Booking pages can render localized interface text where the locale is supported. Business-entered service names and descriptions depend on what the business provides.
Arabic uses right-to-left layout support in the public UI where enabled. It should still be checked visually before launch campaigns.
A broad public app-store mobile app is not a current launch claim. Use the web workspace and only rely on mobile-specific flows that are explicitly enabled.
QR scanning is an advanced or plan-gated capability where enabled. It should not be presented as available to every customer by default.
Staff QR scanning depends on the enabled mobile or QR workflow and the user's permissions. It is not a standalone public promise for every plan.
Mobile and QR flows are advanced or plan-gated where enabled. The pricing page and workspace configuration should define what is available.
No confirmed public iOS release should be assumed from the FAQ. Do not rely on an iOS app unless SlotFlo explicitly announces that release.
Fully autonomous public AI booking is not a public launch claim. Any automated booking workflow must respect permissions, availability, business configuration and plan limits.
The AI assistant is a beta capability where enabled. It is assistive and should not be treated as a guaranteed replacement for business review or customer support.
SlotFlo includes controlled API surfaces for authorized business automation. API access is authenticated, scoped and plan-sensitive.
The Human API is for owner-authorized business automation. The Agent API is separate and designed for permissioned automated booking workflows such as availability checks and booking orchestration.
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 Agent API is designed for bots and AI agents that have permission to work with booking workflows.
Yes. Agent workflows should use controlled SlotFlo API and discovery surfaces instead of scraping customer-facing booking pages.
No. SlotFlo runtime API endpoints are not open unauthenticated public booking APIs. Public discovery files can describe the platform, but protected operations require scoped access.
The Agent API can support permissioned booking orchestration where enabled, but fully autonomous public AI appointment booking is not a public launch claim.
Customer data in API workflows must be protected by authentication, scope, permissions and tenant boundaries. It should not appear in public agent documents or SEO output.
Agents can learn public platform boundaries from /llms.txt, /llms-full.txt and /agent-api.txt. Protected API details still require authorized access.
Agent API access is plan-sensitive or configuration-gated. Businesses should not assume access unless it is enabled for their plan or account.
No. The AI assistant and Agent API are separate concepts. The AI assistant is a beta capability where enabled. The Agent API is designed for permissioned automated booking workflows such as availability checks and booking orchestration. 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.
Client import is available only where supported by the plan and tooling. The business should validate formats and data quality before relying on an import.
Client data export is plan-sensitive and should be handled as sensitive business data. Exports should be stored and shared carefully.
Supported import formats depend on the enabled tooling. SlotFlo should not promise unsupported formats or automatic migration from every legacy product.
Moving from a spreadsheet may be possible through supported import workflows, but it should be checked against the actual data format and plan capabilities.
Data portability depends on supported exports, plan capabilities and legal obligations. SlotFlo should not promise lossless migration for every workflow.
If checkout is unavailable, try again later and contact SlotFlo support if the issue continues. Do not share card details or private billing information in public channels.
If a booking page is unavailable, check the link and contact the business directly. The business owner can verify the booking page and availability setup.
If no availability is shown, try another service, date, time or bookable unit. The business can review working hours, blocked time and existing bookings.
If a manage link does not work, use the latest link from the booking flow or email and contact the business. Do not post private booking links publicly.
Contact the business for appointment-specific questions. Contact SlotFlo support for software, billing or account issues related to the SlotFlo product.