Skip to Content
Get StartedOperator Quickstart

Operator Quickstart

console.sophosic.ai
WorkspaceActive
Tasks24
Revenue$8.2k
Review inboxOpen
Publish siteOpen
Workspace consoleWorkspace setup, daily operations, public-site controls, and launch decisions

This guide walks an operator through the minimum useful setup for a workspace.

Outcome

By the end, the selected workspace should have accurate business basics, a public site shell, at least one sellable or bookable path, customer communications, required integrations, and a completed customer-path pass.

Before You Start

You need:

Console access for the workspace

Make sure the operator can open the intended tenant and has permission to update settings, content, products, bookings, and integrations.

Expected public URL

Keep the workspace slug or production domain visible while testing so console changes are checked against the same customer-facing host.

Business profile details

Bring the public name, address or service area, timezone, currency, hours, phone, email, and support ownership before editing the site.

Payment owner access

If products, bookings, invoices, or deposits are enabled, have the person who can resolve Stripe Connect requirements available.

Google account access

Have the right Google account ready for Analytics, Ads, Business Profile, or Calendar only when those integrations are part of launch.

Step 1: Choose A Workspace

Open the console and select the workspace. If you are already inside the admin shell, use the workspace switcher before making changes.

The selected workspace controls all flat admin routes. If the wrong workspace is selected, changes will apply to the wrong business.

Confirm the selected workspace by checking the business name, slug/domain, and a known record such as a product, service, or customer. This is especially important for agencies and internal support users who manage several workspaces from one account.

Step 2: Complete General Settings

Open Settings > General and confirm:

  1. Public business name.
  2. Location and service area.
  3. Timezone and currency.
  4. Operating hours.
  5. Support email and phone.
  6. Site status.

These values feed public pages, booking availability, notifications, checkout, and local business metadata.

Treat timezone and currency as launch-critical. Timezone affects bookable slots and notification timing; currency affects products, services, checkout, invoices, refunds, and customer expectations. Change either only when the financial or operations owner agrees.

Step 3: Configure The Public Site

Open Website and configure:

  • Homepage structure.
  • Navigation links.
  • Footer sections and legal links.
  • Brand colors, logo, typography, and imagery.
  • Custom pages for services, about, FAQs, policies, and landing pages.

Then open the matching site URL and verify that the shell, navigation, footer, and first content section match the business.

Step 4: Enable Sellable Or Bookable Inventory

For products:

  1. Open Products.
  2. Add products, variants, pricing, media, inventory, shipping, tax, collections, and SEO.
  3. Verify the public shop, product detail, cart, and checkout pages.

For services:

  1. Open Scheduling.
  2. Add services, tiers, add-ons, waivers, staff, duration, buffer, deposits, and availability.
  3. Verify the public bookings flow from service list through confirmation.

Step 5: Wire Customer Communications

Open Email Notifications and configure the messages customers receive for bookings, orders, forms, tickets, and account events. Use Settings > Domain and Email if the workspace sends from a custom domain.

Do not launch until critical messages have a valid sender and a clear reply path.

Verify at least one message per enabled customer path. For example, a commerce workspace should test order confirmation and refund/cancel messaging; a booking workspace should test booking confirmation, reschedule, cancellation, and payment reminders when enabled. The customer should know what happened, and the operator should know where replies land.

Step 6: Connect Integrations

Configure only the integrations the workspace will actually use:

  • Stripe Connect for payments, invoices, deposits, refunds, and payouts.
  • Google Analytics for public site traffic.
  • Google Ads for conversion tracking.
  • Google Business Profile for reviews and listing data.
  • Calendar integrations for booking sync.
  • Domain and DNS for public routing and branded email.

Step 7: Run The Customer Pass

In the public site, complete the workflows a customer would complete:

  1. Browse the homepage and navigation.
  2. Search or filter products.
  3. Add a product to cart and reach checkout.
  4. Book a service and land on confirmation.
  5. Submit a form.
  6. Read help content and open a ticket.
  7. Sign in to the customer portal.

Done Criteria

The workspace is quickstart-complete when console data and public-site behavior agree: the business identity is correct, payments are connected if needed, content is published, customer communications are enabled, and every critical customer path has been tested.

Capture the quickstart result in a short handoff note: workspace, public URL, enabled features, disabled features, tested customer paths, connected integrations, open risks, and launch owner. This keeps the next operator from re-discovering the same setup state.

Continue With

After the quickstart, move into the guide that matches the remaining risk. Use the workflow map when you are unsure, launch QA when the site is nearly ready, and day-two operations when the team needs a daily rhythm after the first real customer traffic.

Operator Quickstart | Sophosic Platform