AI for Customer Success

AI customer service, built inside
the CRM you already run

The fear is not that AI answers slowly. It is that it answers wrongly, to a customer, in writing. So we start by deciding what it is allowed to say.

OpenAI Select Partner
Abbott Laboratories logoCIPD logoLivaNova logoHealix LogoGunnebo LogoUniversity of West LondonCloserStill Media LogoMention Me logoFeefo logoEcommpay LogoSuperior Press logoThought Leaders 4WayPoint PartnersTussell LogoUnily LogoUtilize LogoArdmacCauseway logoSadel GroupTrue Student LivingStudent FM logoLeaders Romans GroupSpriftIncome AnalyticsConnect Vending LogoRoar B2BSIGOS logoTentbox logoZeroAviaproAlpha logoIcon Solutions logoVantagePoint Consulting logoConway ConsultingPetExec LogoBuyaPowa LogoVableStakeholderzAbbott Laboratories logoCIPD logoLivaNova logoHealix LogoGunnebo LogoUniversity of West LondonCloserStill Media LogoMention Me logoFeefo logoEcommpay LogoSuperior Press logoThought Leaders 4WayPoint PartnersTussell LogoUnily LogoUtilize LogoArdmacCauseway logoSadel GroupTrue Student LivingStudent FM logoLeaders Romans GroupSpriftIncome AnalyticsConnect Vending LogoRoar B2BSIGOS logoTentbox logoZeroAviaproAlpha logoIcon Solutions logoVantagePoint Consulting logoConway ConsultingPetExec LogoBuyaPowa LogoVableStakeholderz

What we usually find, and what we build instead

Four things we find in almost every service team that has tried a bolt-on chatbot.

Without SpotDev

What we usually find

With SpotDev

What we build instead

The same twenty questions, every week

Skilled people answering what a published article already answers, while real problems queue behind them.

Published answers handled

Routine questions resolved or drafted, so complex work reaches a person sooner.

The answer is in a system the chat widget cannot see

Order status, contract terms and delivery dates sit in the ERP. The bot sees the help centre.

Retrieval from the real source

Answers grounded in the systems that actually hold the fact, not just the knowledge base.

You find out about churn at renewal

The signals were there for months, spread across tickets, usage and unanswered emails.

Risk surfaced with its evidence

Conditions detected against CRM evidence, with the reasoning shown so a human can judge it.

Nobody can say what the AI may say to a customer

So it is either switched off, or switched on and quietly frightening.

A written action list per workflow

Granted one action at a time, with everything sensitive escalated from day one.

Without SpotDev

The same twenty questions, every week

Skilled people answering what a published article already answers, while real problems queue behind them.

With SpotDev

Published answers handled

Routine questions resolved or drafted, so complex work reaches a person sooner.

Without SpotDev

The answer is in a system the chat widget cannot see

Order status, contract terms and delivery dates sit in the ERP. The bot sees the help centre.

With SpotDev

Retrieval from the real source

Answers grounded in the systems that actually hold the fact, not just the knowledge base.

Without SpotDev

You find out about churn at renewal

The signals were there for months, spread across tickets, usage and unanswered emails.

With SpotDev

Risk surfaced with its evidence

Conditions detected against CRM evidence, with the reasoning shown so a human can judge it.

Without SpotDev

Nobody can say what the AI may say to a customer

So it is either switched off, or switched on and quietly frightening.

With SpotDev

A written action list per workflow

Granted one action at a time, with everything sensitive escalated from day one.

Swipe to explore

What a customer success wave activates

A wave activates two of the four agent capabilities, chosen against your own value case. Enablement and measurement are part of every wave, not alternatives to them.

Service response

Retrieves approved knowledge and account context, then answers, requests what is missing, or routes to the right person.

Account review preparation

Assembles outcomes, risks, open requests and commitments before the review, so the meeting starts with the facts already gathered.

Retention risk detection

Detects inactivity, unresolved service and adoption decline, explains the evidence, and recommends an intervention for a person to take.

Account growth signals

Connects a request or a changed condition to a credible expansion hypothesis, and prepares the internal briefing behind it.

Enablement for the service team

The people answering customers trained on when to trust a draft, when to correct it, and how to report one that was wrong.

Measurement against a baseline

Response time, resolution time, escalation and correction rate, tracked against the position we recorded before anything was built.

Where HubSpot stops and engineering starts

Scroll for all four
1

It answers from content, not systems

HubSpot's own customer agent answers from your published content. It does not know an order status held in your ERP.

2

Non-article sources go stale

Content pulled from outside the knowledge base re-syncs on a schedule, so pricing and lead times can lag reality.

3

The approval model is the platform's

You get the shape of approvals the product ships with, rather than the one your escalation policy actually needs.

4

Three of four jobs are not deflection

Review preparation, retention and growth are not ticket deflection, and no ticket-deflection tool is built for them.

What it is allowed to say

Authority is granted per action, not per agent. Check what your own subscription covers, then decide each of these deliberately.

Always escalated

Refunds, complaints, legal matters, account closure and anything about a vulnerable customer.

External send is separate

Permission to draft is not permission to send. The two are never granted together by default.

Confidence is not a control

A model's confidence score is not evidence. We gate on source and action type instead.

Fails safely

When identity, entitlement or the source is uncertain, it stops and hands over rather than guessing.

Often permanent draft

For many customer-facing workflows, drafting for a human is the right end state, not a phase.

Everything is logged

Every answer, escalation and correction recorded, so a complaint can be reconstructed from evidence.

300+HubSpot implementations, firm-wide

Implementation expertise that drives adoption

An in-house engineering team that has delivered more than 300 technology projects. Work with engineers who have built this before.

In-house engineering team.

Agents and integrations designed, tested and shipped by our own engineers. Nothing is subcontracted.

OpenAI Select Partner

SpotDev is enrolled in the OpenAI Partner Network at Select tier, alongside HubSpot Diamond status and Custom Integration and Onboarding accreditations.

Model chosen for the job.

Honest evaluation of the right model for the work. We hold OpenAI Select Partner status and deep expertise in Anthropic's Claude, and we will say when the answer is the AI you already pay for.

AI with security in mind

Not trained on by default
Cyber Essentials Plus
Built on your infrastructure
In-house engineers

Common questions

Start with a diagnostic.

A short, fixed-scope assessment of which service workflows are safe to automate, which are not, and what your content and data can currently support. No obligation.

SpotDev is an OpenAI Select Partner and a HubSpot Diamond Solutions Partner. SpotDev is a separate company from OpenAI, and partner status does not constitute endorsement of SpotDev by OpenAI. OpenAI and ChatGPT are trademarks of OpenAI. HubSpot is a trademark of HubSpot, Inc. Claude is a trademark of Anthropic, PBC.