> For the complete documentation index, see [llms.txt](https://docs.diro.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.diro.app/en/getting-started/what-is-diro.md).

# What Is DIRO

DIRO replaces three things that are usually separate: a **schedule book**, a **way to accept payments**, and **financial records**. Everything is combined into one, and customers can book on their own, 24 hours a day.

## What you get

**Bookings.** A branded storefront with your own logo and colours. Customers choose a service, date, time, provider, and room — only truly available slots are shown, so there's no double-booking.

**Payments.** Customers pay upfront by bank transfer, e-wallet, card, or QRIS. Invoices and payment receipts are sent automatically. Money goes into your wallet and can be withdrawn to a bank account.

**Operations management.** Multiple branches, staff with their own schedules and access rights, rooms and equipment as bookable resources, plus a customer database.

**Revenue growth.** Vouchers, memberships, add-ons at checkout, automatically calculated provider commission, and customer reviews.

**Visibility into the numbers.** A daily dashboard, commission reports, and payment reconciliation that matches every booking with its transaction.

## Terms used in this documentation

| Term           | Meaning                                                                                                                                                                                                         |
| -------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Business**   | Your main account on DIRO. One business can have multiple branches.                                                                                                                                             |
| **Branch**     | A physical location. Has its own address, operating hours, and services.                                                                                                                                        |
| **Service**    | What is sold and can be booked — a haircut, a yoga class, a therapy session.                                                                                                                                    |
| **Add-on**     | An extra paid item at checkout — a hair mask, a towel, a drink.                                                                                                                                                 |
| **Resource**   | Something that has its own availability and helps determine slots. There are two kinds: **provider** (the person doing the work, who earns commission) and **room/equipment** (which does not earn commission). |
| **Staff**      | A team member with an account to log in to the portal. Different from a provider — staff is about *access rights*, provider is about *who does the booking*.                                                    |
| **Slot**       | A single bookable block of time. Calculated from the service schedule, the provider's schedule, and the branch's opening hours.                                                                                 |
| **Voucher**    | A discount code or membership that customers can redeem.                                                                                                                                                        |
| **Wallet**     | Your business's balance on DIRO, made up of paid bookings.                                                                                                                                                      |
| **Storefront** | The public page where customers book, at `business-name.diro.app`.                                                                                                                                              |
| **Portal**     | Your dashboard at `portal.diro.app`.                                                                                                                                                                            |

## How the pieces connect

```mermaid
flowchart TD
  B["Business"] --> C["Branch"]
  C --> L["Service"]
  C --> R["Resource<br/>provider & room"]
  C --> S["Staff"]
  L --> J["Service Schedule<br/>weekly + specific date"]
  R --> JR["Resource Availability<br/>weekly"]
  J --> SL{{"Slots shown<br/>on the storefront"}}
  JR --> SL
  SL --> BK["Booking"]
  BK --> TR["Transaction & Wallet"]
  BK --> KM["Provider Commission"]
```

The slot a customer sees is the **intersection of two things**: the service schedule and the availability of the resource assigned to that slot. If either one is closed, the slot doesn't appear.

{% hint style="warning" %}
A branch's operating hours are **informational only** — shown to customers, but they don't restrict slots. If your service schedule is open at 9 PM while the branch is listed as closing at 8 PM, the 9 PM slot still appears. Only the service schedule and resource availability determine slots.
{% endhint %}

This is the most common cause of "why isn't my slot showing" — see Frequently Asked Questions.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.diro.app/en/getting-started/what-is-diro.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.