Product Areas Overview

console.sophosic.ai

Tasks24

Revenue$8.2k

Review inboxOpen

Publish siteOpen

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

Sophosic is organized around business jobs, not isolated tools. The console gives operators one place to configure and run the business; the sites app gives customers one place to take action.

Use this page as the product map. Start with the business job, then open the feature guide for the area that owns the data. If the same customer path crosses several areas, the source-of-truth rule decides where to make the change.

Console Groups

Group

Top

Sections: Get Started, Insights

Primary job: Setup guidance and performance summary

Group

Operate

Sections: Scheduling, Sales, Customers, Inbox, Automations

Primary job: Daily work and customer follow-up

Group

Commerce

Sections: Products, Shipping, Payments

Primary job: Catalog, fulfillment, checkout, payouts

Group

Marketing

Sections: Campaigns, Subscribers, Segments, Sender setup

Primary job: Outbound email and audience management

Group

Site

Sections: Website, Stories, Discovery

Primary job: Public presence, content, SEO, reviews

Group

Configure

Sections: Email Notifications, Forms, Settings, Integrations, AI assistance

Primary job: Workspace configuration and channels

Sites Surfaces

Homepage and pages: Learn about the business and navigate to key actions
Shop: Browse products, filter catalog, save items, add to cart
Checkout: Pay with the configured provider, apply coupons, confirm order
Bookings: Pick service, tier, staff, date, time, add-ons, waiver, and payment path
Help and KB: Read self-service answers and articles
Forms: Submit contact, intake, custom, or support forms
Stories: Read editorial content and share resource pages
Customer portal: Manage orders, bookings, billing, profile, notifications, and tickets

Guides In This Section

Understand the admin navigation and day-to-day operator workflows.

Console Operations

Review trends, revenue, exports, payment methods, comparisons, and operator visibility.

Insights and Revenue

Set up products, orders, shipping, services, availability, and payments.

Commerce and Bookings

Configure rates, labels, batches, returns, tracking, and fulfillment operations.

Shipping and Fulfillment

Build forms, review responses, export submissions, and route customer context.

Forms and Responses

Build public pages, stories, forms, help content, and discovery settings.

Website Content

Manage sender setup, subscribers, segments, campaigns, consent, and attribution.

Marketing Growth

Monitor reviews, reputation signals, Google Business Profile data, and moderation.

Reviews and Reputation

Verify customer-facing shop, booking, help, content, and technical routes.

Customer Sites

Understand authenticated orders, bookings, billing, tickets, profile, and saved-item routes.

Customer Portal

How To Choose Where To Work

If the public page looks wrong, start in Website, Settings > Branding, or Discovery.
If checkout fails, start in Payments, Settings > Checkout and Tax, Products, and Shipping.
If customers cannot book, start in Scheduling, Services, availability, staff, calendar sync, and deposits.
If messages are confusing or missing, start in Email Notifications, Domain and Email, and Inbox.
If traffic tracking is missing, start in Integrations and the public site’s consent banner.

For a symptom-first path, use the Troubleshooting Matrix.

Feature Gating

Some console items remain visible even when a feature is disabled so operators can discover what is available. If a section appears unavailable, check Settings > Features and confirm the workspace has the needed module enabled.

Feature gating should not be treated as an error by itself. A disabled module means the public site should hide or protect the corresponding customer path, while the console may still show setup guidance, preview states, or upgrade prompts. Before debugging a missing shop, booking, form, story, or portal route, confirm whether the workspace is supposed to have that feature enabled.

Use this rule when changing gated features:

Enable a feature

Verify: Console navigation, public route, empty state, launch checklist

Disable a feature

Verify: Public route hidden/protected, navigation removed, existing customer records still accessible where appropriate

Hide a feature temporarily

Verify: Ads, links, sitemap, redirects, and customer emails do not drive traffic to the hidden path

Re-enable after setup

Verify: Source data, permissions, notifications, and rollback owner are still current