A help center that answers,
instead of just listing articles
A self-service portal that only links to articles still leaves the customer to do the work of translating an article into an actual account change. This agent reads the question, finds the real answer, and when the action is something it is allowed to do directly, like updating an address or downloading an invoice, it just does it.
The role today
Most self-service portals are really just searchable documentation with an account dashboard bolted on next to it, which means a customer trying to update a billing address still has to find the right article, then separately find the right settings page, then do it themselves. The portal technically contains everything needed to resolve the question, but resolving it is still work the customer has to assemble on their own.
What the agent takes over
The agent sits inside your existing portal and answers questions directly from your documentation, citing the source, but where the question is actually a request to do something, update an address, download an invoice, check a plan’s details, change a notification setting, it performs the action directly within a pre-approved list rather than just pointing to where the setting lives. This turns the portal from a reference library into something that actually finishes the task.
For anything outside that approved list, it hands off cleanly to live support with the context of what the customer was trying to do, so the conversation does not restart from zero. It also tracks what customers actually try to do in the portal, which is often different from what the portal was designed assuming they would do, giving your team real usage data to improve both the portal and the agent’s approved action list over time.
Usage data distinguishes between a customer who found the answer and left satisfied and one who gave up and opened a ticket anyway, a far more useful signal than raw portal traffic for deciding what to automate next. For businesses with tiered account types, the approved action list can differ by tier, since a basic account’s address change and an enterprise account’s address change might carry different approval requirements even though the action looks identical on the surface.
What stays with humans
Any account action outside the pre-approved list, and any request involving a dispute or exception, goes to live support. Your team decides which actions are safe enough to let the agent perform directly, and reviews usage data to expand or restrict that list. Your team reviews which actions customers attempt most often but are not yet on the approved list, which becomes a practical roadmap for where to expand self-service next rather than a guess.
Guards
The agent can only perform actions on a pre-approved list your team defines; nothing outside that list is attempted, regardless of how the request is phrased. Every action taken is logged with a before-and-after record of the account state. The approved action list is tested in a sandbox against real account scenarios before going live, and any action can be reversed by a person. The embedded agent respects your portal’s existing permission structure exactly, so a customer only ever sees and acts on their own account data through the same authentication the portal already enforces, with no new access path introduced alongside it that your security team would need to separately review.
Price and timeline
| Option | Price | Timeline |
|---|---|---|
| Agency runs it | from $3,400 + support plan | 4 to 6 weeks |
| Full control, handover-ready | from $5,800 | 6 to 9 weeks |
“Agency runs it” keeps the agent on our infrastructure with a monthly support plan covering tuning and monitoring. “Full control, handover-ready” delivers the agent on your own servers and accounts with documentation, source and credentials, so your team can run and change it without us; it costs more up front because the handover package, your-infra deployment and internal documentation are built in from day one.
Related
See the AI agents overview for how we build and guard these systems, and Development for the services that often pair with this one. Inside the agents catalogue: FAQ and knowledge base agent, Subscription management agent, Technical support tier-1 agent. For a narrower, single-process version of this work, see Internal knowledge base Q&A, RAG knowledge base with citations in the automations catalogue. For how the same guard patterns held up on real systems: ProBay marketplace AI agent team.
Want this running for your team? Get in touch and tell us where the messages pile up.
FAQ
How much does a self-service portal agent cost?
From $3,400 to embed the agent in your existing portal and connect it to the account actions you want it to perform directly, live in 4 to 6 weeks.
How long before it is live?
4 to 6 weeks, with real time spent deciding exactly which account actions are safe to automate versus should stay a request to support.
Which channels and tools does it work with?
Your existing customer portal or account dashboard, embedded as a widget; it connects to your CRM, billing platform or account database for the actions it is allowed to take.
What if the agent takes an action it should not have?
Every direct action is scoped to a pre-approved list your team defines, address changes, invoice downloads, plan detail views, nothing beyond that list is ever attempted automatically, and every action taken is logged with a before-and-after record.
Is account data safe inside the portal?
The agent operates inside your existing portal's authentication, so it only ever acts on the account the logged-in customer already has access to; no new access layer is introduced, and every action is logged.