AI support agents
One number. A thousand people answering it.
ServeTide gives every support conversation its own AI agent, trained on your sources and held to your rules. When a person should step in, it hands the conversation to your team.
Works with
- Stripe
- Shopify
- Calendly
- Cal.com
- Slack
- MCP
- Answered
- 0
- Waiting
- 0
- With your team
- 0
- Arriving
- Answered
- Handed to a person
- Waiting
01 · The product at work
One refund request, from your customer to your team.
A customer asks on your site while the same conversation runs in ServeTide behind it. The screens are the app's own; the shop is an example.
Now showing · 01 of 05
A customer asks
A refund question arrives in the widget on your site, and appears in Conversations as it happens.
Example workspace: Acme Support. The refund rule and order are example data.
02 · What changes
Support that keeps up with your customers, not the other way round.
Nobody waits in a queue.
Each conversation gets its own agent, so a busy Monday doesn't slow anyone down.
The same answer every time.
Agents answer from your sources, follow your Procedures, and show where an answer came from.
Your team on the cases that need them.
Agents hand off when a person should take over, and anyone on your team can take over a conversation and hand it back.
Changes you can check and undo.
Every configuration change is a version, Tests check answers before you rely on them, and you can roll back.
Trust the wave of agents.Every customer, answered.
03 · How it works
Three steps from your help centre to an agent on your site.
Each step shows up in the conversation. Scroll through them, or pick one.
Where is my order? It was due yesterday.
Shopify order lookupCustomer verified
Order 1042 shipped on Monday and arrives Thursday. You can follow it from the link in your confirmation email.
Source: Shipping and delivery
Can I cancel it instead?
04 · Connections
Start from the knowledge and tools you already have.
Connect the content you already publish and the tools your team already runs. Your agents answer from the first and act through the second.
Your knowledge
- WebsiteCrawled pages
- SitemapEvery listed page
- FilesPDF, Word, text
- TextWritten answers
- Q&AQuestion pairs
Your tools
- StripeSubscriptions, invoices
- ShopifyOrder status
- CalendlyBookings
- Cal.comBookings
- SlackTeam alerts
- Your APICustom HTTP actions
Connect ServeTide to your systems
MCP server · REST API · Webhooks
On the roadmap
Salesforce · Notion · Confluence · Zendesk · HubSpot. Built one at a time, in the order pilots ask for them.
05 · Security and control
Your data stays yours, and your agents stay inside the lines you draw.
Isolated by workspace
Each workspace's data is separated in the database and checked again in the application.
A requestExample Workspace A reads its own rowsAllowedWorkspace A reads Workspace BRefusedA query only sees rows from its own workspace, in the database and again in the application.
Actions limited to what you allow
Agents only use the actions you enable, and custom roles narrow what each teammate can do.
One agent's actionsExample Shopify order lookupOnStripe lookupOffCalendly bookingOffYour own APIOffActions on a customer's own account also need a verified customer.
Every change on the record
Changes to agents, actions, roles and sign ins, and every takeover, go into the audit log.
Audit logExample 09:20action.builtin_enabled10:51ticket.taken_over11:03customrole.updatedFilter by person, agent and date, and export as CSV.
People and access
Roles, two factor authentication, single sign on through OIDC and SCIM provisioning control who can do what.
A person can always step in
Agents hand a conversation to your team when a person should decide, and every takeover goes on the record.
Personal data redaction
On the roadmap, not available yet
Detecting and redacting personal information before it is stored.
06 · How a pilot works
A pilot that proves one workflow before it grows.
There is no long term commitment until the pilot proves out. You decide from the results.
- Workflow
- Order status
- Customers ask
- Where is my order? When will it arrive?
- Answers from
- Shipping and delivery, Returns policy
- Acts through
- Shopify order lookup, for verified customers only
- Hands off when
- A customer wants to cancel or return a shipped order
- A good answer
- States the status and delivery date, and cites its source
Case study[pilot case study, published with the customer's permission]
07 · Questions
What teams ask before a pilot.
Ask a question
Answers come from the questions on this page.
It answers your customers' support requests with AI agents that work from your own content and tools, and hands a conversation to your team when a person should take over.
From the sources you connect: your website, sitemaps, files (PDF, Word, text), and written answers or question pairs. Agents show the source they used.
It hands the conversation to your team. Anyone on the team can take it over and hand it back.
Only the ones you turn on: lookups in Stripe and Shopify, bookings through Calendly and Cal.com, Slack alerts, and calls to your own API. Actions on a customer's own account need a verified customer.
Each workspace is isolated in the database and checked again in the application. Changes and takeovers go into an audit log you can filter and export. Roles, two factor authentication, single sign on through OIDC, and SCIM provisioning control who can do what.
Not yet. Detecting and redacting personal information is on the roadmap.
Models from Anthropic, OpenAI or Google, or any OpenAI compatible endpoint you choose.
ServeTide runs as a hosted service. For a pilot, we agree the setup with you.
We pick one support workflow with you, run it on real conversations, and measure resolution, reopened requests, your team's remaining work and model cost. There is no long term commitment until it proves out.
Prove it on one workflow before you commit to anything.
We pick one support request your team answers often and run it with you on real conversations. There is no long term commitment until it proves out.