Skip to content
Omni Studio
Start free
Use cases

Start with the job that eats your day

Pick the job you're tired of doing yourself.

All use cases

Before you start

Not sure which job to start with?

Five questions to find where to start.

Is this a good first workflow to automate with AI?

A good first job comes up every week, has one clear owner, uses records you already keep, and starts with reading and drafting. Pick the one that costs the most time, and note today's baseline.

What should stay behind approval at first?

Keep a person on anything a customer sees, anything that touches money, and anything you can't undo. In Omni, sending, spending, signing and changing wait for your approval by default. Start with every gate on, and in early access you can take over the AI employee's computer yourself.

What do you measure after the first job goes live?

The baseline you chose the job on, how often you edit or reject a draft, and how long a job waits for approval. The activity log shows each request, approval and change.

Which jobs should you not automate first?

Jobs with high-risk exceptions, legal or compliance calls, safety decisions, unusual promises, or no clear owner. An AI employee can prepare those, and a person decides. If a job fails the check, start smaller.

How do I know my business can run AI employees safely?

You're ready when you can name the job, the approver, the records it reads, and the tools it may use. An owner or admin sets each AI employee's allowed tools, logbook and monthly limit for AI work. In early access you can pause it at any time.

Every example uses sample data. We don't have customer stories yet. Review requests, reactivation and weekly owner reports work in every workspace. Longer reads: the workflow audit checklist and how to choose your first job.

Start small

Start with one job

Try it free for 14 days on sample data.

Start free Talk to a person

See it work

All stories

From the journal

More from the journal