Get started
ConceptKey concepts
The objects ServiceReserve uses — organizations, forms, profiles, services, schedules, areas, and requests.
Updated Sep 30, 2026
A short tour of the objects ServiceReserve uses. Once these click, the rest of the docs read straight through.
Organization
Your workspace. Billing, team members, and bookings belong to it. One login can own or join several organizations. Switch between them, or click Create organization, from the organization menu at the top of the sidebar. Each organization has its own subscription.
Form
A booking flow — what your customers see. A form has its own branding, contact fields, and booking steps. Most workspaces have one form. Advanced setups have several, for different brands or locations.
Business profile
A location attached to a form. Profiles map to Google Business Profiles, which is where Reserve with Google connects. A profile has an address, phone, website, and an optional Google Place ID. Its service area, services, and schedule come from the form it's linked to — link locations to different forms to set them up differently. Each active profile is one seat on your subscription.
Service template, service, intake question
Services are organized as Template → Category → Service. Intake questions attach to the template, a category, or a service. Templates are workspace-level, so any form can reuse them.
Service schedule
Weekly working hours plus per-date overrides. It defines the times a customer can pick when the form's Scheduling step is on. One schedule can serve several forms.
Service area
A list of zip codes you cover. When the form's Service Area step is on, the form checks the customer's zip against your areas. Customers outside them can't finish booking.
Request
A customer submission. It stores contact fields (first_name,
last_name, email, phone), the address, selected_services,
intake_responses, and preferred_times. Its lead_status tracks
your pipeline: New → Contacted → Qualified → Won / Lost.
Abandoned session
A customer who started a booking but didn't finish. These are tracked separately from requests and listed under Abandoned. You can also fetch them with the abandoned-sessions API.
Related