Grounded in your docs
Add FAQs, policies and product docs. It answers from them, shows where the answer came from, and says so when it isn’t sure.
Your $200 agent, running a $200B company’s support.
Give your AI agent the whole desk: it answers customers from your docs, takes HR questions and account set-ups off your plate through your own tools — honestly, whatever you want — and brings in a person when it matters.
Already approved?Sign in to your portal and build your assistant.// live demo
Customers, employees, new hires: ask as them on the left, and watch what your agent does — and what lands with your team — on the right.
01 Your visitor · acme-outdoor.com
02 Your team · staff console
Chats
Tickets
A scripted demo. The real assistant answers from your own documents, calls your own tools, and your team replies from the console.
// make it yours
Everything here is set in your portal. The snippet on your site never changes.
Hi! Ask me about orders, returns or your account.
<script src="https://sharepanel.host/ticket/assistant.js"
data-key="pk_your_assistant_key" async></script>
// what it does
Add FAQs, policies and product docs. It answers from them, shows where the answer came from, and says so when it isn’t sure.
“Talk to a person” hands the chat to your team at once, with alerts on desktop and phone — even with the console closed.
One tap opens a ticket with the chat attached. Your team answers and updates it from the console.
Support staff sign in with your company’s SSO or a signed link. No new passwords.
HR questions, account set-ups, order lookups: connect your own API as tools and your agent does the work — signed requests, verified people only.
Only your sites can load it. Your chats and tickets are never shared. Budgets, rate limits and an activity log built in.
Drop one file in front of your site and it stops SQL injection, XSS, scanners and floods. Attack bursts and “blocked by mistake” reports land in your queue as tickets.
Point Claude Code or any MCP client at it: it sets up assistants, connects your APIs, answers chats and reads the analytics for you.
// how it works
Tell us about your team. A person reviews every request, and we email you when your portal is ready.
Pick a model, write its persona, add your documents and tools, and try it in the live preview.
Add the script tag and go live. Hand-offs and tickets land in your team’s staff console.
// what it costs to run
On our keys, each assistant gets a monthly allowance ($10 by default) on the listed models. Bring your own API key for any model, with no cap.
Assumes about 3,000 tokens in (your persona, the documents it found and the chat so far) and 300 out per answer. Real use varies.
Model usage
$1.26/ month
Fits in the default allowance.
// questions
Models from OpenRouter, Google and Anthropic. Use our keys within your plan’s monthly allowance per assistant, or add your own API key and there’s no cap.
To your staff console’s Tickets tab, where your team posts updates and changes their status. Only your organization sees them.
No. Owners and admins manage everything in your portal; support staff sign in to the console with your company’s login.
Only what you give it: your documents and the tools you connect. Visitors your site signs in are verified by your server, and their data stays with your organization.
No. Point it at whoever needs answers: customers, employees, new hires. Give it your handbook and policies as documents, and your own API as tools — leave requests, account set-ups, order lookups — and it handles the busywork.
Request access. Once we’ve approved your team, you can create your first assistant in a few minutes.