One Inbox
Your team works chat, email, forms, and webhooks from one filtered list. You can turn the agent off and keep using the inbox.
AI Automation for Your Business and App
Most AI tools can only talk. AssistJet looks up the order, chases the invoice, follows up the lead, and runs the refund you approved, because it works through the tools your app already exposes. Every run is stored in your app's database, and your team can take over at any moment.
My order never arrived. Can you help?
orders_getOrder 8142, shipped October 28
carrier_trackMarked lost in transit
I found order 8142, and the carrier lost it. I can send a replacement today.
Yes, please send a new one.
Approval needed
orders_reship order 8142
Approved by Maya
orders_reshipReplacement created
Your replacement ships today, and the tracking link is on its way by email.
Where a thread can start
Use Cases
If you or your team can do a job in your app, AssistJet can do it through the same routes and under the same permissions. Sales, finance, operations, and support all run on one agent.
One Agent, Three Seats
The same agent answers your customers, helps your team on every dashboard page, and runs your automations while you are away. In a chat or on the dashboard, the agent can only do what that person is allowed to do.
Customer
The agent answers with sources, looks up that customer's orders and records, opens tickets, and passes the thread to your team. A visitor can reach only what that visitor is allowed to reach.
Team
Your team can open the agent on every dashboard page. It answers questions about your data, drafts replies, and makes only the changes that member is allowed to make.
Automation
A schedule, a record, a webhook, or a message starts a run. Each run uses only the tools you allowed and stops for your approval when you ask it to.
Full Reach
You no longer have to wire up an agent one action at a time. AssistJet reads the tools your app already has. When you ship a new route, it appears in the list, and you choose who may use it.
One Thread for Everything
Most teams run Zendesk or Intercom for support, Zapier for automations, and a chatbot on top, with glue code to connect them to the app. AssistJet stores a chat, an email, a ticket, an automation run, and an approval as the same kind of record, so your team works them all in one place.
Your team works chat, email, forms, and webhooks from one filtered list. You can turn the agent off and keep using the inbox.
Anyone on your team can take over a thread with one click and read the full history. You can also reply straight from your email.
You see the exact call before anything happens. You approve it once, and it runs once.
Each message, tool call, model, and cost is stored in the thread. There is no second audit system to search.
Paste a site address or upload your docs. The agent answers from them and links each source.
Set a name, a tone, a length, and the words to avoid. A live preview updates as you type.
Automations
AssistJet drafts the trigger and the steps as a card. Press Try It to run the draft on a copy of your data. Steps that need no model cost you no tokens.
Your Data
Most AI tools keep your conversations in a separate store that you have to secure and export. AssistJet writes every thread into your app's database, beside your records and the records of every other Substrio app you use.
Getting Started
Add AssistJet to an app you have, or create a new one. It reads your app's tools and tells you what it found.
Paste your site address or your docs, or skip this step. The defaults already work.
Press Go Live for the hosted widget, or copy one script tag into your site.
Security
A model can ask for anything. Only the calls your grants and your route gates allow will run.
A tool runs only when the seat has a grant for it and the caller passes the route's gate. Both are enforced in code before the call runs, so no model can talk its way past them.
A call that cannot be undone comes to you first. The approval covers that one exact call, and the call runs once.
A change to any seat's grant always comes to you, so an agent can never widen the access it runs with.
The customer seat has no built-in tools. A signed-in visitor can reach only what that visitor could already reach in your app, and an anonymous visitor can reach only public routes.
Each run has a limit on calls and writes. Writes made by a triggered run fire no further triggers, so a chain cannot grow, and you can set a monthly cost cap on any automation.
Every message, tool call, model, token count, and cost is stored in the thread. Your exports and backups include all of it.