> ## Documentation Index
> Fetch the complete documentation index at: https://docs.comforthub.app/llms.txt
> Use this file to discover all available pages before exploring further.
# How Comfort Hub runs
> The business in one page: what we sell, what a visit looks like, and which systems carry each step
export const Touches = ({systems}) =>
Systems involved:{" "}
{systems.split(",").map((s, i) =>
{i > 0 ? " ยท " : ""}
{s.trim().replace(/-/g, " ")}
)}
;
Comfort Hub sells, installs, services and maintains heating and cooling equipment for homeowners. Every piece of equipment a customer buys becomes an **asset** on their account, and that asset is what brings them back: it needs fixing, it needs looking after, and it is covered by a warranty or by a plan.
## Every visit has the same shape
A **work order** says what the job is. An **appointment** puts a technician at the property on a day. The technician does the work in the app and taps **Complete**. An **invoice** bills the customer. A **payment** settles it. The only things that change from visit to visit are *why* the customer is visited and *whether* they are billed for it.
```mermaid theme={null}
flowchart LR
P[Lead] -->|converted| C[Customer + property]
C --> W[Work order]
W --> A[Appointment]
A -->|done in the app| I[Invoice]
I --> M[Payment]
M -->|receipt| C
```
## Five kinds of visit
| Visit | Why | Billed? |
| ------------ | ------------------------------------------ | -------------------------------------- |
| Installation | They bought equipment | Yes |
| Service | Something broke | Yes |
| Maintenance | Yearly upkeep; produces a certificate | Yes |
| Warranty | Covered repair | No |
| Plan visit | A visit the customer's subscription covers | No, logged on the subscription instead |
The work order's lines decide this. Every line is billed to the customer, to warranty, or to the subscription, and the job is invoiced only for what is billed to the customer. The rule, and what happens when the lines do not settle it, is on [How invoicing works](/handbook/invoicing/how-invoicing-works).
## Who does what
* **The office works in Zoho.** Leads, customers, booking, checklists, timesheet approvals, and anything that needs a record edited by hand.
* **The engine (Supabase) runs in the background.** It mirrors Zoho both ways, makes the billing decision, builds invoices, talks to QuickBooks, sends the emails, and runs the phone. Nobody edits it by hand day to day.
* **Technicians work in the app.** Their day, the work order, checklists, parts, quotes, hours, time off, the phone and texts.
* **QuickBooks holds the books.** Customers, items, invoices, payments. The card processor behind the pay page posts each payment into it; the engine records the same payment and does the paperwork. See [How payments work](/handbook/payments/how-payments-work).
* **The customer sees email and the pay page.** A booking confirmation, an invoice with a link to pay, and a receipt.
## The chapters
The rest of the handbook walks this loop in order. Each chapter opens with a page like this one, then has a short page per task.
From a lead to a customer with all their records.
The work order, the appointment, the billing decision.
What the technician does in the app.
How Complete becomes an invoice.
The pay page, QuickBooks, the receipt.
Sync, the monitor, and what to do when a check fails.
## Related
* [The customer lifecycle](/handbook/the-business/the-customer-lifecycle)
* [How it all fits together](/systems/how-it-all-fits-together)
* [Who is the source of truth](/systems/who-is-the-source-of-truth)