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 can you do for us?

Two answers, and it is worth keeping them apart.

Today the assistant is text support. It was built to answer questions about EyeOnTask — how a feature works, where a setting lives, why the app did what it did, what an error means. Ask, and you get the answer with a link to the page it came from.

Doing the work comes in an upcoming version. Creating a job for you, pulling a report, telling you where a fieldworker is or what a client still owes — all of that is being built, and none of it works yet. See what it is being built towards.

So if you are asking can you set this up for me? — not yet. If you are asking how do I set this up? — that is exactly what it is for.

When you ask it to do something, or to look something up

People ask the assistant for their own records as naturally as they ask it how things work — show me the last invoice, how much is due. Today it cannot do either. It has no access to your account, so it cannot open, read, change or export anything in it, and it will say so rather than answer a different question.

What it gives you instead is the three things that are true today:

It cannot do that yet — it shares knowledge about EyeOnTask, and does not act on your account.
How to do it yourself, now — the screen and the steps.
It is coming — looking things up and doing the work from this window are features on their way to the assistant.

Some questions asked this way, and the answer each one gets today:

You ask	Today
Show me the last invoice for Harbour REIT.	It cannot see your invoices. Open Invoices, switch to Table View and search the client’s name, or open the client and read their Invoice tab — see a client’s quotes and invoices.
Do you have access to my data?	No. It reads this documentation only. Your jobs, clients, invoices, figures and people are not visible to it.
How much is due?	It cannot see your figures. Due Amount sits above the invoice table in Table View, a client’s own balance is on their Payment tab, and everyone who owes you is in the Client Receivable report.
Can I extract all the data in the portal?	It cannot export anything. In your EyeOnTask account, each list and report has its own Export or download — reports, the invoice and request tables, a client’s payment ledger, your item list. For everything at once, ask EyeOnTask support. If you meant the customer portal your clients sign in to, that is covered in customer portal settings.
Can you create a new job, or copy a quote and add a new client?	It cannot create or copy anything for you. Raise a job with Add Job — see creating a job. To build a quote from an existing one, open it and choose Copy Quote on the ≡ menu — see copying a quote. A client is added under Clients — see adding a client.
There was an option to delete a job from the schedule — I can’t find it now.	That one it can answer. Right-click the strip and choose Delete Jobs. If it is not in the menu, your user may not have permission to delete jobs — ask your Super Admin. See deleting a job from the board.

When looking things up and taking actions arrive, questions like the first four will be answered from your account directly — see what it is being built towards.

What EyeOnTask does, module by module

The other thing people mean by what can you do is what the software covers. Briefly:

Module	What it is for
Jobs	The work itself — created, scheduled, dispatched to a phone, completed and reported on
Scheduler	The board the work is planned on, by person and by day
Mobile app	What the fieldworker carries — their jobs, check in and out, items, photos, signatures, offline
Requests	Enquiries and leads before they become work, including from your own website
Quotes	Pricing work before it is agreed, with optional lines and e-signature
Invoices	Billing it, taking payment, credit notes and statements
Contracts	Standing agreements — recurring visits, rate cards, contract invoicing, leased equipment
Clients	The customers, their sites and their contacts
Inventory	Parts and products, stock, suppliers and purchase orders
Equipment	Individual units with a serial number and a service history, yours or the client’s
Users	Your people, their permissions, attendance, worklog and pay
Expenses	What the work cost, against the job it belongs to
Reports	The questions that span everything — revenue, receivables, stock, time, travel
Settings	The lists and rules behind all of it, and the integrations — QuickBooks, Xero, Stripe, PayPal, Zapier, SMS
Developer API	Putting jobs and requests in from your own systems

What EyeOnTask is is the fuller picture, and every module has its own How it works page.

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 look up data in 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 take actions for you. It can tell you how to create a job; it cannot create one for you. Every action still happens in the app, by you — until doing the work arrives in an upcoming version.

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. What that means in practice:

Creating work. Book a service call for Alpha Clean on Thursday morning and put Edward on it — the job created from the sentence, instead of being talked through the form.
Reports on demand. What is this month’s revenue? — the figure answered in the conversation, with the report it came from one click away, so the number can be checked and exported.
Questions about your own account. Where is Edward right now? How much does this client still owe? What is overdue today? — read from your data rather than from the documentation.
The small chases. Which invoices are unpaid, which jobs nobody has picked up, which equipment is due a service.

One window for all of it — asking and it happening, rather than an assistant that describes the app beside the app.

Two things will stay true when it arrives: it will only do what your permissions already allow, and anything that changes your data will ask you to confirm before it does it.

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.