Connector lanes
3
Required provider or connector categories that have to be ready before the lane is fully live.
Workflow templates
1
Workflow blueprints already mapped to this family in the shared service catalog.
Recommended bundles
6
Reusable launch bundles and vertical packages already linked to this service family.
Managed entry points
1
Flagship managed programs that can deliver this family as part of a broader commercial engagement.
Blueprint map
How this family turns into a real rollout
The shared catalog now maps each public service family to workflows, agent packs, onboarding steps, reporting, and dashboard modules without inventing a separate marketing model.
Workflow templates
Automation blueprints
Knowledge Refresh
Keeps source material current so AI assistants stay grounded.
Agent packs
AI workforce coverage
Knowledge Curation Pack
Agents that organize, refresh, and validate grounded source material.
Onboarding
What must be ready before launch
Knowledge Import
Load and validate source material for grounded automation.
Workflow Approvals
Review risky automations and sign off on change-control rules.
Dashboard modules
Where the work becomes visible
Knowledge Readiness
Source health, refresh cadence, and grounding posture.
Conversation Coverage
Channel visibility for chat, messaging, and support interactions.
Provider readiness
Connectors and reporting that support the service family
These are the connector categories, reporting lanes, and supporting routes already mapped to this family in the shared service catalog.
OpenAI runtime
LLM and retrieval runtime for grounded assistants and agent logic.
Knowledge base
Approved source material for grounded answers and support context.
Document store
Policies, files, and retention-sensitive source documents.
Supporting routes
Commercial fit
Managed programs and reusable packages already linked to this family
Each service family can sit inside a flagship managed program, a reusable launch bundle, or a more opinionated vertical package depending on how much of the operating model you need NEXA to own.
Launch bundle
Marketing Visibility Foundation
Answer-engine visibility, grounded website coverage, and reporting bundled into one reusable demand-generation foundation.
Launch bundle
Support Inbox Intelligence
Grounded support triage, queue clarity, escalation prep, and response reporting bundled into one reusable support lane.
Launch bundle
Knowledge Assistant Foundation
Reusable grounded assistant bundle for source ingestion, refresh cadence, website answers, and operator-visible knowledge health.
Vertical package
Healthcare Admin Coordination
Admin-heavy coordination where consent, routing, and queue ownership matter as much as response speed.
Vertical package
Professional Services Pipeline
Longer deal cycles with high-value leads, human review steps, and service-delivery handoffs.
Vertical package
Education And Training Ops
Multi-step learner journeys with intake, reminder, support, and reporting checkpoints.
Trust posture
Why this public page stays believable
The catalog can expand the public story before every live execution seam is finished, but the repo still keeps the truth boundary explicit.
Shared catalog, not page-local copy
Services, bundles, pricing posture, workflow links, and form deep links resolve from the same typed service catalog.
Lead capture stays durable-first
Contact and audit requests still flow through one shared capture service with hashing, rate limits, and downstream dispatch tracking.
Delivery state stays honest
Public pages describe scope and rollout inputs, while real workspace activation and readiness remain in dashboard and admin service ledgers.