Ask AwraIQ about features, pricing, onboarding, login, integrations, security, demos, mobile apps, automation, reports, or support.
Ask a question about your records. See the report that answered it.
“Sales by customer last month.” “Open purchase orders over 100,000.” The question becomes a custom report definition, the definition runs through the report engine under your own permissions, and the answer comes back with the definition written out in plain words, so you can check what was actually counted.
- “Sales by customer last month”Question
- Dataset · Customer invoicesDefinition
- Issue date · last monthFilter
- Grouped by customer · sum of totalSummary
- Customer A412,500.00
- Customer B288,040.00
Illustration of the screen’s shape. Names and figures are examples.
A question in, a checkable report out.
Ask
Type the question the way you would say it. Suggestions on the page are drawn from the datasets you are allowed to read.
It becomes a definition
A dataset, columns, filters, a period, a grouping and a sum or count — the same parts a report built by hand has.
The engine runs it
Through the custom report engine, with your permissions, row-level security, the query time limit and your plan’s row cap. Up to 200 rows show on the page.
Check, then keep it
Read the definition beside the answer, open it in the report builder to change anything, or save it as a report of your own.
The model writes a definition. It never reads a row.
Its reply is treated as untrusted input. Anything it names that is not on the allowed list is refused outright, rather than quietly dropped or turned into a query.
Field names, not records
The model is shown the names, labels and types of whitelisted fields on datasets the person asking may read. No customer, no amount, no row.
Unknown means refused
A dataset, field, join, operator or period that is not on the list stops the answer. Nothing becomes SQL except through the report builder’s own payload.
Every question logged
The question, the definition, who asked, from where and how long it took. The rows of the answer are never stored in the log.
The report datasets you already have, in the words you already use.
Sales
Customer invoices, POS sales, sales orders, quotes and customers. “Revenue”, “turnover” and “billed” all find invoices.
Buying and paying
Purchase orders, supplier bills, vendors, quotations, purchase requests, expenses, expense claims, petty cash vouchers and payments.
Stock and assets
Items, assets, asset movements, maintenance work orders and assembly orders.
People and work
Employees, leave, attendance, payroll runs, staff advances, projects, tasks, timesheets, helpdesk tickets and workflow tasks.
Periods it understands
Today, yesterday, this or last week, month, quarter or year, and the last N days.
With AI switched off
When your workspace has switched third-party AI off, or the allowance is used, a rule-based reader handles the common shapes. If it cannot, it says so and opens the builder.
What AWRA OpsHub does today
- Plain-language questions turned into a custom report definition on your existing report datasets.
- The definition shown beside the answer in plain words, with a table of up to 200 rows and a chart where the answer suits one.
- The report engine’s own rules: your permissions, row-level security, the query time limit and your plan’s row cap.
- Field names and types only sent to the AI provider, never a row, and anything unknown refused.
- A rule-based reader for common questions when AI is switched off or unavailable.
- Edit in the report builder and save as a report, plus a history of your questions.
- The same questions from the mobile app, over the API.
More we can add to your workspace
- Follow-up questions that refine the last answer — “now only Nairobi”. Commission it
- Pinning an answer to your dashboard as a tile that refreshes. Commission it
- Explaining a change: why a figure moved between two periods, line by line. Commission it
- Asking from a chat channel such as WhatsApp, Slack or Teams. Commission it
- Questions in Swahili and other languages beside English. Commission it
Where we point you to a specialist
- We will not send your records to an AI provider to answer a question. It sees field names and types, and writes a definition.
- We will not answer beyond the permissions of the person asking. The engine applies them exactly as it does to a report built by hand.
- We will not show an answer without the definition behind it. A figure you cannot check is not an answer.
Follow-up questions and dashboard tiles are the two items people ask for first once they have used it. Tell us the questions your team asks every week and we will come back with a written spec, a timeline and a price.
The reporting it is built on.
Frequently asked questions
What does Ask your data send to the AI provider?
Can it show data a person is not allowed to see?
How do I know the answer counted the right thing?
Does it work with AI switched off?
Can I keep an answer?
Is it in the mobile app?
Help Center
Need a quick answer while you read?
Run inventory, procurement, assets, sales, and field work with approved AWRA guidance for setup, migration, integrations, security, pricing, and support.