Vertical package

Education And Training Ops

Enrollment and learner-success teams that need nurture, support, and progress reporting without manual overload.

Education And Training

Multi-step learner journeys with intake, reminder, support, and reporting checkpoints.

From GBP 4,800/mo5 linked services

Core outcomes

3

Commercial and operational outcomes already mapped to the bundle.

Workflow templates

4

Workflow blueprints that operationalize the bundle once dependencies are ready.

Connector lanes

10

Provider and connector categories that need to be available for the bundle.

Tracked KPIs

4

Operational or commercial scorecards the bundle is already designed to surface.

Operating model

The service families and workflows inside this bundle

Vertical packages turn the public service families into one more opinionated rollout path, with onboarding, dashboards, and KPI expectations already aligned.

Blueprint map

What the bundle maps to inside NEXA OS

The same package record now maps to workflow templates, agent packs, onboarding modules, dashboard modules, and reporting without splitting public and operational definitions.

Workflows

Automation templates

Lead Intake Router

Normalizes inbound requests and pushes them into the right queue or owner.

Enrollment Nurture

Keeps enrollment and learner onboarding moving through reminders and routing.

Support Triage

Classifies support requests and routes them into the right escalation path.

Reporting Digest

Builds recurring service scorecards for operators and stakeholders.

Agent packs

AI workforce coverage

Lead Intake Pack

Agents that qualify, route, and summarize inbound demand.

Support Desk Pack

Support agents for triage, response drafting, and escalation prep.

Knowledge Curation Pack

Agents that organize, refresh, and validate grounded source material.

Reporting Analyst Pack

Agents that summarize KPIs, trends, and rollout posture for humans.

Onboarding

Launch checklist

Workspace Baseline

Define owners, source systems, and the first service boundaries.

Connector Readiness

Confirm every required connector before workflows are activated.

Knowledge Import

Load and validate source material for grounded automation.

Reporting Goals

Align on the KPIs and digest cadence that make the rollout believable.

Dashboard and reporting

Where teams track the rollout

Lead Intake

Queues, qualification posture, and handoff readiness.

Conversation Coverage

Channel visibility for chat, messaging, and support interactions.

Knowledge Readiness

Source health, refresh cadence, and grounding posture.

Analytics Scorecards

Service and package KPI scorecards tied to real workflows.

Executive Summary

High-level program summary for operators and customer stakeholders.

Support Quality

Highlights queue health, answer quality, and escalation pressure.

Knowledge Coverage

Shows whether grounded source material matches what the system is asked.

Readiness and compliance

Dependencies that keep the bundle trustworthy

These bundles deliberately call out operational dependencies and compliance considerations so public storytelling does not pretend the rollout is push-button.

Deployment dependencies

Enrollment stages mapped

Learner FAQ and policy sources uploaded

Escalation rules defined for at-risk learners

Provider mapping

Apideck CRM

This bundle already maps to the shared workspace connection seam for Apideck CRM.

Google Calendar

This bundle already maps to the shared workspace connection seam for Google Calendar.

Twilio

This bundle already maps to the shared workspace connection seam for Twilio.

Google Analytics 4

This bundle already maps to the shared workspace connection seam for Google Analytics 4.

n8n

This bundle already maps to the shared workspace connection seam for n8n.

OpenAI

This bundle already maps to the shared workspace connection seam for OpenAI.

Compliance watchpoints

Protect learner records in support and reporting workflows

Review consent and notification rules for reminders and nudges

Connector requirements

CRM sync

Lead, customer, and pipeline state mapped into the right record system.

Calendar

Scheduling availability, reminders, and appointment routing.

Messaging transport

SMS or WhatsApp delivery, consent handling, and follow-up coverage.

Knowledge base

Approved source material for grounded answers and support context.

Analytics

Conversion and operational reporting inputs for believable scorecards.

Workflow engine

Durable automation orchestration, approvals, and operational handoffs.

Voice transport

Phone routing, missed-call recovery, and transcript capture.

Ticketing

Support queue intake, triage, and escalation ownership.

OpenAI runtime

LLM and retrieval runtime for grounded assistants and agent logic.

Document store

Policies, files, and retention-sensitive source documents.

Expansion path

The next lanes this bundle usually unlocks

Vertical packages can start with a narrow industry problem, then expand into adjacent service families once the core lane is stable.

Trust posture

Why the bundle page does not over-claim delivery maturity

The public bundle story is intentionally tied back to the same shared records that power dashboards, forms, onboarding, and later activation work.

Catalog-driven

Shared catalog, not page-local copy

Services, bundles, pricing posture, workflow links, and form deep links resolve from the same typed service catalog.

Production path

Lead capture stays durable-first

Contact and audit requests still flow through one shared capture service with hashing, rate limits, and downstream dispatch tracking.

Truthful boundary

Delivery state stays honest

Public pages describe scope and rollout inputs, while real workspace activation and readiness remain in dashboard and admin service ledgers.