Sophosic Operator Docs
Sophosic is an operating platform for service and commerce businesses. The console is where operators configure the business, manage work, connect integrations, and publish customer experiences. The sites app is the public storefront and customer portal that turns those settings into bookings, orders, help, stories, forms, and account self-service.
These docs now focus on the console and sites apps: operator workflows, public-site behavior, launch steps, commerce, bookings, integrations, and troubleshooting.
How To Read These Docs
Use Get Started when you are learning the platform, Workflow Guides when you need to finish a real customer path, Product Areas when you need a feature map, Integrations when payments or Google tooling is involved, and Troubleshooting when something does not match console state.
Start Here
Pick a workspace, verify the core settings, and open the matching customer site.
Operator QuickstartFollow complete runbooks for setup, publishing, commerce, bookings, integrations, launch QA, and daily operations.
Workflow GuidesPick the right page by operator job, customer action, source-of-truth surface, or failure symptom.
Workflow MapWork through the setup order for business profile, branding, domain, payments, bookings, and email.
Workspace Setup ChecklistUnderstand how console sections map to customer-facing site features.
Product AreasFinal checks before sending traffic to a site.
Launch ChecklistWhat The Platform Covers
Business setup
Console owns: Workspace, team, hours, domains, email, legal, feature flags
Sites owns: Tenant routing, branded shell, public policy pages
Commerce
Console owns: Products, collections, inventory, orders, invoices, payments, shipping
Sites owns: Shop, cart, checkout, saved items, order history, tracking
Bookings
Console owns: Services, tiers, add-ons, waivers, availability, booking lifecycle
Sites owns: Service discovery, scheduler, deposits, confirmations, pay links, reschedules
Customer operations
Console owns: Customers, inbox, forms, consent, communications, automations
Sites owns: Customer portal, tickets, billing, profiles, notification preferences
Growth
Console owns: Stories, discovery, reviews, Google integrations, campaigns
Sites owns: SEO metadata, sitemaps, redirects, Google tags, reviews, public content
Operator Flow
- Choose the workspace in the console.
- Confirm the business profile, hours, team access, and site status.
- Configure branding, navigation, footer links, policies, and domain/email.
- Connect Stripe if the site accepts payments.
- Create products, services, forms, stories, and support content.
- Connect Google Analytics, Google Ads, and Google Business Profile when needed.
- Test the public site as a customer: browse, book, buy, submit, sign in, and request support.
- Launch only after notifications, fulfillment, and payment paths are verified.
Core Destinations
Use core destinations when you know the product area but need the operating model. These pages explain the console source of truth, the customer-facing site behavior, and the checks that prove the two are aligned.
Daily operator workflows across scheduling, sales, customers, inbox, automations, and settings.
Console OperationsProduct sales, service scheduling, deposits, invoices, refunds, and fulfillment.
Commerce and BookingsPublic pages, shop, bookings, help center, account dashboard, orders, billing, and tickets.
Customer Sites and PortalIntegration Guides
Use integration guides whenever a customer path depends on a third party. Payments, Google tools, domains, email, calendar sync, and webhooks all have both setup state and customer-facing effects, so verify the console connection and the public result together.
Connect a workspace to Stripe, verify checkout readiness, and understand payment surfaces.
Stripe ConnectConfigure GA4, Google Ads, Google Business Profile, consent, and conversion tracking.
Google IntegrationsVerify domains, understand cache invalidation webhooks, and route customer traffic safely.
Domains and WebhooksWhere To Go Next
If you are launching a business for the first time, follow Operator Quickstart, then Publish Your First Site. If you are fixing a specific issue, start with the Workflow Map or Troubleshooting Matrix.
When a guide points to a console setting, always verify the matching public site path before considering the work finished. These docs are organized around that loop: configure in console, test on sites, then monitor the resulting customer or operator record.