Skip to main content
Built for independent auto service See where it fits

Onboarding and support

A good rollout should feel guided, visible, and reversible.

Small shops do not need another login and a pile of documentation. They need the first workflow configured correctly and a clear view of what is ready.

Plan a supported rollout

Readiness is part of the product

Setup does not disappear after the first call.

The workspace keeps business details, locations, staff, SMS, email fallback, embed domains, QR signs, imports, and workflow setup visible as an ongoing health state.

  • Progress and recommended next step
  • Direct links to the exact setup screen
  • Integration and delivery warnings
  • Shop health and request-freshness signals
ShopStatus onboarding checklist and readiness state

The rollout path

Four checkpoints before customers depend on it.

The exact sequence can flex around the shop, but the core checks remain visible from first configuration through launch.

01

Shape the workspace

Business details, location scope, staff access, simple or advanced mode, and status language.

02

Connect communication

SMS mode, email fallback, portal links, domain settings, notification logs, and test sends.

03

Rehearse the visit

QR or front-desk intake, status updates, approval, customer reply, ready state, and closure.

04

Watch the launch

Readiness alerts, stale requests, failed notifications, audit activity, and advisor queue behavior.

Support surfaces

Enough visibility to support a shop without standing at its counter.

Readiness alerts

See disabled SMS, missing fallback, domain setup, stale work, and integration failures where the team works.

Delivery logs

Trace notification attempts, skipped sends, provider errors, retries, and related service requests.

Platform support

Switch into the correct shop and location with audited support access and a clear exit from support mode.

Account health

Review tenant setup, active requests, usage, integration state, onboarding, and critical account signals.

Owner-supported operations

A real support cockpit behind every shop account.

The platform view brings shop accounts, signups, health, global search, and critical support issues into one place.

ShopStatus platform support dashboard

Support questions

What support means here.

Who configures the first workspace?

Standard setup is collaborative. We help shape locations, staff, customer-facing language, intake, readiness, and the first advisor workflow.

Can support see every shop?

Platform-owner access can switch shop and location scope for support. Support mode is visible and changes are auditable.

What happens when a notification fails?

The product records delivery state and surfaces failed or skipped communication so the shop can use a fallback and investigate the provider issue.

Can a shop launch before every integration is configured?

Yes, when the remaining gaps are understood. QR and portal-link workflows can launch before SMS, while readiness banners keep the limitation visible.

Start with a clean first workflow

Plan the rollout at the same time as the product demo.

We will cover both what the shop sees and how it stays supportable after launch.

Book a supported walkthrough