How it works

Architecture, principles and the life of a message, from arriving on a channel to becoming a task, an action or an alert.

Updated:

Principles

  1. Deterministic core, AI as interpreter. The AI understands the customer and calls tools. The engine computes availability, holds and confirms. The AI never invents a time or a price.
  2. The database guarantees the rules. Double booking is impossible because PostgreSQL rejects overlapping allocations, not because the app "checks first".
  3. One operational truth, many views. A task is a single object; you see it in Today, as a list, in the calendar or on the map.
  4. API first. The dashboard, the bot, MCP and Wagy use the same services. If something cannot be done through the API, the API is missing it.
  5. The credential defines the business. A key or session always belongs to one project.

From input to action

Inputs → engine → interpretation → actions. This is the path of a conversation, not a mandatory sequence: the dashboard and API call the engine directly; forms go to a person. AI returns to the engine to validate each proposal before acting.

Inputs → Fiuit engine → AI interprets → Actions and outputs

AI does not execute on its own: it requests tools and the engine validates permissions, availability and confirmations. Bookings and tasks share one operational truth. Alerts depend on your rules and the channel; web chat replies during the conversation, without proactive reminders. The customer bot books services with scheduled times; the team creates queue tasks through the dashboard or API. Creating queued deliveries through chat: coming soon.

WhatsApp → booking “Any time tomorrow for a haircut with John?”

Fiuit checks real availability, offers options and holds the chosen slot for 10 minutes. It asks for missing details and confirmation; only then does the engine confirm the booking. John sees it on his schedule.

Telegram → scheduled booking “Do you have a table for four tomorrow at 20:00?”

Fiuit checks the service’s available times, holds the chosen slot for 10 minutes and asks for details and confirmation. When the customer confirms, the engine records the booking and the team sees it on their schedule.

The team creates the delivery in the dashboard with a queue-based service, the customer and address, without choosing a time. They can then assign, claim and complete the task in Work. Alerts depend on enabled rules. Automatically creating queued deliveries through chat: coming soon.

The life of a message

  1. Receive and organize. The channel verifies the source and discards repeated messages. The engine keeps context in the Inbox and respects pauses. Forms arrive for human attention, without automatic bot replies.
  2. Respect context. The customer and conversation are identified. If a person takes over, the bot stays quiet. Team and API actions have their own permissions and do not need to pass through AI.
  3. AI interprets. On conversational channels, the model understands intent, looks up business data through tools and asks for missing details. Audio is transcribed only where the channel supports it.
  4. Propose and confirm. The engine checks rules, permissions and availability. A chosen slot is held for 10 minutes; the customer confirms before it becomes a booking. If something changed, alternatives are offered.
  5. The engine executes. Idempotent operations prevent a retry from repeating an action. The database prevents overlapping bookings. Dates, prices and confirmations use real system data in message templates.
  6. Work, alerts and dialogue. A booking created through chat or a queued delivery recorded by the team in the dashboard appears as a task for the team. Active rules generate alerts and permitted actions. Fiuit also answers questions and hands off to a person; not every message needs to create a task.

Tasks, stages and actions

Each business defines the stages its work goes through and the actions that move a task from one to another (take, release, complete, "no-show"). An action can have effects: assign it to whoever runs it, release it, close it with an outcome. See Work and actions.

Rules

A rule says "when this happens, if this condition holds, do that": send a message, notify the team, wait, run an action. Conditions are simple expressions about the task, the customer or the time.

Security

Each business is isolated in the database itself, secrets are encrypted and every change is recorded in an audit log. You are responsible for your customers' data; Fiuit processes it on your behalf.

Where to go next