The AI assistant

EyeOnTask carries an assistant you can ask questions in plain language, instead of hunting through screens or reading a whole page to find one line.

Ask it how do I raise a credit note, why is my invoice not syncing to Xero, where do I add a payment mode — and it answers from this knowledge base, with a link to the page it took the answer from so you can read the detail yourself.

What it can do today

It answers questions about how EyeOnTask works. Every module, every screen, every setting documented here:

• How to do something — the steps, in order, with the buttons named.
• Where something lives — which menu, which tab, which settings screen.
• Why something behaves the way it does — why an invoice will not delete, why attendance and worklog disagree, why a job will not drag on one scheduler view.
• What an error means — the sync failures, the messages the app shows you.

It gives you the page it answered from, so you can check the full explanation rather than take a summary on trust.

What it cannot do yet

It cannot see your account. The assistant reads the documentation, not your database. So it can tell you how to find an unpaid invoice, and it cannot tell you which of your invoices are unpaid. Your jobs, clients, figures and people are not visible to it.

It cannot do anything for you. It explains how to create a job; it does not create one. Every action still happens in the app, by you.

It only knows what is written here. A question about something undocumented gets an honest I don’t have that yet rather than a guess — which is deliberate. An assistant that invents an answer about your money or your schedule is worse than one that admits the gap. When that happens, the documentation is what needs fixing, and telling support which question failed is what gets it fixed.

What it is being built towards

This part is not available yet. It is written here so you know where the assistant is going, not because you can use it today.

The intention is that the assistant stops being only a reader of documentation and starts doing the work from the same window:

• Create a job from what you tell it, rather than talking you through the form.
• Show a report — pull the figures and put them in front of you instead of naming the report to run.
• Answer questions about your own account — where a particular fieldworker is right now, how much this client still owes, what is overdue today.

The shape of it is one window where you ask and it happens, rather than an assistant that describes the app beside the app.

Until then, everything above under what it cannot do yet still applies, and nothing here is a commitment to a date. If a workflow of yours depends on one of these, tell support — it is worth knowing which of them matters most to the people using it.