Service Setup Guide | ServiceHub Docs

What Services Control

A service definition is not just a name and price. It controls what customers can book, what technicians must collect, and what automation runs after completion.

•Booking page offerings (primary services + add-ons)
•Pricing logic (fixed, per-unit, choice-based, tiered)
•Estimated duration used by scheduling and dispatch
•Required intake fields per service
•Completion checklist templates
•Recurring due reminders from last completed service date

Pricing and Duration

ServiceHub supports multiple pricing modes. Pick one per service and keep naming consistent so quotes and invoices are clear.

Fixed Price

Single price per job. Best for repeatable packages.

Per Unit

Price × quantity. Supports a unit label (e.g., rooms, hours, panels).

Choice-Based

Customer selects one option (each option has its own price and optional duration).

Tiered

Different unit pricing by range (e.g., sqft bands).

💡 If time scales with quantity, set duration per unit/tier so calendar blocks stay realistic.

Intake Fields (Per Service)

Use intake fields to collect required information before dispatch. This reduces back-and-forth and avoids incomplete work orders.

•Field types include text, textarea, number, date/time, select/multiselect, checkbox, address, photo, and signature.
•Mark only truly necessary fields as required.
•Use short labels and clear helper text.
•For photo-heavy workflows, require photo intake on the services that need it (not globally).

Job Checklists

Checklists are service templates that technicians complete on jobs. They standardize delivery and give you a verifiable completion record.

•Create reusable checklist items per service.
•Set required vs optional items deliberately.
•Keep checklist text action-oriented and auditable.
•Use checklist comments for edge-case notes instead of adding too many checklist rows.

Recurring Service Reminders

Recurring reminders are configured at the service level and calculated from the last completed date for that client + service.

•Enable recurring reminders per service.
•Set interval in months (e.g., 12 for annual service).
•Set lead days (e.g., remind 30 days before due).
•When job status changes to completed, ServiceHub updates the next due/reminder dates.
•Reminder emails include a booking link pre-selecting that service.

💡 This is cost-safe by design: reminders are processed daily from due schedules, not by constant high-frequency polling.

Staff and Store Assignment

Assign services to stores and staff so booking, routing, and permissions stay accurate.

•Service-to-store mapping controls where a service is offered.
•Service-to-staff mapping controls who can perform that service.
•Use staff role correctly (owner/admin/manager/tech) for access boundaries.
•Staff profile photo and bio are used on booking flows when staff picker is enabled.
•Keep availability and service assignments aligned to avoid invalid dispatch suggestions.

Reminder Behavior and Notifications

Reminder outcomes depend on both business/store settings and contact data quality.

•Customer appointment reminders use business-level toggles and timing windows.
•Staff reminders require store-level enablement and staff opt-in preferences.
•Recurring due reminders rely on completed jobs plus valid client email.
•Incomplete client contact data can pause reminder delivery for that schedule.

Recommended Setup Checklist

•Create primary services first, then add-ons.
•Set pricing mode + duration before enabling booking page.
•Add intake fields only where needed.
•Add completion checklist templates for quality control.
•Assign stores and eligible staff per service.
•Enable recurring reminders for maintenance services.
•Run one test booking and one test completed job to verify automation.

Services Setup Guide