How it works
How Fiuit works under the hood
A complete explanation, no marketing: how a customer message becomes a booking or a delivery, how the team works and what the AI can and cannot do.
Three steps and your business runs itself
You set up what you have (staff, tables, machines) and Fiuit turns conversations into bookings and reminders.
- 1
Pick your business type
Start from a ready-made template (barbershop, aesthetics, clinic, restaurant, deliveries) and adjust services, prices and hours.
- 2
Connect your WhatsApp
Scan a QR code just like WhatsApp Web. Test the bot in the simulator before going live.
- 3
Let the AI handle it
The bot answers questions, offers real times and books them. Reminders go out through the rules you turn on. Jump into any conversation whenever you want.
Overview
All channels (WhatsApp, WebChat, Telegram, dashboard and API) come in through the same gateway and use the same scheduling engine. The AI is just another client of that engine: it has no shortcuts.
A booking · 1/9
The customer writes: “any slot tomorrow morning?”.
From "hi" to a concrete action
- 1
The message arrives
WhatsApp, WebChat or Telegram deliver the message. We verify the origin, discard duplicates and store it in the Inbox in milliseconds. If the channel is paused, your rule applies before anything else.
- 2
Understanding
If it is audio, we transcribe it. We identify the customer (one person, several channels) and the conversation. If a human took over, the bot stays quiet. On the WebChat, the bot asks for the contact details you configured before replying.
- 3
The AI asks the system
The model gets the business context, local date and time, the history and what your knowledge base knows, and can only call tools: find times, hold, confirm.
- 4
The system decides
Every call is validated and executed by the scheduling engine. If something does not exist or changed, the AI gets alternatives and asks again.
- 5
A reply with exact data
Date, time, service, price and address come from templates filled with the real result, never from free AI text.
- 6
The team sees it and acts
The task shows up in Today for whoever has it. Whoever works on it takes it, releases it or closes it with an outcome; flows and webhooks react to every action.
Resources, services and requirements
It all comes down to one question: which resource is consumed, how much, and when. A haircut, a table for 4 and a 2–4 pm delivery are the same object.
- Organization
- Your account. It can hold several businesses or locations.
- Business (workspace)
- One location with its own time zone, WhatsApp, bot and team.
- Resource
- What gets consumed: barber, doctor, table, room, machine, booth, vehicle, zone. Exclusive (one at a time) or pooled (covers, seats).
- Service
- What the customer books: duration, buffers, price, deposit and the resources it needs at the same time.
- Schedule
- When each resource works, with exceptions and holidays.
| Resources | The service requires | What limits it | |
|---|---|---|---|
| Barbershop | Each barber, with their own hours | 1 barber (customer's pick or next available) | Each barber's hours |
| Aesthetics | Professionals, machines and rooms | 1 professional + 1 machine + 1 room at the same time | The scarcest resource (usually the machine) |
| Clinic | Doctors and offices per location | 1 doctor + 1 office | Doctor and office |
| Restaurant | Dining room with covers per slot | Covers based on party size | Covers per slot |
| Deliveries | Zones (2-hour window) and couriers (backlog queue) | Capacity in the window and the postal-code zone, or a spot in the courier's queue | Deliveries per window and zone, or active tasks per courier (no fixed time) |
Holds and zero double bookings
A conversation can take minutes. So when the customer picks a time, we create a 10-minute hold. If they don't confirm, the slot is released. And the no-overlap rule lives in the database itself: even if two customers and the booking page try the same slot in the same second, only one succeeds.
- Held
- Awaiting deposit
- Confirmed
- Completed
Flows and automations
Flows of the kind when this happens, if so, do that. Each business builds its own or installs the examples for its industry.
- A reminder before a booking, as far ahead as you choose
- A message when a booking changes stage or is completed
- Conditions: only notify if the customer already missed 3 times, or if the delivery has not left in 2 hours
- Waits: a step that waits minutes, a time of day or an event
- Team alerts through Telegram, WhatsApp or email
- Quiet hours: nothing to customers between 9 pm and 8 am
The team work
The work shows up where the team already is: in the dashboard, on the phone and on Telegram.
- Today
- Each person day: staff see their own work, owners and managers see everything.
- Work
- All tasks as a list, a calendar or a map, with the same filters.
- Actions with effects
- Take, release, start and close with an outcome (completed, absent, refused, cancelled) and a form when needed.
- Team Telegram
- Alerts and the My day Mini App to open the schedule without logging in to the dashboard.
AI with clear limits
The AI can
- Understand text, voice notes, typos and changes of mind
- Find slots and offer 2 or 3 options
- Place a hold and ask for missing details
- Answer questions using the business information
- Hand the conversation to a person
The AI cannot
- Make up times, prices or addresses
- Confirm a booking without the system
- Use admin tools with a customer
- Follow instructions hidden in messages or files
- Access another business's data
Integrations
The dashboard is just another API client. Anything it does, you can do too.
- REST API
- Scoped tokens, idempotency, cursor pagination, RFC 9457 errors.
- Webhooks
- HMAC-signed events, automatic retries and a delivery log.
- SDKs
- TypeScript and Python, generated from the OpenAPI (used from the repository for now).
- MCP Coming soon
- AI agents can find times, book and run the business. Hosted server: coming soon.
- WebChat
- A one-line script puts the assistant on your site, with contact details and per-channel policy.
Security and LGPD
- Every business isolated at the database level
- Credentials and secrets encrypted
- Audit log of every change
- You are the data controller; Fiuit processes on your behalf