Troubleshooting guide
Salons & Spas: Diagnostic Guide
Salons & Spas: Diagnostic Guide organizes the decisions that matter for salons, spas, barbershops, esthetic practices, and wellness studios: the current workflow, ownership, implementation choices, rollout risk, and acceptance evidence.
Working artifact
Salons & Spas rollout scorecard
Use the scorecard to keep each phase tied to an operating outcome rather than a list of completed tasks.
| Phase | Required outcome | Proof before proceeding |
|---|---|---|
| Phase 1: Service menu and provider websites | Reduce or resolve clients book the wrong service or duration | Verified result involving scheduling and payment integrations |
| Phase 2: Booking, membership, and gift-card integrations | Reduce or resolve provider specialties and availability are unclear | Verified result involving mobile-first service comparison |
| Phase 3: Consultation and pre-visit information workflows | Reduce or resolve policies and preparation details are missed | Verified result involving local SEO, analytics, and reminder workflows |
Record the symptom before changing it
Clients book the wrong service or duration. Confirm who encounters it, where it occurs, and what changed before it appeared. Then distinguish the visible symptom from dependencies such as scheduling and payment integrations.
- Save exact error text
- Record the last known working date
- List recent code, content, vendor, DNS, or account changes
Separate reachability, data, and behavior
For Salon & Spa Technology Systems, confirm account ownership, current exports or backups, recovery options, and recent changes before touching production. Preserve exact errors and timestamps that may disappear after a restart or update.
- Reachability check for local SEO, analytics, and reminder workflows
- Data or content check related to service menu and provider websites
- Behavior check for booking, membership, and gift-card integrations
Use stop conditions
Frame the first scope around service menu and provider websites and one observable acceptance journey. Treat booking, membership, and gift-card integrations as a later phase unless the evidence shows it is a true dependency.
- No confirmed backup
- Unknown production ownership
- Security or payment data may be involved
Verify the repair in the real journey
Repair fits when the core remains sound. Extension fits when the boundary around scheduling and payment integrations is understood. Replacement fits when ownership, architecture, or operating risk prevents a responsible change.
- Service menu and provider websites
- Consultation and pre-visit information workflows
- Responsive and accessible web application delivery