TotalApp Docs

AI Assistants Overview

Two families of contextual AI Assistant — one built for acting on table rows, one built for interpreting dashboard metrics — both powered by the same Agentic writer-engine settings.

What is AI Assistant?

TotalApp gives almost every screen its own AI Assistant — a contextual panel that understands the data on that specific screen and can act on it or explain it in plain English. Rather than one generic chatbot bolted onto the app, there are two purpose-built families, each shaped for the kind of screen it lives on.

Every AI Assistant, regardless of family, is powered by the same underlying Agentic configuration (see Agentic → Overview) — the Writer Engine you choose in Settings (Ollama, In-Browser/WebGPU, or Cloud LLM) is what actually answers the assistant's requests. This is why every AI Assistant in TotalApp respects your chosen engine instead of silently calling a cloud API: the client-side code checks the active Writer Engine before making any request, so switching to a fully local or in-browser engine keeps every assistant working without a single behavior change.

The core split

Table/List screens get an assistant built for row-level action. Dashboard screens get an assistant built for metric-level insight. Same underlying AI, two very different jobs.

Screen preview

A quick look at the screens. Use the toggle in the corner of each preview to switch between the dark and light themes.

app.totalapp.app/ai-assistant
Summarise our Q2 HR report and highlight risks
Q2 HR Summary:
— Headcount grew 12% to 48 employees
— Turnover rate: 8.3% (— from 6.1% in Q1)
— —— Risk: 3 senior roles open >60 days
— Leave utilisation: 71% of annual budget used
Create a workflow to auto-notify managers
Generating workflow—
Ask anything about your business data—
—

Native AI assistant

app.totalapp.app/fleet/vehicles
Fleet Logistics
Vehicle Registry
12
Available
8
In Use
1
Expiring
Filter
PlateDriverStatus
34 KF 919
Expiring
06 TA 271
Active
35 ZC 044
Active
AI Assistant
1 vehicle(s) selected as context
✕
Try Asking
Which vehicles have expiring documents?
How is the fleet being utilized right now?
Ask about vehicles, expirations...

The native AI Assistant panel with screen context

AI Assistants Across TotalApp (8 screens)
AI Assistant
Embedded intelligence for your workflow
Analyze our top 5 opportunities by probability and value.
Top 5 Opportunities
1. Acme Corp — $240K (85% prob) · active 2d
2. TechStart Inc — $180K (62% prob) · quiet 14d
3. Global Ltd — $320K (78% prob) · active 1d
4. Northwind Group — $95K (54% prob) · active 5d
5. Bluepeak Retail — $150K (48% prob) · quiet 9d
⚠️ TechStart shows low recent activity—recommend outreach.
Draft a follow-up email to TechStart.
Draft ready — references the 14-day gap, proposes a 20-minute call this week, and attaches the security overview they requested.

Embedded AI Assistants across eight domain screens

Table Assistants vs. Dashboard Assistants

Aspect Table & List Assistants Dashboard Assistants (Insight Generator)
Where it appears Any table/list screen — Asset Registry, My Projects, Purchase Orders, Employees, and more Chart-heavy dashboard screens — starting with the MTBF/MTTR Reliability Dashboard
What it does Acts on the rows in front of you — selects, edits, cleans up, filters, summarizes, converts Reads the charts for you — summarizes metrics, explains trends, recommends next steps
Example action "Set status to Approved for these 5 records and create a work order" "MTTR spiked in Q3 — driven mostly by the Boiler System H8 asset group"
Output shape Bulk edits, filtered views, exported files, inline suggestions Executive summary, root-cause explanation, actionable recommendation

One Shared Panel, Everywhere

Every assistant in TotalApp is built on the same panel, so what you learn on one screen works on all of them. The panel follows your AI Assistant settings — width, font size, history depth, suggestion chips — and takes its accent colour from the module you are in. Every panel has the same controls: suggestion chips on an empty chat, chat history and New Chat, full-screen mode, Save as Report and Add Knowledge.

Select rows, then ask

On table screens, tick the checkbox at the start of any rows. The panel lists them under Selected (n) and offers Analyze selected and Summarize selected — one click sends the ticked records to the assistant with a ready-made prompt. If you type your own question instead, the selected rows are used as its context. With nothing ticked, the assistant looks at the whole list. The checkbox look (shape, colour, size) is set in Settings → Appearance.

Learn More

Table & List Assistants

Multi-select bulk actions, data cleanup, natural-language filtering, quick summarization, and inline smart suggestions on every table screen.

Dashboard Assistants (Insight Generator)

Natural-language executive summaries, root-cause and anomaly detection, and actionable recommendations for every chart-heavy dashboard.

Dashboard Assistants Are Arriving Now

Table/List Assistants already exist across many screens today. Dashboard Assistants — the Insight Generator — are the newest addition to this family, rolling out across TotalApp's chart-heavy dashboards starting with the MTBF/MTTR Reliability Dashboard in Maintenance Operations, with the Manufacturing OEE Dashboard and other analytics screens close behind.

Same concept, screen by screen

Because every Dashboard Assistant is scoped to its own dashboard's own screen and data, rolling it out to a new dashboard is a matter of wiring up that screen's metrics — not building a new AI concept from scratch.

Frequently Asked Questions

How do I know which type of AI Assistant a screen has?
Table and list screens (Asset Registry, My Projects, Purchase Orders, etc.) show a Table & List Assistant. Chart-heavy dashboard screens (starting with the MTBF/MTTR Reliability Dashboard) show a Dashboard Assistant. The panel itself is always labeled and scoped to the screen you're on — you never have to pick a type manually.
Do I need an API key to use AI Assistants?
No. AI Assistants work with whichever Writer Engine you've selected in Settings → Agentic — Ollama, In-Browser (ONNX/WebGPU), or Cloud LLM. If you choose a fully local or in-browser engine, no API key or cloud call is required at all.
Why does my AI Assistant behave differently after I change the Writer Engine?
Every AI Assistant checks the active Writer Engine before each request, so switching engines in Settings → Agentic changes response speed and style immediately — no separate per-screen configuration is needed.
Will every screen eventually get an AI Assistant?
Table/List Assistants already cover most table screens today. Dashboard Assistants are rolling out screen by screen, since each one is wired to that dashboard's specific metrics — new dashboards are added to the rollout regularly.
Is my data sent anywhere when I use an AI Assistant?
That depends entirely on your chosen Writer Engine. Ollama and In-Browser engines process everything on your own machine; Cloud LLM sends the relevant screen data to the configured provider. See Agentic → Overview for details on each engine.