Use the same Specteron workspace for the widget, gateway API, inbox, tickets, knowledge base, and rollout surfaces. Enterprise teams add OIDC SSO, audit visibility, retention, webhooks, and domain policies without inventing a separate product tier.
Three evidence-backed areas from the product today: delivery surfaces, grounded answers, and workspace governance.
Run the web widget, inbox, human handoff, and customer ticket portal inside the same workspace instead of splitting support across disconnected tools.
Use collections, file uploads, URLs, notes, and retrieval settings to keep answers tied to your own content and to expose the same product in docs and studio workflows.
Add OIDC SSO, optional email two-step verification, audit logs, retention, domain rules, PII masking, origin allowlists, and signed production requests without changing the core product.
This is the practical surface area the repo already proves, grouped by how teams usually buy, launch, and operate Specteron.
The same workspace can run the floating or inline widget, the internal inbox view, and the customer-facing ticket flow.
Knowledge lives in workspace collections and can be populated from files, URLs, or notes, then reused in bot and studio workflows.
Enterprise workspace controls live inside the product instead of in a separate ops layer.
Custom systems can connect through the gateway API, workspace API keys, and webhook deliveries with retries and health views.
When the workspace plan allows it, the same bot can be reused in WhatsApp and Messenger with the same runtime and inbox.
Enterprise buyers usually need more than the bot itself, so the product also exposes rollout and trust surfaces publicly.
Showing all 6 review modules.
Start with the web widget, route conversations into the shared inbox, and let agents take over when a workflow needs a human.
Use one gateway for the widget or custom clients, then extend the same bot to WhatsApp and Messenger when the workspace plan allows channel access.
Ground answers with collections, uploaded files, public URLs, and notes. Studio pages expose indexing, collections, jobs, and retrieval settings.
Keep support signal connected to public planning and release communication with roadmap lanes, changelog entries, and a public status surface.
Control spend and downstream delivery with monthly message plans, rate limits, queued webhook deliveries, workspace API keys, and secret rotation.
Enterprise workspaces can add OIDC SSO, audit log visibility, retention, email-domain policies, and optional PII masking without switching products.
A realistic rollout path based on what is already exposed in the product, not on a future-state architecture deck.
Start with the web widget for the fastest rollout, or use the same gateway from your own client if you need a custom front end.
Add collections, upload files, connect URLs, and tune retrieval so responses stay tied to your own product material.
Route conversations into the inbox, enable takeover when needed, and expose ticket flows for issues that must become tracked support threads.
Turn on OIDC SSO, audit and retention controls, domain policies, PII masking, webhooks, and Meta channels as the operation matures.
