Glossary
Plain definitions of the words Zoop uses — customers, jobs, invoices, crews, plans, and more.
This page defines the words Zoop uses. When you see an unfamiliar term in the product, find it here. If a word behaves differently on a specific page, that page will explain it.
Zoop
The field service management software your business runs on. Zoop connects your customers, jobs, quotes, invoices, and payments in one place. It works in a browser and on mobile.
Tenant
Your business account in Zoop. Everything — customers, jobs, invoices, settings — belongs to your tenant. If you run two separate businesses, each gets its own tenant. You will mostly not see the word "tenant" in the product itself; Zoop just calls it your account or your business.
Team member
Anyone you add to your Zoop account. Every team member has one of three roles:
| Role | What they can do |
|---|---|
| Owner | Full access. Manages settings, billing, API keys, and team members. |
| Office | Creates and manages jobs, quotes, invoices, customers, and crews. Cannot manage billing or API keys. |
| Tech | Views and completes their own assigned jobs. Access is limited to their own work. |
See Team for how to invite and manage team members.
Customer
A person or company you do work for. A customer can be an individual (first name, last name) or a company (company name). Each customer gets a unique customer number and can have multiple contacts, locations, and billing profiles attached.
See Customers.
Job
A single unit of work for a customer. A job has a title, an optional description, a start and end time, and a status that tells you where it stands:
| Status | What it means |
|---|---|
unscheduled | Created but not yet on the calendar |
scheduled | On the calendar, not yet done |
done | Completed |
cancelled | Cancelled — kept for your records |
Jobs can be linked to a quote and an invoice.
See Jobs.
Recurring job (job series)
A job that repeats on a schedule — weekly lawn care, monthly HVAC maintenance, quarterly inspections. The schedule lives in a job series, which holds the recurrence rule, timezone, and the template details (line items, assigned crew) that Zoop copies onto each new job occurrence automatically. Editing the series affects future jobs; past jobs are unaffected.
See Recurring jobs.
Quote
A priced proposal you send to a customer before work begins. A quote has a status that tells you where it stands:
| Status | What it means |
|---|---|
draft | Still building it — not sent yet |
quoted | Sent to the customer |
converted | Accepted and turned into a job or invoice |
archived | Closed without converting |
Customers can accept a quote through a shared link — they do not need a Zoop account.
See Quotes.
Invoice
A request for payment you send to a customer after (or during) work. An invoice can reference a job, a quote, both, or neither — they are independent records. Invoices go out by email or SMS, and customers pay through a link — no login required. Here is what each status means:
| Status | What it means |
|---|---|
draft | Still building it — not sent yet |
sent | Sent to the customer, payment not yet received |
processing | Payment received and being confirmed |
paid | Fully paid |
overdue | Past due date, still unpaid |
void | Cancelled — kept for your records |
See Invoices.
Plan
A recurring billing agreement with a customer. A plan runs on a schedule — weekly, monthly, annually, or any cadence you choose — and generates invoices automatically. If your customer has a saved payment method on file, Zoop can charge it each cycle without them needing to do anything.
See Recurring billing.
Pricebook / catalog item
Your library of services, products, labor rates, fees, bundles, and discounts. Each entry is a catalog item with a name, unit price, and kind. When you build a quote or job, you pull items from the pricebook instead of typing line items from scratch.
Catalog items are grouped into catalog categories to keep the list organized.
See Pricebook.
Crew
A named group of team members that you assign to jobs as a unit — "Tuesday crew", "HVAC team A". A crew is a scheduling convenience: one assignment covers all the members in it. A team member can belong to more than one crew at the same time.
See Team.
Storefront
Your public-facing business page, hosted by Zoop. It shows your business name, contact info, service hours, service area, and the services you offer. If you turn on the booking widget in Settings → Storefront, customers can request appointments directly from the page.
See Storefront.
Customer portal
A private page where one specific customer can view their invoices, pay outstanding balances, and manage their saved payment methods. Zoop gives each customer their own unique link — they do not need a Zoop account to use it.
See Customer portal.
Dispatch
The view that owners and office members use to assign jobs to team members across a day. The dispatch board shows who is working, what they are assigned to, and where. Techs see their own route view — dispatch is the scheduling surface above it.
See Dispatch.
Route
A tech's ordered list of stops for a given day — their jobs and calendar events in the sequence they plan to visit them. Routes can be reordered by dragging. Zoop flags any stop that looks at risk of running late.
See Dispatch.
Note
A text record attached to a customer, job, quote, or other subject. Notes are internal — customers never see them. You can pin a note so it stays at the top, and Zoop saves every edit as a revision so nothing is lost. Zoop's AI agent can also create notes automatically.
See Notes.
Tax rate
A named percentage — for example, "State sales tax 8.25%" — that you apply to line items on invoices and plans. You set up tax rates once in Settings → Tax rates, then select them when building an invoice or plan. You can have more than one tax rate active at the same time.
See Settings.
MCP
Model Context Protocol — an open standard that lets AI tools (such as Claude Desktop) connect to Zoop and read or write your data. If you are not building an integration, you will not need this. For developers: Zoop's MCP server exposes the same tool layer the in-product AI agent uses. Access requires an API key or OAuth token with the appropriate scopes.
See MCP.
Scope
A permission that controls what an API key or OAuth token is allowed to do. If you are not building an integration, you will not need to set scopes. For developers: scopes follow a read:<entity> / write:<entity> pattern — for example, read:jobs lets a token list and view jobs, while write:jobs lets it create and update them. A token can only do what its scopes allow.
See Scopes.
API key
A long-lived credential that lets an external script or tool connect to Zoop without signing in through a browser. Most users will not need one. If you are building an integration, Zoop issues two kinds:
- User key (
zoop_uk_…) — acts as the team member who created it. Use this for actions that need to record who made a change. - Tenant key (
zoop_tk_…) — acts as the account itself, with no individual user attached. Use this for read-heavy or reporting integrations.
Create keys in Settings → API & MCP. You need the owner role to do this. Zoop shows you the key once when you create it — copy it then, because you cannot retrieve it again.
See API keys.