AI support agentSupport that does the steps, inside your app.
Many support tickets are someone asking how to do a thing your product already does. An AI support agent in your app can take those: the user asks in their own words, and it does the steps while they watch. Your team keeps everything else.
The tickets your product could answer
Look at a week of support tickets and sort them. Some are bugs. Some are billing. Many are a user asking how to do something: change the time zone, add a teammate, export last month’s data, connect a calendar. The product can already do all of these. The user just couldn’t find the way.
These “how do I” tickets are the ones an AI support agent can take, because the answer is a set of steps in your own product. To see what they cost you today, try the support ticket cost calculator.
Two kinds of AI support agent
An answering agent replies from your help content: it explains the steps or links the right article, and the user follows them. It suits questions, such as “do you support SSO?” or “what does this setting do?”.
A doing agent works inside your app and carries out the steps for the user: it opens the right page, fills in the form and changes the setting while they watch. It suits requests to change something, such as “add Saturdays 10am to 2pm to my hours” or “invite Priya as an admin”.
The two work well together. Many products answer questions from their help content and let an in-app agent do the requests.
How Stiro handles a support request
- Step 1The user asksTyped or spoken, in their own words, from any page
- Step 2Stiro does the stepsIn your real interface, while they watch
- Step 3The user confirmsAnything that sends, spends or deletes is theirs to press
- Step 4Or your team steps inIf it can’t finish, the request goes to you with the reason attached
- One script tag, nothing to train. It reads your live screens, so there are no flows to record and nothing breaks when you ship a redesign.
- An honest stop. If your product can’t do what was asked, or the record doesn’t exist, it says so and changes nothing.
- Your team for the rest. A signed-in user can message your team from the same panel, and your reply shows up there. Stiro reuses those answers the next time someone asks something similar. Already on a help desk? One line hands requests to it instead.
- Their permissions, not more. It only does what the signed-in user could do themselves.
- everyday requests passed, cold, in three apps it had never seen
- 44 of 44
- requests the apps couldn’t do, stopped with a reason and nothing changed
- 7 of 7
- median time from request to reply
- 19.5 s
What to check before you add one
- What can it touch? Only what the signed-in user could reach themselves.
- What does it do when it can’t? Say so and change nothing, not guess.
- How does it hand over? To your team or help desk, with the context, not a dead end.
- How is it priced? Per seat, per conversation or per task looks very different at your volume.
Adding Stiro takes one script tag. See the plans on the pricing page, or watch a real request in Cal.com.
AI support agent questions.
What is an AI support agent?
An AI support agent handles support requests without a person on your team taking each one. Some answer questions from your help content; an in-app AI agent like Stiro goes further and does the steps in your product for the user, while they watch.
Can an AI support agent reduce support tickets?
It can take the “how do I” requests: changing a setting, inviting someone, finding an export. Those are the tickets where the answer is a set of steps in your product. Bugs, billing exceptions and judgement calls still belong with your team.
What is the difference between answering and doing?
An answering agent replies with the steps or a help article, and the user follows them. A doing agent carries out the steps in your app for the user. Both have a place: answers suit questions, doing suits requests to change something.
What happens when the AI can’t help?
With Stiro, it stops and says why. The user can then message your team from the same panel, with the request and the reason already attached, or it hands the request to your existing help desk. Your team’s reply shows up in the user’s panel.
Is it safe to let an AI act in our product?
Stiro only acts on what the user asked, with the permissions they already have in your app. It hands anything that sends, spends or deletes back to them to confirm, and values of password, card and ID fields it recognises never leave the browser. Keep your app’s own confirmations in place too.
How much does an AI support agent cost?
Pricing varies by product: per seat, per conversation or per resolution. Stiro charges per task done: the free plan includes 50 runs a month, Starter is $149 a month for 2,000 tasks and Growth $599 for 10,000. A run that fails on our side is free.
Let your users just ask.
Stiro does the steps in your app for your users. One script tag, 50 runs a month free, no card.