Workflow Guides

console.sophosic.ai/workflows

Tasks24

Revenue$8.2k

Review inboxOpen

Publish siteOpen

Workspace consoleWorkspace setup, daily operations, public-site controls, and launch decisions

These guides are written for operators who need to complete real workflows from console setup through public-site verification. Each guide names the console surfaces to configure, the sites surfaces to verify, the expected result, and the failure checks.

Use This Section When

You are onboarding a new workspace.
You are launching or relaunching a customer-facing site.
You need to validate commerce, bookings, forms, portal, integrations, or notifications across the full customer path.
You are debugging a customer-facing issue and need to trace it back to the console source of truth.
You are preparing an operator team for daily use after launch.

Guides

Choose the right guide by operator job, customer action, failure symptom, and source-of-truth surface.

Workflow Map

Select the workspace, configure business settings, team access, legal, features, domain, email, and readiness.

Workspace Onboarding

Build the branded public shell, add pages, configure conversion paths, verify discovery, and publish.

Site Publishing

Connect payments, add products, configure shipping/tax, run checkout, fulfill orders, and verify portal history.

Commerce Workflow

Configure services, staff, availability, payments, calendar sync, public booking, reschedule, and lifecycle actions.

Bookings Workflow

Configure shipping, buy labels, run batches, handle returns, and verify tracking.

Shipping and Fulfillment

Manage customers, inbox, forms, tickets, consent, communications, and account self-service.

Customer Operations

Publish pages, stories, help content, reviews, SEO, GEO, redirects, sitemap, Open Graph, and search surfaces.

Content and Discovery

Configure sender setup, subscribers, segments, campaigns, consent, landing pages, and attribution.

Marketing Campaigns

Configure Stripe, Google Analytics, Google Ads, Google Business Profile, calendars, domains, email, shipping, and webhooks.

Integrations Workflow

Run the final customer-path test matrix before traffic, ads, or production domain cutover.

Launch QA

Daily, weekly, and incident-response operating rhythms after launch.

Day-Two Operations

Source-Of-Truth Model

Business profile

Configure in console: Settings > General

Verify on sites: Homepage, footer, local business metadata, notifications

Domain and email

Configure in console: Settings > Domain and Email

Verify on sites: Final URL, login links, email sender, technical routes

Brand and shell

Configure in console: Settings > Branding, Website

Verify on sites: Header, footer, theme, mobile shell, Open Graph

Products

Configure in console: Products

Verify on sites: Shop, product detail, cart, checkout, saved items

Shipping

Configure in console: Shipping, product shipping settings

Verify on sites: Checkout shipping options, order tracking

Payments

Configure in console: Payments, Checkout and Tax

Verify on sites: Product checkout, booking payment, invoices, refunds

Services

Configure in console: Scheduling, service editor

Verify on sites: Bookings service list, scheduler, confirmation

Customers

Configure in console: Customers, Inbox

Verify on sites: Portal, tickets, orders, bookings, billing

Public content

Configure in console: Website, Stories, Forms, Help, Discovery

Verify on sites: Pages, stories, forms, help center, sitemap, search previews

Integrations

Configure in console: Integrations, Scheduling, Payments, Domain and Email

Verify on sites: Tags, conversion events, reviews, calendar conflicts, emails

Golden Path

Onboard the workspace.
Use the Workflow Map to choose the first customer action to prove.
Publish the public site shell.
Configure the first conversion path: product sale, service booking, form intake, or support request.
Connect only the integrations needed for that path.
Run customer-path QA.
Publish and monitor first real activity.
Move into day-two operating rhythm.

Done Criteria

The docs are sufficient when a new operator can use them to answer:

Where do I configure this?
Where do customers experience it?
What should happen after I save?
What do I test before launch?
What console surface receives the resulting customer action?
What should I check when it fails?