What You Can Do with Operator
Start from the problem, not from the feature
Most help pages explain how a button works. This section answers a different question: what can you actually achieve with Operator, and what does it take to get there?
Everything in Operator comes down to four kinds of result.
| Outcome | What it means | Read |
|---|---|---|
| Answer and advise | An agent that looks things up in your data and documentation, explains, drafts and replies. | Answer and advise |
| Watch and act | An agent that runs on its own — on a schedule, on an incoming email, on an event — and takes action. | Watch and act |
| Build apps for your team | A screen or tool built in natural language, running on your live business data. | Build apps for your team |
| Publish to the outside world | A page anyone can open — no login, no account. | Publish to the outside world |
Playbooks: problems and the solution you can build
Each playbook is a complete recipe — the problem, what you end up with, what it needs, and the exact steps (including what to type) to build it.
| The problem | Build this |
|---|---|
| Supplier or competitor prices change and nobody notices until margin is gone. | Price-watching agent |
| The same customer questions arrive by email fifty times a week. | Email answering agent |
| Customers phone to ask "can I get it in this size, this colour, what does it cost?" | Product configurator website |
| Salespeople on the road can't see stock, prices or customer history. | Mobile sales app |
| A salesperson is driving and can't type an order or a visit report. | Voice sales executive |
| Overdue invoices pile up because nobody has time to chase them. | Overdue invoice chaser |
| Approval requests get lost in email threads. | Approvals desk |
| Field technicians report time and materials on paper. | Field service check-in app |
| Management asks for numbers that take a day to assemble. | Management cockpit |
How much work is any of this?
Almost all of it is conversation. You describe the outcome to the Agent Builder or the App Builder; it builds, you test, you correct. A simple agent is minutes. A working app is usually one sitting. The playbooks say honestly which ones need a Pro app, which need a connected ERP.net instance, and which need nothing but an agent.
Not sure which one fits?
Ask the Advisor agent in plain words — "prices from my suppliers keep changing, can Operator help?" The Advisor searches this documentation, including every playbook here, and will point you at the right recipe and walk you through it.