Services and availability

Services, multi-resource requirements, schedules and how slots are computed.

Updated:

Services

A service is what the customer books.

FieldMeaning
duration_minLength of the service
step_minGrid for start times (every 15, 30 minutes…)
buffer_before_min / buffer_after_minCleanup or preparation time blocked around the booking
price_cents, currencyPrice shown by the bot (always from the database)
deposit_centsDeposit required to confirm (online charging: coming soon)
booking_paymentWhat is charged when confirming an appointment: none, deposit or total (the task's value)
lead_time_minMinimum notice (for example 60 minutes)
max_advance_daysHow far ahead customers can book
window_modeThe slot is a fixed window (deliveries: 14:00–16:00)
fulfillment_modescheduled (default, with a time slot) or queue (dispatch by queue, no fixed time)
location_modeWhere the service happens: at your business, at the customer's address, their choice or remotely
colorColor that identifies the service across all views
intake_formJSON Schema of extra data to collect (insurance, address…)
requirementsWhich resources the service needs at the same time

Window or dispatch: two fulfillment modes

Every service defines how the booking is fulfilled (fulfillment_mode):

  • scheduled (the default): the booking occupies a known time range — a fixed slot or, with window_mode, a window (deliveries from 14:00 to 16:00, with capacity per zone).
  • queue (dispatch, for water, gas or on-demand delivery): the booking has no fixed time — it joins a courier's backlog queue. The engine assigns it to the courier with the fewest active tasks, and each courier has a cap on active tasks at a time, enforced in the database. The queue uses the same states as a booking: pending → accepted → started → completed (or failed).

So the same delivery business can offer scheduled windows, immediate dispatch, or both.

Requirements

A requirement says: from this team, I need this many units. A service can have several; a slot exists only if all of them are free.

{
  "name": "Laser hair removal",
  "duration_min": 45,
  "buffer_after_min": 10,
  "requirements": [
    { "resource_group_id": "grp_professionals", "units": 1 },
    { "resource_group_id": "grp_lasers", "units": 1 },
    { "resource_group_id": "grp_rooms", "units": 1 }
  ]
}

With two professionals but only one laser, Fiuit will never offer two overlapping laser sessions.

Advanced options:

  • units: "party_size" — consume as many units as people (restaurants, classes).
  • offset_min / duration_min on a requirement — use a resource for part of the service only (for example the wash basin during the last 15 minutes of a hair color).

Schedules

Each resource has a schedule: weekly rules in the resource's time zone plus overrides for specific dates (closed, or special hours).

Hours past midnight. If the closing time is earlier than or equal to the opening time, the range ends the next day: ["20:00", "03:00"] shows as 20:00 – 03:00 (+1). The night belongs to the day it opens: Friday 20:00 – 03:00 (+1) runs until Saturday 03:00 even if Saturday is closed, and closing Friday removes that whole night. 24 hours is written ["00:00", "00:00"]. A range that overlaps the next day's early hours can't be saved. A booking can cross midnight without being cut, and asking for one day of times (bot, public booking, GET /v1/slots?day=) includes that night's times after 00:00. Daylight saving changes are respected: a night with a clock change lasts its real hours.

{
  "tz": "America/Sao_Paulo",
  "weekly": { "tue": [["09:00", "19:00"]], "sat": [["08:00", "12:00"], ["13:00", "16:00"]] },
  "overrides": [{ "date": "2026-12-24", "ranges": [["09:00", "13:00"]] }, { "date": "2026-12-25", "closed": true }]
}

Blocking time

A block is an override for the day: the whole day (closed) or some hours (saved as the ranges that are still open that day: the weekly hours minus the blocked time). In the panel the same dialog blocks from the Calendar (tap a free slot or drag over the grid), from each resource's page (Hours and blocks) and, separately, from the service (Pause for a period, which closes only that service and does not block the resources that provide it). You can pick one or several resources, a range of days, or repeat it every week. Tasks already in that time are flagged and never moved automatically. If several resources share the same schedule, the block applies to all of them.

The service's own days and hours

A service can also have its own window: the days and ranges when it is offered, using the same weekly editor as resources. Availability is always the intersection: the service window narrows the team's availability, it never widens it. If the service sets no window, any time its resources have is offered. The editor previews the real intersection before saving, and the bot explains the window when there are no slots.

Color

Each service picks a color from the theme palette. You see it in the calendar, Today, Work, the map and the statistics, next to the name: the color identifies, but it never replaces the text. If you do not pick one, Fiuit assigns a stable color automatically.

Where it happens

Each service defines its destination:

  • At your business: the task happens at the business address.
  • At the customer's address: deliveries, visits, in-home service.
  • The customer's choice: the customer decides when booking.
  • Remote: a video or phone session. No address is asked for or shown: not in the bot, not in web booking, not in notices. You can add the service's meeting link (your video call room): the bot shares it when confirming and reminders repeat it. Fiuit does not generate the link.

When the destination is the customer's address, creating the task suggests the address already on file (with autocomplete or manual entry, see Map and addresses). Each task keeps its own destination: changing it on one task does not touch the others or the profile. Saving the new address to the customer profile is optional and separate: it only happens if you tick the consent checkbox. The bot confirms the address, the consent and the booking as separate steps.

Forms with quantities and calculations

Besides text fields, a service's form supports:

  • Quantities: how many units of something (bottles, meters, people, devices).
  • Calculated fields: a simple expression that combines quantities and prices to show a total (for example water * 1500 + gas * 3000). The calculation is validated on the server and cannot touch other modules' or other businesses' data.

The dashboard has an editor and a preview: test the result before saving. When creating the task, the form asks for the quantities, applies the calculation and shows the total; the customer sees a clear summary of what they ordered. The quote stays frozen with the task: if the catalog price changes before confirming, the already-built task keeps its total; editing the quantities by hand recalculates with the current catalog.

How slots are computed

  1. Expand the schedules for the requested range, in each resource's time zone.
  2. Remove active bookings and holds (plus buffers) and manual blocks.
  3. Cut into candidate slots using the service duration and step.
  4. Apply lead time, max advance, cutoff rules and party size.
  5. Cross all requirements, trying team members according to the assignment strategy.
  6. Return a short, ordered list.

When nothing is available, the response includes unavailable_reason (closed, no_staff, no_equipment, no_space, lead_time, max_advance, cutoff, full) so the bot can explain why.

Each service's past results —completed, canceled, estimated revenue, peak time and CSV export— live in Results and sales.

Set up a service in the panel

In My business → Catalog, open the service and tap Edit. What each block does:

  • Who does it: pick a team. There can be several requirements at once, for example a bay and a mechanic for part of the time. Availability is the intersection of the service, the resources and the zone hours, minus blocks.
  • Own hours: a toggle. It allows several ranges per day (breaks are the gaps between them) and pausing by dates.
  • Advance notice: the minimum to book and Book up to (days).
  • Slot interval: the start grid (every 15, 30 minutes…).
  • Duration: fixed, or several durations (2 to 6) the customer picks, each with its own price. Full-day services let the customer pick only the day. There are buffers before and after.
  • Price: fixed, from, or taken from the form (form-only).
  • When booking: no charge, a deposit or full payment (full needs Mercado Pago).
  • Where: at the shop, at the customer's address (with zones), customer's choice, or online with a meeting link.
  • Bot offers: a toggle to keep the service out of the bot without pausing it.

Example: «Full service» of 2 h, team «Mechanics» plus a bay, a 30 % deposit and «Bot offers» on.

Create a service from text

In My business → Catalog → New service → Add with AI, describe the service in your own words, for example: «Haircut 30 min $ 5000 with optional beard».

  • Duration and price are read by rules; the name by AI.
  • You review and confirm before it is created.
  • An optional extra («with beard») is suggested as a separate service: services have no built-in add-ons.

You can also import several services at once from a photo of the price list or from examples, in the catalog sheet (import from photo / examples).

Pause and duplicate

Pausing stops offering the service for new requests through the bot, public booking, Wagy and MCP. Already scheduled tasks can be rescheduled, reassigned, completed and canceled with the usual permissions and validation. Pausing preserves schedule and capacity checks. Reactivating offers it again. Pause and deactivate are the same action.

Duplicate creates a paused « (copia)» with price, rules, requirements, form, products, independent hours and stages. It does not copy tasks, results or reviews. Catalog permission is required; without stage editing permission it uses the project base stages and warns you. Review the copy and reactivate when ready.

In the detail open ⋯ → Duplicate or Pause. Desktop also has a list menu. Wagy proposes both actions and waits for plan confirmation. MCP allows pausing with update_service(active=false, confirm=true); duplication does not yet have an MCP tool.

Delete and archive

Paused and archived are not the same. Paused is temporary: the service, product, team or resource shows dimmed in the catalog with “Reactivate” and does not appear in work filters or the bot. Archived is out of sight: it only shows under “Archived” (at the end of the catalog, collapsed and hidden when empty), with “Restore”.

⋯ → Delete really removes it if it has no history (no task, payment or record uses it) and archives it if it does; the dialog says which one happens. An archived item disappears everywhere (catalog, filters, pickers, bot, business site, Wagy and suggestions), but old tasks and payments keep showing its name. With future tasks it is not deleted: they are shown so you can reassign or cancel them first. Restore leaves it paused.

Filters and pickers offer only what is active; a paused or archived item is offered only when there are tasks with it, marked “(paused)” or “(archived)”. API and MCP: DELETE with ?mode=remove|archive|delete (admin permission; without mode it pauses, as always), GET …/removal to see what would happen and POST …/restore.

Test a flow

In My business → Stages, inside a flow, ▶ Test flow (on the phone, ▶ Test) walks through the draft on your screen, even if you haven't saved it. Only whoever can edit flows (the Owner) sees it.

  • View as: Team sees every screen; Customer sees only the items and buttons marked «Customer». If a stage has nothing for the customer, the test says «The customer does not see this stage: the team completes it» and offers to continue as the team.
  • Data: fill in each item or tap Fill with an example. A button does not advance if the items it requires are missing, and the test says which.
  • Paths: the stage's buttons and, for the team, the fixed exits that apply at that point (Cancel, Reschedule, No show and, during service, Close without completing with its reason).
  • Map and log: the map marks where the test is. What would happen lists each step: the notice to the customer or the team (with the message's example text), the assignment and the data that would be saved.
  • Restart goes back to the first stage.

The test saves nothing, notifies nobody, charges nothing and sends no messages, and leaves no tasks, history or audit entries. It does not simulate timing or deferred reminders, the customer link or payment.