Approval before changes
Anything that creates, changes, sends or deletes shows a preview and waits for a tap.
Integrations
Answers, or actions. You choose.
Every RageEdge assistant answers questions from your own data. If you want more, connect your tools and it can also check stock, create tickets and book slots, always within the rules you set. Connecting tools is optional.
Try both modes
-
Answers from your data Manuals, price lists, stock. Works offline.
-
Uses your connected tools Check, create, book, update.
-
You approve every change Logged to the audit trail. Queued if offline.
Connected to this assistant
- InventorySynced
- ManualsSynced
- CalendarTool
Service desk assistantOnline · synced 08:40
Example conversation
Connect a tool
Three steps to your first action.
Describe the tool
A name, what it does, the details it needs and whether it only reads or also writes.
Point it at your system
A REST or GraphQL endpoint, a webhook, or a function in your own app through the SDK.
Set the rules
Which roles may use it, whether it needs approval, and what happens when the device is offline.
ai.registerTool( name = "book_slot", description = "Book a service slot for a vehicle", params = params("vin", "day", "time"), access = Access.WRITE, // READ or WRITE approval = Approval.ALWAYS, // ask before it changes data roles = listOf("service-advisor"), offline = Offline.QUEUE // send when back online) { args -> bookingApi.book(args) }Code shown is illustrative.
Guardrails
Actions only within the rules you set.
Read or write, per tool
Mark each tool as read only or write. Read tools never change anything in your systems.
Roles decide who can act
A technician can check stock; only a service advisor can book a slot. Set it per role and per site.
Every call is logged
Who asked, which tool ran, with which details, who approved it and the result, in the audit trail.
An offline queue you can see
Changes made offline wait on the device, visible and cancellable, and are sent when it reconnects.
Off by default
A new assistant answers only. Tools are added one at a time, and can be switched off at any moment.
What you can connect
Your systems, through the interfaces they already have.
No new middleware. If it has an API, a webhook or a function in your app, the assistant can use it.
Inventory and ERPStock levels, parts, orders, deliveries
CRMCustomers, vehicles, contracts, follow-ups
Ticketing and serviceCreate, update and close tickets and jobs
SchedulingSlots, shifts, appointments, routes
Document systemsLook up and file reports, forms, photos
REST and GraphQL APIsAny internal service your team runs
WebhooksNotify other systems when something happens
On the deviceCamera, files, calendar and app functions. These work offline.
FAQ
About tools and actions
No. Every assistant answers from your data without any tools. Add tools later, one at a time, when a team needs the assistant to act.
Only read tools you allow to run on their own. Anything that creates, changes, sends or deletes can be set to always ask first, and that’s the default.
Tools on the device, like the camera or files, work as normal. Tools that need your servers wait: changes are queued on the device, visible to the user, and sent when it reconnects. Answers from synced data keep working.
On the device. A small model picks the tool and fills in its details, so planning works without a network. Only the final call to your system needs a connection.
Every tool call lands in the console’s audit trail with the user, the details, the approval and the result. You can filter by tool, team or device.
Put AI where your work happens.
Pick one team and one use case. We’ll have it running on your own devices in weeks.