Skip to content
NGB.ai
NGB.ai · Next Generation of Business

AI agents that serve customers, grow revenue and support your people.

Put AI to work across customer conversations, revenue workflows and everyday employee tasks. Built on Potential.com's platform, configured around your business and connected to the systems you use.

Built on Potential.com

A customer calls after hours

Illustrative sequence
BeforeCall arrives at 8:42 pm. Office closed.
  1. Customer

    Inbound call, 8:42 pm

    “I need to move my site visit to Saturday morning.”

  2. NGB agent

    Agent answers from approved knowledge

    Confirms the customer, the existing appointment and Saturday availability.

  3. Connected system

    Authorized action completed

    Appointment rescheduled in the connected calendar. Confirmation sent.

  4. Your team · approval point

    Team notified with context

    A summary reaches the right team with the reason for the change.

After

An illustrative sequence, not a recording of a live deployment. See what customer service ai agents can do today.

Three solutions, one platform

Start where the work is slowest.

Each offer has its own buyer, its own workflow and its own measure of success. They run on a shared agent platform, so what you build for one journey is reusable in the next.

Service or contact-centre head

Customer Service AI Agents

Answer questions, manage requests and book appointments across your customer channels.

Give every customer a clear next step.

CMO

Autonomous Revenue Agent

Connect acquisition, qualification and follow-up so more enquiries reach the right sales conversation.

Turn more enquiries into qualified sales conversations.

Function head

Employee Digital Twins

Give each role an assistant that helps people find knowledge, prepare work and complete routine tasks.

A work assistant built around each employee's role.

Published capabilities are listed on each solution page with their availability status — deployed, available to configure, pilot only or planned. We would rather show you the scope than let you assume it.

Where this lands first

Sectors where the first workflow is obvious.

These are starting points drawn from work already being sold, not dedicated sector products. If your industry is not here, the qualifying question is the same: is there volume, an accountable owner and a system that records the outcome?

  • Property and homebuilding

    Answering enquiries and booking site visits, including outside office hours.

  • Appointment-led services

    Booking, rescheduling and confirming appointments, and answering what-do-you-offer questions.

  • Clinics and patient reception

    Reception: finding the right service, booking with the right practitioner, and answering questions about what a treatment involves.

    Reception and booking only. We keep clinical advice and triage firmly out of scope, and we scope these deployments separately.

  • Retail and e-commerce

    Product discovery, order tracking and returns, plus handover to a person for anything unusual.

  • Sales-led B2B

    Qualifying inbound enquiries against your criteria and booking the next sales conversation.

  • Professional services

    Preparing briefs and drafts from approved records so fee earners spend less time assembling context.

  • Recruitment and HR operations

    Structured screening conversations and role questions, with decisions staying with your team.

    Screening support and structured information for human follow-up — never an automated hiring decision. These deployments get tailored human review.

Evidence

A deployed voice receptionist, answering after hours.

A voice receptionist answering inbound enquiries for a homebuilder, capturing contact information and covering contacts that arrived outside office hours.

A meaningful share of answered calls arrived outside Monday-to-Friday office hours — the part of the demand that is hardest to cover with a roster.

Delivered by Potential.comHomebuildingInbound voice

Figures in review

The call volume and after-hours figures from this deployment are held back until their reporting window is published with them. We will share the numbers and their definitions in a demo conversation.

How we handle evidence

  • Every public metric carries its source, reporting window and definition.
  • Work delivered by Potential.com stays attributed to Potential.com.
  • A solution architecture is labelled as a design, not as a result.

How it works

Four steps, one workflow at a time.

You provide the knowledge, the systems and the approval rules. We handle configuration, integration and operation.

  1. 01

    Choose a workflow

    One workflow that matters, with an accountable business owner. Not an AI programme.

  2. 02

    Connect knowledge and systems

    Your approved knowledge, and the CRM, calendar, helpdesk or telephony in scope.

  3. 03

    Set actions and approvals

    What the agent may complete on its own, and exactly where a person steps in.

  4. 04

    Launch and measure

    Baseline first, then measure the business outcome — not the number of conversations.

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.

Demonstrations

See the agents doing the actual work.

Three recordings from the product, one per solution. In each, the agent is given real source material for a synthetic business, then answers or acts on it — so you can judge the output rather than a feature list.

These are recordings of the product against synthetic businesses — no client data, records or systems appear in them. They are walkthroughs, not case-study results. To see an agent run against your own knowledge and systems, ask for a scoped demo.

Control and oversight

Agents do defined work. People keep the judgment.

Every deployment states what the agent may read, what it may do, where it stops and how the result is measured.

Approved data access

Agents work from knowledge you approve and permissions you already operate. We inherit access; we do not widen it.

Authorized actions only

Actions are allowlisted per deployment. Anything outside the list needs a person.

Escalation by design

Uncertainty and restricted actions trigger a handover with full context, not a guess.

Measured outcomes

We report resolution, rework and quality — not just volume and speed.

Start with one workflow that matters.

Tell us where customer requests, sales follow-up or employee work slows down. We will help define the right agent, the systems it needs and how to measure the result.

Looking for workforce, learning or stakeholder programmes instead? Potential.com covers those.