How do I let the assistant work with nobody there?
A schedule step can be a free-form request to the assistant, in natural language. The assistant looks up whatever it needs, proposes actions and runs them if the schedule has them approved; what it can’t run, it leaves as a task for a person. This is what lets you, for example, reply automatically to the price enquiries that come in by email.
What do I need before I start?
The company must have the assistant available (an AI provider configured, or the central service). To ask for a reasoning level (1, 2 or 3) you need AI credits: the step spends them in your name, because the schedule runs in your name.
And you need to know one thing before you start: the assistant with nobody there can only do what you approve for it by category, and never more than the company allows to be done without confirmation.
How do I do it?
- In the schedule, add a step and choose Ask the assistant something in natural language (free-form step), marked with ✦ at the top of the drop-down.
- Type the request as you would say it in the chat: ‘check the outstanding orders older than a week and create a task in sales for each one’.
- Choose the level: 0 basic (no cost), 1 fast, 2 normal, 3 deep. Levels 1 to 3 spend credits; the Preview shows the approximate cost per run and per month.
- The What the assistant can run on its own block appears. Tick the action categories that will run without asking: Create and modify, Send email, Issue invoices, Receipts and payments, Delete and void. Whatever you don’t tick is left for a person.
- If the schedule replies to emails or messages, fill in Automatic reply (further down).
- Preview, Save and Approve and start. Approving a free-form step means approving its categories: whoever approves needs edit permission in the scope.
What happens when it runs?
The assistant receives your request, the data of the event that triggered the schedule (if there is one) and an instruction: there is nobody on the other side, so it has to resolve things or leave a record of them, without asking. It works with your permissions: it doesn’t see or touch what you can’t.
Each action it proposes is checked against the approved categories:
- If its category is approved and the company doesn’t require it to be confirmed by hand, it runs there and then and is listed in the run’s Actions run.
- If not, an Awaiting confirmation: … task is created with the action ready, High priority, due tomorrow and in your name. You open it, check it and run it with one click, or cancel it. See a task’s action.
There is a limit of ten actions per run. If the assistant is left halfway, the run ends in Error with what it managed to do.
The run summary says how many actions were left for a person. With Summary written by the assistant ticked, the assistant itself writes that summary in three or four sentences; if not, you get the table of steps.
Why won’t it let me tick ‘Send email’?
Because the company’s policy takes precedence. In Settings → POS and terminal settings → Terminals (‘Assistant actions’ card) each company says which categories require manual confirmation; out of the box they are email, issuing invoices, receipts and deletions. A schedule can’t approve what the company requires to be confirmed. The preview warns you and Approve rejects it.
If you want the assistant to send emails on its own, that category first has to be relaxed in the company’s policy. It is a decision for whoever administers the system, not for whoever schedules.
How do I set up the automatic reply to emails?
A new company comes with the Reply to price enquiries by email schedule, paused: it is triggered when an incoming email is classified as a price enquiry with high confidence, and asks the assistant to read it and reply with the customer’s price list. With no approved categories, each reply is left as a task with the draft so that someone sends it.
For the replies to go out on their own, tick Send email in What the assistant can run on its own (and relax the company’s policy) and adjust the limits in Automatic reply:
- Only to senders who are customers: an unknown sender doesn’t get an automatic reply.
- Only between one time and another: outside those hours there is no automatic reply. It can cross midnight (22:00 to 06:00).
- Daily reply limit: how many this schedule can send per day. Empty means the company’s limit (50 out of the box), which also takes precedence if it is lower.
- Fixed footer on every reply: a text that is always added at the end (‘Automatic reply. A colleague will review it during office hours.’).
Outside those limits the assistant writes the reply anyway, but it is left as a task for a person instead of going out. The run summary says why (‘the sender is not a known customer’, ‘outside the automatic reply hours’, ‘the limit of 50 automatic replies a day was reached’).
If something goes wrong
| What you see | What has happened | What to do |
|---|---|---|
| ‘The free-form step does not say what to ask.’ | The request is empty | Write it |
| ‘no AI engine is available’ in the run | The company has neither an AI provider nor the central service | The same as would happen to the chat: configure the assistant |
| The run doesn’t spend credits and answers worse than expected | The step is at level 0 | Give it level 1, 2 or 3 |
| ‘The company requires manual confirmation of actions that send email’ | The company’s policy blocks that category | Remove it from the ticked ones or change the policy in Settings → POS and terminal settings → Terminals (‘Assistant actions’ card) |
| Everything ends up as ‘Awaiting confirmation’ tasks | There are no approved categories, or an Automatic reply limit wasn’t met | Tick the categories and approve; read the reason in the summary |
| A reply went out without the footer | The footer was already at the end of the text | That is correct: it isn’t duplicated |
| ‘Approving action categories for the assistant requires edit permission in the scope.’ | Whoever approves only has view access | Have someone with edit permission approve it |
See also: Schedule something for when an event occurs · Ask the assistant to do something · Organising work with tasks and schedules