Skip to content
NGB.ai

Platform

One agent platform. Three commercial journeys.

All three NGB solutions run on the same engine: knowledge, orchestration, tools and actions, integrations, analytics, governance and human handoff. What you configure for one workflow is reusable in the next.

Architecture

Channels → solution → agent OS → your systems → measured outcome.

Read top to bottom. A request enters on a channel, runs through a packaged solution on the shared engine, acts in your systems, and lands as a recorded outcome.

Three journeys, one engine

Architecture
Customer request
Revenue enquiry
Employee task

Shared Agent OS

KnowledgeOrchestrationTools and actionsGovernance

Built on Potential.com

CRM
Calendar
Helpdesk
Documents
Recorded outcome

Connector support is confirmed per system during scoping. The systems shown are examples, not a claim that every connector is productized for every deployment.

  1. Layer 1

    Channels and interfaces

    Phone, web chat, WhatsApp, landing pages and internal workspaces. Each channel is enabled per deployment.

    Voice / telephonyWeb chatWhatsAppWeb formsInternal workspace
  2. Layer 2

    NGB solution experience

    The packaged workflow a buyer actually purchases: service, revenue or a role-based work assistant.

    Service agentsRevenue agentEmployee digital twins
  3. Layer 3

    Shared Agent OS

    The common engine behind all three offers, operated by the Potential.com platform team.

    Knowledge, profile and memoryWorkflow orchestrationTools and actionsIntegrationsAnalyticsGovernance and human handoff
  4. Layer 4

    Enterprise systems

    Your installed environment. Connector support is verified per system before it is published.

    CRMCalendarHelpdeskTelephonyWebsite and ad platformsDocument storesHR and learning systems
  5. Layer 5

    Measured outcome

    The recorded business result: a resolved request, a qualified opportunity, a completed task.

    Outcome recordsFunnel reportingQuality review

This diagram shows the structure of the platform. It does not imply that every connector in every layer is productized for every deployment — connector support is confirmed per system before we publish or promise it.

Integrations

Connected to the systems you already run.

We distinguish native, configured and custom integration, because the difference changes your timeline and your cost.

Integration register with support level
SystemWhat the agent does with itSupport
CRMCreate and update lead, contact and opportunity recordsConfigured
CalendarCheck availability and book, reschedule or cancel appointmentsConfigured
Helpdesk / ticketingCreate, classify and route service requestsConfigured
TelephonyAnswer inbound calls and hand over to a person with contextConfigured
Website and web chatCapture enquiries and answer from approved knowledgeNative
WhatsApp and messagingConversational qualification and follow-upConfigured
Ad platformsCampaign attribution back to qualified outcomesConfigured
Document storesSource-grounded retrieval within existing permissionsConfigured
HR and learning systemsRole context and programme workflowsCustom build

Named vendor connectors are confirmed during scoping for your specific environment and version. Ask us to state the support level for your stack in writing.

Product architecture

Seven internal capability families, three things you buy.

The platform is built from reusable agent families. We sell three journeys, so you are buying an outcome rather than a catalogue.

  • Revenue Agent SuiteAutonomous Revenue Agent
  • Service and Contact Center AgentsCustomer Service AI Agents
  • Screening, Qualification and MatchingReusable capability across revenue, recruitment and selected service journeys
  • Role-Based Work Assistants and Digital TwinsEmployee Digital Twins
  • Coach and Learning CompanionEmployee adoption, and Potential.com learning use cases
  • Program Operations AgentShared execution capability for Potential.com programs and scoped NGB operations
  • Outcome Intelligence AgentMeasurement across all three NGB offers

Emerging capability

Beyond the three launch solutions.

The same engine supports work we have not packaged as a launch offer yet. We show it here so you can see where the platform is going — not as something you can buy today off a price list.

Conversational commerce avatar

A voice-and-video avatar that answers product questions and builds a basket in conversation. It runs on the same knowledge, actions and governance layers as the three solutions.

How to read this

Pilot only. Deployment scope, supported languages, commerce connectors and the approval model are scoped per engagement. If this is what you need, say so early and we will tell you honestly what it takes.

Commerce avatar: shopping by conversation

Product walkthroughSynthetic data

A voice avatar takes a shopper's spoken requests, answers product questions and adds items to the cart, with the assistant's own accuracy warning visible in the interface.

1 minute 47 seconds · captions are burned into the recording · the business, contacts and records shown are synthetic

Pilot onlyNot one of the three launch solutions.

Deployment

Who runs what.

This website

Brand, content, evidence, analytics events and the booking interface. No privileged tokens in the browser.

Website server layer

Validated forms, CRM relay, signed booking callbacks and short-lived demo sessions. Secrets stay here.

Shared platform

Agent execution, knowledge retrieval, workflow logic, approved tool actions, tenant controls and outcome records.

Your systems

CRM, calendar, helpdesk, messaging, telephony and model providers, as selected during scoping.

Public content delivery and agent data processing are hosted separately, so region choices for your data are not dictated by where this website is served. Actual data flows are confirmed in writing during scoping.