Use cases by area
Each case lists its steps, whether anything leaves your computer, whether it can be undone and how many checked runs in a row it needs to run on its own.
Administration and finance
Invoices, receipts, collections and payments: whatever arrives by email or in a folder, recorded in its sheet and filed where it belongs.
3 casesInsurance
Policies, premiums and claims: from the incoming email to the insurer's system, with a person deciding what matters.
3 casesSales and customers
Quotes, orders and follow-up: replies prepared for review, never sent on their own.
2 casesCustomer support
Enquiries and complaints sorted, with the customer's data at hand.
2 casesHuman resources
Staff paperwork in order and documents made from their templates.
2 casesOperations and logistics
Delivery notes, shipments and suppliers: what changes outside, seen in time.
2 casesLegal and compliance
Contracts from templates and regulatory changes watched, with a person reviewing.
2 casesMarketing
What is published in your sector, summarised; texts translated and ready for review.
2 casesIT and systems
Backups, folder reports and maintenance that is not forgotten.
2 casesManagement and office
Day to day: the morning email summary and whatever repeats every week.
2 casesWhere the cases come from
- Roubot is tested with requests written the way a person writes them. These are the ones in the test bench, by area.In the test bench
- The example requests only use action types that already have an action in Roubot. They are not in the test bench.Example request
- To become autonomous, an automation needs 20 checked runs in a row; 60 if any step leaves the machine or cannot be undone.
See it working on your own work
Tell us about a task that repeats in your organisation and we will show you how it would look as a flow, with its log.
hola@roubot.ai