Connector lanes
4
Required provider or connector categories that have to be ready before the lane is fully live.
Workflow templates
2
Workflow blueprints already mapped to this family in the shared service catalog.
Recommended bundles
7
Reusable launch bundles and vertical packages already linked to this service family.
Managed entry points
2
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
Lead Intake Router
Normalizes inbound requests and pushes them into the right queue or owner.
Qualification Follow-Up
Scores fit, asks the next question, and keeps follow-up moving.
Agent packs
AI workforce coverage
Lead Intake Pack
Agents that qualify, route, and summarize inbound demand.
Onboarding
What must be ready before launch
Workspace Baseline
Define owners, source systems, and the first service boundaries.
Connector Readiness
Confirm every required connector before workflows are activated.
Handoff Rules
Clarify who owns each stage when automation stops and humans take over.
Dashboard modules
Where the work becomes visible
Lead Intake
Queues, qualification posture, and handoff readiness.
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.
CRM sync
Lead, customer, and pipeline state mapped into the right record system.
Workflow engine
Durable automation orchestration, approvals, and operational handoffs.
Messaging transport
SMS or WhatsApp delivery, consent handling, and follow-up coverage.
Voice transport
Phone routing, missed-call recovery, and transcript capture.
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.
Flagship managed program
AI Operations & Automation
Replace manual friction with a managed operations program that hardens intake, automation coverage, and change visibility.
Flagship managed program
Advanced Google Ads
Run a cleaner Google Ads program with tighter measurement, better lead handling, and a more credible loop between spend and outcomes.
Launch bundle
Lead Intake Foundation
Inbound capture, qualification, routing, and first-response coverage bundled into one reusable launch-ready intake lane.
Launch bundle
Google Ads Control Tower
Paid-acquisition operations bundle for cleaner campaign signals, faster follow-up, booking flow discipline, and anomaly visibility.
Vertical package
Logistics Control Tower
High-velocity inbound demand, route changes, and status updates that need durable handoffs.
Vertical package
Construction And Field Service Ops
Quote requests, missed calls, and appointment logistics spread across office and field teams.
Vertical package
Recruitment And Staffing Desk
Two-sided workflows across candidate nurture, role intake, and client-facing status updates.
Vertical package
Education And Training Ops
Multi-step learner journeys with intake, reminder, support, and reporting checkpoints.
Vertical package
Property And Estate Workflow
Lead-heavy workflow with viewing schedules, document requests, and communication across multiple agents.
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.