Assistance for teams. A coworker for everyone.
Seats for 2 to 150 people, your own model key, and a clear view of what every bot did.
- 2–150
Seats
Mix Standard and Premium seats as people need them.
- Your key
Your model provider
The owner adds the team's own key. It's stored encrypted on our server and never reaches laptops.
- Audit
One log for every bot
See what each bot did, for whom, and when, across the team.
- Policy
Rules for the whole team
Decide what bots may do on their own and what always needs a person.
A small team with a long reach.
Assistance doesn't replace people. It takes repeatable computer work off their desks. A rough sketch from your own numbers:
29hours
About the capacity of 4.7 people from a team of 4.
A sketch from your inputs and the assumptions under each task type, at 40 hours per full-time week. Real results depend on your work and setup.
Next to what you use today.
| Assistance | Virtual assistant | RPA tools | Chatbot | |
|---|---|---|---|---|
| Works in your apps | On your computer | By hand | In scripted flows | You do the clicking |
| Getting started | Describe the task in chat | Hiring and onboarding | Someone builds each flow | Same day |
| When a page changes | Reads the page and adapts | Adapts | The flow needs fixing | Not applicable |
| Schedules, day or night | Yes | Working hours | Yes | No |
| Asks before risky steps | Built in | Depends on the person | Rules you script | Not applicable |
A general comparison of approaches, not of specific products. Individual services vary.