Solutions · Customer Support

Support that answers from your own documentation.

Build a support agent in a dashboard, ground it in your help centre and FAQs, connect your order and account systems over MCP, and embed it on your site. It clears the repetitive questions around the clock, and hands the rest to your team with the whole thread attached.

14 days free · No credit card · Bring your own model keys

support-agent
My promo code won't apply at checkout
SPRING20 only applies to full-price items, and two things in your basket are already reduced. The markdown saves you more — want me to keep it?
Answered from your live systems, and traced end to end.

Where the time goes

Ticket volume grows. Your team doesn't.

Most support hours go to questions your documentation already answers — which leaves less room for the conversations that genuinely need a person.

01

The same questions, daily

A short list of questions makes up most of your queue. Your team answers them again every morning instead of solving the hard tickets.

02

Answers that drift

Two agents, two versions of the same policy. Every price or process change quietly widens the gap.

03

Waiting for what's published

Customers queue for an answer that is already written in your help centre — and patience runs out before the reply lands.

04

Knowledge in four places

Help centre, FAQs, a spreadsheet, someone's Slack thread. Even good agents have to go hunting first.

What it does

Answers you can put your name to. At any hour.

A support agent on SentientOne takes the repetitive work accurately, and makes your team quicker on everything it hands over.

Answers at 2am

Resolves common questions the moment they are asked, in every timezone, with no queue and no rota to staff.

Grounded in your docs

Retrieval runs on every message against your help centre, FAQs and uploaded files. When the answer is not there, it says so instead of inventing a policy.

Reads the real record

Connect order, account and CRM systems over MCP so it answers about this customer's subscription, not the general rule.

Escalates with the context

Hands the hard tickets to a person with a summary, the right tags and the whole thread attached — nobody starts from scratch.

Shorter handle time

Drafts a grounded reply and surfaces the right macro, so the tickets that need a human move faster too.

Every market, one agent

Replies in the customer's own language from the same knowledge base. No second agent, no translated copy to maintain.

How it works

Live in four steps. No SDK to install.

From an empty dashboard to a traced conversation on your own site.

01

Create the agent

Name it, write a system prompt that sets tone and scope, and pick a model — GPT-4o, Claude or Gemini. Five fields, no code.

02

Ground it in your knowledge

Upload help docs and FAQs, or point it at your help centre URL to crawl. Re-crawl whenever the docs change and the agent updates with them.

03

Connect tools, set the guardrails

Register your order, account or CRM systems as MCP servers for live lookups. Decide when it must hand off — unsure, angry, or asked for a person.

04

Put it in front of customers

One script tag for the widget, or one POST from your app. Every conversation comes back as a trace with tokens, latency and cost.

Drop it on your site
<script
  src="https://app.sentientone.ai/widget.js"
  data-agent-id="support-agent"
  data-style="bubble">
</script>
Or call it from your app
curl https://api.sentientone.ai/v1/chat/stream \
  -H "Authorization: Bearer $SENTIENTONE_KEY" \
  -d '{
    "agent": "support-agent",
    "message": "Where is my order #10294?"
  }'

Same agent behind both. Change the model or the prompt in the dashboard and neither snippet changes.

Connections

Plugged into your support stack. Not replacing it.

Bring the knowledge you have already written, connect the systems that hold the truth, and deploy where your customers already ask.

Knowledge sources

  • Help centre & docs
  • FAQs
  • Website crawl
  • PDFs & files

Connect via MCP

  • Order & fulfilment systems
  • CRM & account data
  • Subscription & billing
  • Your internal APIs

Deploy to

  • Website chat widget
  • In-app via REST API
  • Private team workspace
  • Any channel, one API

Questions

Before you build it.

Something here still unanswered? Ask us directly — a person answers.

How do you stop it inventing answers?

It answers from the knowledge you give it — your help docs, FAQs and crawled help centre — and retrieval runs on every message. When the answer is not in your material it says it does not know and escalates, rather than filling the gap with a plausible policy.

Can it hand off to a human?

Yes, and you write the rules. When a ticket is complex, the customer asks for a person, or the agent is unsure, it passes the conversation to your team with a summary and the full thread attached.

What can it connect to?

Your help centre and FAQs for knowledge, and your order, account or CRM systems over MCP for live lookups — so it can answer about a specific order instead of quoting the returns policy.

How long does setup take?

Most teams have a working agent in an afternoon: create it in the dashboard, point it at your docs, connect any tools, then embed the widget with one script tag.

Which languages does it support?

It replies in each customer's own language from the same knowledge base, with no separate agent or setup per market.

Can we run it in our own infrastructure?

Yes. Run SentientOne single-tenant in your own AWS, Azure, GCP or on-prem environment, with your own model keys, when privacy or data residency requires it.

Your support agent is an afternoon away.

Point it at your help centre on the free trial, then ask it the question your team answered five times today.

14 days free · No credit card · Cancel anytime