How do I ask the assistant to do something in the ERP?
The assistant doesn’t just answer: it can create a quote, record a receipt or add a customer. It never does it on its own. It prepares a proposed action, shows it to you and waits for you to click Confirm.
How do I ask it?
You ask it in plain language, in the usual box:
- ‘Create a quote for Talleres Ruiz with 3 units of item A-100.’
- ‘Record the receipt for instalment 4512 in the bank account.’
- ‘Add the customer Muebles del Norte with Tax ID (NIF) B12345678.’
Talk in names, not numbers. You can say ‘Talleres Ruiz’ or ‘item A-100’ without knowing any internal number: the assistant looks them up itself and never asks you for an identifier. If the search finds a single record, it uses it without asking you to confirm it. If it finds several, it lists them by name and you answer by name: ‘the La Caixa one’.
Nor does it ask you for what the ERP can fill in. The code of a new record —customer, supplier or item— is assigned following the numbering you already use, and the same goes for an order’s warehouse, the series and the price list. If you prefer to set the code yourself —your usual reference, a barcode—, say so and yours is used.
**The same goes for the treasury account and the warehouse.** If your company has only one active account, it uses it without asking and the card names it in full, saying that the ERP has set it. If there are several, it asks you, listing them by name. The only exception is transferring stock between warehouses: that needs two and neither can be worked out, so both are always stated.
If it is missing details that only you know, it asks you for them once and all together, in plain language, before proposing anything. It doesn’t make them up.
It doesn’t repeat what it has already found out. Within the same conversation it remembers who and what the names it has already looked up refer to. If you have just added Muebles del Norte, ‘make them a quote’ applies to that customer without looking it up again. A ‘yes, go ahead’ or a ‘do it’ follows on from the last thing being done. With New conversation it forgets everything and starts from scratch.
And there is no need to paste again what you have already pasted. A long message —a table, a price list— or an attached text file stays as working material for the conversation: it has it in front of it, in full, in all the following messages. If you then correct something (‘the third one goes at 10 %’), just say so. It is explained further down.
When it has everything, instead of a text a card appears in the thread.
Do I have to repeat what I already gave it?
No. Whatever you paste or attach is kept as working material for that conversation, and the assistant has it in front of it in every following message. It will never ask you to paste it again or tell you it has no record of it.
The last three pieces you have given it are kept. The fourth pushes out the first, so if you need something from a long time ago again, paste it again.
New conversation clears it all: it starts blank, with nothing from before.
An attached text file —a CSV, a spreadsheet— goes in the same way, with the file name in front: attach a CSV or a spreadsheet. From an image or a PDF, on the other hand, only the name stays in the thread.
Nor do you have to repeat what you are talking about: if it has just looked up a document or a record, in the next message it has at hand what can be done with it. After finding invoice BOR0002, “delete it” or “send it to the customer” is enough; after seeing your treasury accounts, “set it to inactive”.
What does it show me before doing it?
The card is titled Proposed action and contains:
- A summary of what it is going to do, in one line.
- An Action details drop-down with the full list of details: customer, items, amounts, accounts… everything that is going to be used. Each detail is shown with its name, not with an internal number: it says Treasury account · Banco Santander (BS01), not a code that means nothing.
- The expiry time: Expires at HH:mm.
- Two buttons: Confirm and Cancel.
Read the details before confirming. Those details are exactly what is going to be run, no more and no less; they aren’t an approximate summary written by the artificial intelligence.
Whatever the ERP has filled in because you didn’t say it is shown marked with its reason: ‘Warehouse · Almacén central (ALM1) — set by the ERP: it’s the only one’, or ‘— your preferred account’ if it is the one you set. That way you can see at a glance what you said and what the program has decided for you.
Before showing you the card, the ERP checks that the action would work: that the report has the fields it asks for, that the invoice it is about to issue is a sales or a purchase one as the action says, that there isn’t already a customer with that code, that an email saying “please find attached” carries the attachment. If something doesn’t fit, the assistant fixes it by itself and shows you the right card. If it can’t fix it, it doesn’t show you a card that would fail when you confirm it: it tells you I could not prepare the action and the reason.
There can only be one live action at a time. While it is pending, the typing box says Press Confirm, or type here to change something…, and you can do either:
- Correct it by typing: “change the Tax ID”, “make it 5 units”. The assistant proposes the corrected card and the previous one is left as Replaced by a more recent proposal.
- Confirm it by typing “confirm”, “yes” or “ok”, and nothing else: it is the same as pressing Confirm. If you add anything (“confirm but change the Tax ID”), it is not confirmed: it is taken as a correction.
To cancel it, press Cancel: typing “no” does not cancel it.
What happens when I confirm?
- You click Confirm.
- The ERP checks again that you are still you and that your permission covers it, at that instant.
- It runs the operation for real, just as if you had done it by hand on its screen.
- The card is replaced by another: Action carried out or Action not carried out, with the result message.
What is created this way is a normal ERP document. It appears in its list, can be edited and can be voided in the usual ways. The assistant doesn’t create anything special or hidden.
If you click Cancel, nothing is run and the card is left as Cancelled. If you let the time run out, it is left as Expired without confirmation. And if you ask for another action before dealing with the first, the previous one is left as Replaced by a more recent proposal.
Every proposal is recorded, whether you confirm it or not: what was proposed, who, when and how it ended.
Can I ask it for several things in one message?
Yes. If in the same message you ask it for several operations that don’t depend on each other —‘create the Sofás family, create the Sillas family and raise the price of A-100’—, the assistant proposes them all together and they appear on a single card:
3 proposed actions
- New item family · Sofás
- New item family · Sillas
- Change the sales price of A-100
Each line expands to show its full details, just like a single action. Below there are two buttons: Confirm all and Cancel. Cancel cancels them all.
Up to 10 actions fit on one card. If you ask for more, it proposes ten and carries on with the rest after you confirm.
When you click Confirm all they are run in the order they are shown. Each one goes through its own checks —your permission is read again for each action— and each one is recorded separately.
If one fails, the following ones aren’t attempted. The result card says which were done and where it stopped, with the ERP’s message. What is done is done: you correct what failed and ask it for the rest.
And if each step needs the previous one?
They also go on one card. “Create an order for 10 chairs for ACME, turn it into a delivery note, invoice it and email it to them” is four actions, and each one works on what the previous one leaves: the delivery note comes from the order, the invoice from the delivery note, and the email carries that invoice. The assistant proposes them all at once:
4 proposed actions
- Sales order · customer ACME (00002) · 1 line(s)
- Convert the document from step 1 into Delivery note
- Convert the document from step 2 into Sales invoice
- Send the document from step 3 by email to compras@acme.com
Since what a step creates doesn’t exist yet when it is proposed, its details say It works on the result of step N of this card. With one click on Confirm all they are done in order, and each step works on what the previous one has just created. If one fails, the ones that depended on it aren’t attempted, and the result card says what was done.
Within a multi-step task this doesn’t change: there is still one action per step, and the confirmation is the plan’s. It is in give it a multi-step task.
Does it carry on by itself after I confirm?
Yes, when what is left can’t be proposed yet: it needs something you have to decide after seeing the result. What only needs what the previous step leaves already goes on the same card (see “And if each step needs the previous one?”). In the other cases, the assistant proposes the first part and, as soon as you confirm it, carries on by itself without you typing anything.
You will see it in the thread: the sentence Carry on with what’s left. comes in as another message. It is visible on purpose —there are no hidden turns—, and after it comes the next card, which you confirm just like the first.
It also carries on by itself when the card filled up with ten actions and there were more, and when your request asked for more things than have been done so far: “create the customer, make them a quote and send it to them” is three, so after you confirm the first one it carries on with the others. It also counts what is joined without its own verb (“create the customer Juan and a quote for 3 tables” is two), and if it asks you something along the way —a missing tax ID—, your answer doesn’t make it forget the rest.
Each next step asks for your confirmation again: carrying on by itself never means doing anything without asking you. If it ever stops before finishing, type ‘carry on’ to it and it picks it up again.
What happens if it reaches the step limit?
To answer you, the assistant takes steps: it looks up a piece of data, reads the result, looks up another. There is a step limit per request that exists to keep AI usage very low. If it reaches it without finishing, it doesn’t cut the conversation: it tells you what it has so far and shows a card with two buttons:
- Continue (4 more steps): it carries on from where it left off, without repeating what it has already looked up, with four more steps for this conversation. You can press it again if needed.
- No limit in this conversation: it carries on with no step limit until you start a new conversation.
If you ask it to do something and it asks “shall I do it?”, you don’t have to answer in writing: the question is the card itself, which you confirm or cancel. And if it says it can’t do something you asked, before answering it tries again with all its tools in view and, if needed, with a higher-capacity model, at no extra cost to you.
What can it do?
It depends on the module, and always within what your role lets you do by hand.
Sales. Create a quote, create an order, add or remove a line on a document and convert a document (order to delivery note, delivery note to invoice). And close the cycle: issue an invoice that is in draft, invoice several delivered delivery notes in one go and void a document. A line is never removed from an issued invoice, nor the last one: a document can’t be left empty.
On a document that can still be changed —a draft, or a quote, order, delivery note or service report not yet invoiced—, sales or purchase, it can also add a line, change it —the quantity, the price, the discount, the description or the warehouse: “on order 3001 make it 5 units instead of 3”— or remove it, and change the header: the date, the reference, the notes, the payment method or the warehouse. That is how material goes into a service report already open: “put item 000006 in report A00001”. Whatever you don’t mention stays as it was. It doesn’t touch what no longer admits changes: an issued invoice (it is voided or corrected), a document already invoiced (it is corrected in the next one) or a delivered service report (it is set back to Repaired). A line with batches, serial numbers or components changes quantity on the screen, where the breakdown is allocated.
It can also delete a document, sales or purchase: “delete quote 120”. It uses the same deletion as the screen, so it needs the same permission (full access). Before you confirm, the card tells you what will happen: whether it is deleted, whether it is voided —an issued sales invoice is not deleted: it is voided keeping its number and the voiding is sent to the Tax Agency— or whether it can’t be and why (a voided document, one another document already came from). It is final.
Name documents as you see them in their list: “delete BOR0002”, “invoice A000002”, “purchase order A00003”. A draft has its own number too (BOR…). If two document types share the same number, put the type first: “order A0001”. The same goes for records: a customer or supplier by its code or name, a treasury account by its code (“account BAN01”).
Customers, suppliers and items. Create a customer or a supplier —the name is enough; the ERP sets the code— and update their contact or tax details. If the record has two names and a person, tell it all three and each one goes to its own box: "create the customer Ferretería Sierra, legal name Ferretería Sierra S.L., contact José Luis Gómez" puts the trade name in Trade name, the legal name in Legal name and the person in Contact. Create an item —again the name is enough, plus the item family, description, brand and price if you give them— and change the sales price of one that already exists. The ERP proposes the item code following your series; if yours is a real reference you want to keep, give it and yours takes precedence. The price can be given excluding VAT or including VAT, stating the rate. A name that another item already has is rejected, with the code of the existing one. So is a name that is the code of an item you already have (asking for “item 000006” doesn’t create a new one called “000006”: it tells you which one it is).
It also creates several items at once from a list, a pasted table or a file —up to 50 per action, in a single confirmation—, and separate item families and sub-families. It is explained in add several items at once.
And it corrects an item that already exists, without creating another. You tell it which one —by its code or its name— and what changes: the name, the description, the item family, the brand, the supplier, the price or the code. Whatever you don’t mention stays as it is. It can also delete it, or mark it as discontinued so that it is no longer offered without losing its history. That is what to ask for when an add went wrong: correct it, not add the record again.
The code can be changed. The only thing the ERP checks is that no other item already has it; if one does, it tells you which and doesn’t touch anything.
An item that already appears on an invoice, delivery note or order isn’t deleted: in that case the way is to discontinue it, and the assistant tells you so when it tries.
Several at once, too. ‘Set the supplier Antea Business on all of them’, ‘move these items to the Sofás family’, ‘discontinue them’ or ‘correct these codes’ is a single action for the whole list —up to 50—, with a single confirmation. It is checked in full before anything is touched: if a row is wrong none is changed and it tells you which and why. You give it the supplier by name; if several suppliers share that name, it doesn’t choose: it shows you which they are and you tell it which one.
It also deletes several items at once —up to 50— from a list or a pasted table: ‘delete the items in this list’. They all appear on a single card, with a single button. Those that don’t exist or have already been used in documents are skipped, and at the end it tells you which it has deleted and which it hasn’t, with the reason for each.
A single field on a record, calling it by its name. For fields not covered above —ones your installation has custom-made, or the less common ones on a record— you tell it which record, which field and what value: ‘change the notes of customer 42’, ‘tick the publish box on item family 7’. It works with the item, item family, brand, customer, customer type, carrier and treasury account records; if you ask for another, it tells you which it can do.
Some fields aren’t written this way, and it tells you so when you try. Some are calculated automatically —an item’s stock, what you owe a supplier— and come from their movements, not from typing them. Others are changed through their own process, and then it tells you how it is done: the amount of an instalment is changed by recording the receipt, not by typing it.
As it doesn’t look the record up by name, it needs to know which one it is: ask it to look it up first, or give it its number.
And it replaces an entire list: delete and create again, in a single step. Paste it the table as it should end up and ask it ‘delete these items and create them again’. It is a single action: it finds the records that already exist by their name or their code —so it works even if you have corrected the code in your table—, deletes them and creates the new ones, all or nothing. If something fails halfway, nothing is left deleted. If there are several records with one name, they are all replaced by the one in your table. A record that is already on a document can’t be deleted: that row is skipped and it tells you so.
The card shows you what is going to happen, not just what you asked for. Before you confirm a deletion, a replacement or an add of several items, at the very top you read which records will be deleted (with their code), which will be created and which will be skipped and why. If the action wasn’t going to do anything —they all exist already, the code you gave isn’t there— it says so there, before you click.
If two items have the same name, it doesn’t choose for you. When you ask it to change or delete one by its name and there are several with that name, it doesn’t touch any: it tells you their codes and you tell it which by the code, which is never repeated.
Receipts and payments. Record the receipt of an instalment against a treasury account and record the payment of an instalment to a supplier. Generate a direct debit batch grouping several instalments, or a payment batch with its SEPA file. Issue a voucher in favour of a customer. And apply an advance payment already received to the instalments that are still outstanding: the assistant allocates it in order and, if the balance isn’t enough for all the ones you have given it, it doesn’t do anything and asks you to remove some. It never leaves an instalment marked as settled without money behind it. And it can **set your usual *treasury account***: ‘always collect through Santander’ gives you a card that, when you confirm it, saves that account as yours for receipts and payments that don’t say otherwise. It is explained in Collect an instalment.
Accounting. Create a manual journal entry: its date, its description and its journal lines with debit and credit. The journal entry must balance. If the debit doesn’t equal the credit, if it uses a group account or a blocked account, or if it falls in a closed period, it is rejected in full and nothing is saved. An invoice’s journal entries aren’t made this way: the document itself generates them.
Warehouse. Adjust an item’s stock, transfer a quantity between warehouses and adjust the stock against a count: you dictate what you have counted for several items and it sets the stock of all of them to the counted figure, in one go. It checks the whole count before touching anything, and at the end it tells you line by line what there was and what it has left. If you don’t say the warehouse and you have several, it uses the company’s default warehouse; it only asks if none is set up.
With an item that has batches or serial numbers, the adjustment is done as on the screen: a warehouse receipt if it adds and a warehouse issue if it takes away, with its batch or its numbers. “20 of LECHE-1 from batch L2611 have come in, expiring 30/11”, “write off 3 from batch L2610”, “serial numbers SN100 to SN104 of laptop P-15 come in”. On a receipt you have to give the batch or the numbers; on an issue, if you don’t, the oldest go out, just as on the screen. With batches you don’t set a total (“leave it at 50”): you say what comes in or goes out. To transfer such an item, it proposes on the same card the issue from one warehouse and the receipt in the other with the same batches.
CRM. Create a contact, a note or a deal card; move a card to another column; change a contact’s sales status and reassign the owner.
CRM: calendar and deals. Create an activity, schedule an event —an appointment with its length in minutes, and in another owner’s name if you say so— and mark as done a pending activity, with a result note if you want. An activity that was already completed isn’t reopened: it tells you so and doesn’t touch anything. It can also create a deal with its amount, its probability and its expected closing date, all in a single confirmation.
A calendar event that isn’t with a contact —an internal meeting, a reminder: “put a team meeting in the calendar on Tuesday at 10”— is left as a task with its date and time, which also shows in the calendar. And if you ask how many AI credits you have left this month, it tells you with the same figures as the assistant’s costs screen.
Email. On your mailbox: send a new email, reply to an email you have (to the sender only or to all), leave an email ready in Drafts without sending it, mark an email as read or unread, and move an email to another folder. And separately, send a sales or purchase document —an invoice to a customer, an order to a supplier— by email with its PDF attached.
What leaves your mailbox —a new email, a reply or a draft— can carry ERP attachments: the PDF of an invoice, a delivery note, an order or a service report, or a report in PDF, CSV or Excel. “Send invoice A000002 to compras@acme.com” goes out with the PDF attached. If the text says “I attach…” and nothing is attached, the action isn’t processed: that way no email goes out promising something it doesn’t carry.
Reports. Create a report in the designer with the columns and filters you ask for, and pin a report to your menu with the filters already set. With existing reports it does quite a lot more, and that doesn’t need confirmation because it doesn’t change anything: find them, run them —by their name, and giving it the customer or supplier by name, not by code—, give you the link to open them on screen with the filters set —the PDF and the spreadsheet are produced from that screen—, and analyse them: see how an amount evolves month by month, compare two periods or project the next ones. And without you asking: when an answer is a list of data, View as report appears next to it (how it works).
A note on the words: converting a document to an invoice leaves it as a draft document, with no number. For it to be an issued invoice you need the issue action, which is something else.
When converting you don’t have to bring everything. If only part of the order arrives or goes out —“only 6 of the 10 boxes of purchase order 45 have arrived”, “from order 3001 deliver only 3 chairs”—, the delivery note is made with those quantities and the rest stays pending on the order, for the next delivery. It won’t bring more than what is still pending.
Which actions should I look at twice?
Almost everything the assistant does can be corrected afterwards, just as if you had done it yourself by hand. Not these five. The card says so in plain words before you click Confirm.
Issuing an invoice, on its own or by invoicing several delivery notes in one go. The invoice gets its final number, moves stock and open items, and is reported to the Spanish Tax Agency (AEAT). An issued invoice can’t be ‘un-issued’: if it is wrong, it is voided or corrected, and both leave a trace. What exactly happens when issuing is in Issue an invoice.
Voiding a document. It is final. It reverses the effects and leaves it voided, but doesn’t delete it: if the document was a tax document, the voiding is also reported to the AEAT and the legal record still exists.
Deleting an item. The record disappears from the master and can’t be recovered. If the item has already been used in a document, the ERP doesn’t let you delete it; and if what you want is to stop offering it without losing what is behind it, ask it to mark it as discontinued.
Sending an email or replying to one. The message has already gone and can’t be pulled back. If it isn’t final yet, ask it for a draft.
Generating a payment batch. Here the warning works the other way round: the action **prepares the SEPA file, it doesn’t order the payment at the bank**. The money doesn’t leave until you submit that file in your online banking. The ERP’s bank connection only reads movements. In the ERP, however, open items and treasury are updated when you confirm. The full process is in Record a payment to a supplier.
What does it show me before sending an email?
When the action is an email one, the card’s summary says who is being written to and with what subject, or the email and the folder if it is only being moved or marked. The message text never appears there, on purpose: that text is drafted by the assistant and, when replying, it may be coloured by what the original email says. A message that comes from outside is data, not an instruction, and it isn’t going to be presented to you as if it were a sentence from the program.
The full text is in the Action details drop-down, as one more detail among the others. Open it and read it before confirming a send.
When replying you only write the new text. The recipient, the ‘Re:’ in the subject and the quote of the original message are added by the ERP by reading the email you are replying to, not by the assistant.
If the message isn’t final yet, ask it for a draft: ‘leave it in drafts and I’ll check it myself’. It stays in Drafts, nothing goes out, and you send it yourself from Email when you are happy with it. It is the cautious option, because a sent email can’t be pulled back.
It only works on your mailbox: a colleague’s email doesn’t exist for it. If you don’t have an email account set up, it tells you so and does nothing. And marking an email as read marks the whole thread of that conversation, not just the message you pointed it to.
And if my company doesn’t want the assistant to run anything?
It can be turned off. Whoever administers the ERP can turn off the actions channel completely, or leave it open only for some modules —for example sales and receipts and nothing else—, or set a limit of actions per day.
With the channel turned off, the assistant still answers and queries data as normal; it simply stops offering action cards.
Above that policy your role always takes precedence: if you can’t create orders by hand, you won’t be able to create them through the assistant either.
If something goes wrong
| What you see | What has happened | What to do |
|---|---|---|
| ‘The proposal has expired: ask the assistant for the action again.’ | The card’s time ran out | Ask for it again |
| ‘There is no proposal pending confirmation…’ | It was already cancelled, it expired or another replaced it | Ask for it again |
| ‘The session has changed since the action was proposed: it has been discarded.’ | You changed company or user in between | Ask for it again in the right company |
| ‘You no longer have enough permission to run this action.’ | Your role was changed between the proposal and the confirmation | Ask for the missing permission |
| ‘The action cannot be proposed: you have reached the daily limit of actions…’ | The day’s quota of actions has been used up | Wait until tomorrow or do it by hand |
| Action not carried out with a message from the ERP | The operation was attempted and the ERP rejected it | Read the message: it is the same one you would see on the screen |
| ‘The activity … is already completed.’ | You asked to close an activity that was already done | Nothing: it hasn’t been touched. To reopen it, go to the contact’s record |
| ‘The … isn’t in draft…: this action only removes lines from drafts.’ | You asked to remove a line from a document already issued | Edit it on its screen, or void it |
| ‘It is the only line on the …: a document can’t be left empty.’ | You asked to remove the last remaining line | If the whole document isn’t needed, void it |
| ‘The available balance … doesn’t cover all the instalments given.’ | The advance payment isn’t enough for all the ones you gave it | Nothing has been done: remove instalments from the list and repeat it |
| ‘The journal entry doesn’t balance (…): it won’t be saved until Debit and Credit match.’ | You asked for a manual journal entry whose debit doesn’t equal its credit | Nothing has been saved: correct the amounts and repeat the action |
| ‘Stock count rejected without applying any adjustment: …’ | A line in the count doesn’t add up: an item that doesn’t exist, a repeated one or a negative quantity | No stock has been touched: correct that line and repeat the count |
| ‘Item X “…” already exists. If you really want another one with the same name…’ | You asked for an item that has already been added | Use the existing one, or tell it you want another the same |
| ‘Row N (“…”): …’ when creating several items | A row in the list is wrong | None has been created: correct that row and repeat it |
| ‘There is no item with the code or name “…”.’ | You asked to change or delete one that isn’t there | Look it up in Warehouse → Items: it may have another name |
| ‘There are N items called “…” (codes …). Say which one by its code.’ | You asked to change or delete by name, and several items have that name | None has been touched: repeat it with the code of the one you want |
| ‘There are N suppliers matching “…”: … Say which one…’ | You asked to set a supplier and several share the name you gave | Nothing has been touched: give it the full name or the code of the one you want |
| ‘Batch rejected without modifying any item: Row N (“…”): …’ | When changing several, a row is wrong | None has been changed: correct that row and repeat it |
| ‘Another item with code “…” already exists.’ | You asked to give it a code another record already has | Nothing has been touched: choose another code, or look at what that other record is |
| ‘The field “…” is calculated automatically: a value can’t be assigned to it.’ | You asked to write an accumulated figure, such as stock or risk | It comes from its movements: change it with the corresponding movement |
| ‘The field “…” isn’t written by hand; it is done with “…”.’ | That field is changed through its own process | The message says which: ask for it that way |
| ‘The field “…” doesn’t exist.’ | The field name doesn’t belong to that record | Look it up on the record’s screen and give it the label you see |
| ‘“…” can’t be edited. The ones that can: …’ | You asked to change a field on a record this action doesn’t support | The message lists the ones that can; for the rest, use their screen |
| ‘The identifier of the record being changed is missing…’ | You asked to change a field without saying which specific record | Tell it which one, by its code or name |
| ‘The ‘…’ field doesn’t exist. The ones that can be changed: …’ | That record has no field with that name | Pick one of the listed ones; the name you see on the record works |
| ‘The item cannot be deleted: it is used in document lines.’ | The item has already been invoiced, delivered or ordered | It isn’t deleted: ask it to mark it as discontinued |
| The card with several actions stops halfway | One action failed and the following ones aren’t attempted | Read the message, correct that and ask it for the rest |
| ‘The email has been saved in Outbox to retry it’ | The mail server didn’t respond | Nothing: the email hasn’t been lost and is retried automatically. Look in Outbox in Email |
| ‘No email account is set up for this user…’ | Your user has no mailbox | Set up your account in Email; a colleague’s won’t do |
| The assistant never proposes actions | The channel is turned off, or your module isn’t enabled | Check with whoever administers the ERP |
See also: Ask the assistant something · What the assistant knows and what it doesn’t
More about Assistant
- Can I attach a CSV or a spreadsheet for the assistant?
- Can I show the assistant an image or a PDF?
- How do I teach the assistant about my company?
- How do I add several items at once with the assistant?
- How do I choose how much effort the assistant makes?
- Working with the assistant
- How do I ask for a professional analysis and what does it cost me?
- How do I put the assistant on my website?
- How do I ask the assistant something?
- Test the assistant and find out what it costs
- Can I tell the assistant to stop asking me about the professional analysis?
- What does the assistant know and what doesn’t it?