AI agentReporting for customer-flow operations

Ask your branch data a question. Get an answer you can defend.

Nexia plans the query, shows you the SQL, dry-runs it against your database before anything executes, and hands back the report. No ticket to the BI team.

Book a 20-minute demo Sign in to workspace

Connects to your existing Wavetec queue, counter and footfall data — no new instrumentation.

Nothing executes before a dry run — and reporting SQL that starts with DDL is rejected.

Runs in your cloud, your data centre, or ours.

Nexia · Retail Banking workspaceConnected

Your question

01 · reading schemabranchesticketscountersservice_types

report.sqlplanfilters

-- generated by Nexia · dry-run before executionSELECT b.branch_name,       ROUND(AVG(t.wait_seconds) / 60.0, 1) AS avg_wait_min,       SUM(CASE WHEN t.wait_seconds > 600 THEN 1 ELSE 0 END)         * 100.0 / COUNT(*) AS pct_breachedFROM   tickets tJOIN   branches b ON b.id = t.branch_idWHERE  t.served_at >= DATEADD(day, -7, CAST(GETDATE() AS date))  AND    b.region = 'South'GROUP BY b.branch_nameORDER BY pct_breached DESC;

Dry run passed SELECT only · no DDLCompile 42 msRow filters · Region: South

Breached 10-min SLA · last 7 days5 branches

Branch	Avg wait	Breached
Saddar	14.8m	31.2%
Korangi	12.1m	24.6%
Gulshan	10.4m	18.0%
Clifton	7.9m	6.3%
DHA Phase II	6.2m	4.1%

Sample workspace · your data stays in your tenant

The agent

It works like an analyst, and it shows the working.

Nexia is a conversation, not a search box. Ask, narrow it down, change your mind — every step it takes is on screen, so you can follow the reasoning to the number.

Compare wait times across South-region branches this month against last month, and flag anything over the 10-minute SLA.

Three of the fourteen South-region branches are above the SLA. Saddar is the largest contributor at 14.8 minutes average and 31.2% of tickets breaching — but it is also the only branch that improved week-on-week.

Resolved 14 branches in Region: South
Matched KPIs avg wait · SLA breach % · abandonment
Dry run passed in 42 ms · no DDL
Compared 2 periods × 8 weeks

Pin that as a dashboard for the regional review.

Building South Region — SLA Review with four widgets: the trend, the branch ranking, the breach rate and the abandonment tile.

Created dashboard · 4 widgets
Applying shared filters · date range, region

It asks before it guesses

If “last quarter” or “the new flow” is ambiguous, Nexia comes back with a short clarifying question instead of quietly picking an interpretation.

Every step is inspectable

Resolved entities, matched KPIs, the generated SQL and the dry-run result are all attached to the answer — not hidden behind it.

Follow-ups keep the context

“Now just the wealth counters” re-runs the same analysis with one more filter, instead of starting the conversation again.

Analysis & dashboards

Pin the answers you keep asking for.

Any answer becomes a widget. Arrange widgets into a dashboard for a region, a business line or the Monday review — one shared filter bar drives all of them.

South Region — SLA ReviewLast 8 weeksRegion: SouthAll services

Tickets served0+8.2%

Average wait6.2m−37%

Within 10-min SLA0.4%+3.1pt

Abandonment4.7%+0.6pt

Average wait per week

minutes

This monthLast month10-minute SLA

By branch, last 7 days

minutes

Every widget keeps the SQL that produced it — open it, copy it, or export the underlying rows.

The Nexia engine

One engine between your operational data and a number you can sign off.

Nexia reads the systems Wavetec already runs on your floor, plans the query, dry-runs it, and only then gives you the answer.

Your Wavetec data

What you get

Queue ticketstickets · tokens · waits

Countersagents · services

Footfallentries · dwell

Appointmentsbooked · no-shows

Nexia engine

Plans the queryGenerates SQLDry-runs it first

Reportwith its SQL attached

Dashboardpinned · shared filters

ExportCSV · Excel · PDF

~0sFrom question to validated report

0%Of queries dry-run before execution

0 DDLCREATE / ALTER / DROP is rejected

1 clickTo the SQL behind any figure

The honest comparison

You already have three ways to get this number.

Here is what each one actually costs you, and where Nexia sits.

Option one

Export to Excel

Stale the moment it lands in your inbox
Every branch rebuilds the same pivot differently
Nobody can trace where the number came from
Customer data now lives on twelve laptops

Option two

Paste your schema into a chatbot

Guesses at joins it has never seen
No validation — a wrong number looks like a right one
Your table structure leaves the building
Someone still has to run the query by hand

Option three

Nexia

Works off a knowledge base synced from your own schema
Re-sync is one click, and it is instant
Shows the SQL — hand it to your DBA before you trust it
Dry-run validated before anything executes

How it works

Three steps, and you can audit all of them.

The order matters — nothing runs against your database until the query has compiled cleanly.

01 · ASK

Describe the report

Plain English, your own vocabulary. Nexia maps it to your branches, counters, services and SLAs — then shows you the plan it intends to run.

02 · CHECK

Read the SQL, not the summary

The generated query is on screen and one click from your clipboard. It is dry-run first, so a query that would not compile never gets executed.

03 · SHIP

Filter, pin, send

Change the date range, region or branch and re-run in place. Pin it to a dashboard, or export to Excel, CSV or PDF for the Monday review.

Capabilities

Built for the people who own the service floor.

Shipped today, plus what's next — labelled honestly.

Plain English to SQL

Tuned to queue-management tables, not generic. Understands tickets, tokens, counters, service types, no-shows and abandonment.

A knowledge base of your schema

Nexia syncs your own tables, columns and KPI definitions into a knowledge base it reasons over. Re-syncing after a schema change is one click, and it is instant.

An agent, not a search box

It asks a clarifying question when your request is ambiguous, then shows every step it took to reach the number.

Dry-run validation

Every generated query is dry-run against your SQL Server before it executes. Failures come back as sentences, not stack traces.

Live filters

Date, region, branch, counter, service. Adjust and re-run without rewriting the question.

Custom dashboards

Pin any answer as a widget, then drag, resize and arrange a dashboard for a region or a business line — trends get lines, comparisons get bars, single numbers get a tile.

Templates & report builder

Start from a library of standard operations reports, or build and save your own for the whole team to reuse.

Exports

CSV, Excel and PDF, formatted for circulation rather than for a database client.

Scheduled deliveryPlanned

Send a saved report to a distribution list every Monday at 08:00, or when an SLA threshold is breached.

Use cases

The questions people actually ask on a Monday morning.

Head of Branch OperationsBanking workspace

Which branches missed the 10-minute wait SLA last week, and which counters caused it?

Nexia answered

3branches over SLA14.8mworst average wait31.2%tickets breached

5 branches · 42 ms · dry-run passed

Also asked by this team

01Teller utilisation by hour against staffing roster
02Abandonment rate before and after the new token flow
03Wealth vs retail service times in the same branch
04Branch ranking for the monthly performance review

Each one is a saved report in the same workspace — no new build, no new ticket.

Security & control

Two questions your risk team will ask first.

Can it break something, and can it invent a number? Both answers are architectural, not aspirational.

Reporting queries are SELECT-only

Generated reporting SQL is checked before it runs: a batch beginning CREATE, ALTER, DROP or TRUNCATE is rejected rather than executed.

Nothing runs before a dry run

Each query is first sent to your SQL Server under SET NOEXEC ON, which compiles and validates it without executing it. Only a query that survives that pass is allowed to run for real.

Every number has a visible source

The SQL behind any figure is on screen and one click from your clipboard. If a report goes to a regulator or a board, someone can reproduce it without Nexia in the room.

Deploy where your data lives

Wavetec cloud, your own VPC, or fully on-premise for institutions that cannot send branch data outside the country. Model calls can be routed to a private endpoint.

Access mirrors your org chart

Row-level filters are applied before the query runs, not after the results come back. Users cannot ask their way around a permission.

Full audit trail

Questions, generated SQL, execution results and exports are logged per user and retained to your policy. Available to your SIEM.

Compliance documentation, DPA and penetration-test summary available under NDA — request the security pack.

Behind Nexia

Wavetec has been counting these queues for thirty years.

Nexia is built by Wavetec, whose queue management, digital signage and customer-experience systems run in banks, telecom stores, government service centres and hospitals worldwide. The reporting layer knows the data because the same company built the systems that produce it.

0+Years in customer-flow systems

0+Countries with Wavetec deployments

0Sectors served: banking, telecom, government, healthcare

Get started

Two ways in.

New to Nexia

Twenty minutes, your questions run against a sample workspace. Bring the report your team argues about most.

Book a demo

Already have a workspace

AI agentReporting for customer-flow operations

Ask your branch data a question. Get an answer you can defend.

Nexia plans the query, shows you the SQL, dry-runs it against your database before anything executes, and hands back the report. No ticket to the BI team.

Book a 20-minute demo Sign in to workspace

Connects to your existing Wavetec queue, counter and footfall data — no new instrumentation.

Nothing executes before a dry run — and reporting SQL that starts with DDL is rejected.

Runs in your cloud, your data centre, or ours.

Nexia · Retail Banking workspaceConnected

Your question

01 · reading schemabranchesticketscountersservice_types

report.sqlplanfilters

-- generated by Nexia · dry-run before executionSELECT b.branch_name,       ROUND(AVG(t.wait_seconds) / 60.0, 1) AS avg_wait_min,       SUM(CASE WHEN t.wait_seconds > 600 THEN 1 ELSE 0 END)         * 100.0 / COUNT(*) AS pct_breachedFROM   tickets tJOIN   branches b ON b.id = t.branch_idWHERE  t.served_at >= DATEADD(day, -7, CAST(GETDATE() AS date))  AND    b.region = 'South'GROUP BY b.branch_nameORDER BY pct_breached DESC;

Dry run passed SELECT only · no DDLCompile 42 msRow filters · Region: South

Breached 10-min SLA · last 7 days5 branches

Branch	Avg wait	Breached
Saddar	14.8m	31.2%
Korangi	12.1m	24.6%
Gulshan	10.4m	18.0%
Clifton	7.9m	6.3%
DHA Phase II	6.2m	4.1%

Sample workspace · your data stays in your tenant

The agent

It works like an analyst, and it shows the working.

Nexia is a conversation, not a search box. Ask, narrow it down, change your mind — every step it takes is on screen, so you can follow the reasoning to the number.

Compare wait times across South-region branches this month against last month, and flag anything over the 10-minute SLA.

Resolved 14 branches in Region: South
Matched KPIs avg wait · SLA breach % · abandonment
Dry run passed in 42 ms · no DDL
Compared 2 periods × 8 weeks

Pin that as a dashboard for the regional review.

Building South Region — SLA Review with four widgets: the trend, the branch ranking, the breach rate and the abandonment tile.

Created dashboard · 4 widgets
Applying shared filters · date range, region

It asks before it guesses

If “last quarter” or “the new flow” is ambiguous, Nexia comes back with a short clarifying question instead of quietly picking an interpretation.

Every step is inspectable

Resolved entities, matched KPIs, the generated SQL and the dry-run result are all attached to the answer — not hidden behind it.

Follow-ups keep the context

“Now just the wealth counters” re-runs the same analysis with one more filter, instead of starting the conversation again.

Analysis & dashboards

Pin the answers you keep asking for.

Any answer becomes a widget. Arrange widgets into a dashboard for a region, a business line or the Monday review — one shared filter bar drives all of them.

South Region — SLA ReviewLast 8 weeksRegion: SouthAll services

Tickets served0+8.2%

Average wait6.2m−37%

Within 10-min SLA0.4%+3.1pt

Abandonment4.7%+0.6pt

Average wait per week

minutes

This monthLast month10-minute SLA

By branch, last 7 days

minutes

Every widget keeps the SQL that produced it — open it, copy it, or export the underlying rows.

The Nexia engine

One engine between your operational data and a number you can sign off.

Nexia reads the systems Wavetec already runs on your floor, plans the query, dry-runs it, and only then gives you the answer.

Your Wavetec data

What you get

Queue ticketstickets · tokens · waits

Countersagents · services

Footfallentries · dwell

Appointmentsbooked · no-shows

Nexia engine

Plans the queryGenerates SQLDry-runs it first

Reportwith its SQL attached

Dashboardpinned · shared filters

ExportCSV · Excel · PDF

~0sFrom question to validated report

0%Of queries dry-run before execution

0 DDLCREATE / ALTER / DROP is rejected

1 clickTo the SQL behind any figure

The honest comparison

You already have three ways to get this number.

Here is what each one actually costs you, and where Nexia sits.

Option one

Export to Excel

Stale the moment it lands in your inbox
Every branch rebuilds the same pivot differently
Nobody can trace where the number came from
Customer data now lives on twelve laptops

Option two

Paste your schema into a chatbot

Guesses at joins it has never seen
No validation — a wrong number looks like a right one
Your table structure leaves the building
Someone still has to run the query by hand

Option three

Nexia

Works off a knowledge base synced from your own schema
Re-sync is one click, and it is instant
Shows the SQL — hand it to your DBA before you trust it
Dry-run validated before anything executes

How it works

Three steps, and you can audit all of them.

The order matters — nothing runs against your database until the query has compiled cleanly.

01 · ASK

Describe the report

Plain English, your own vocabulary. Nexia maps it to your branches, counters, services and SLAs — then shows you the plan it intends to run.

02 · CHECK

Read the SQL, not the summary

The generated query is on screen and one click from your clipboard. It is dry-run first, so a query that would not compile never gets executed.

03 · SHIP

Filter, pin, send

Change the date range, region or branch and re-run in place. Pin it to a dashboard, or export to Excel, CSV or PDF for the Monday review.

Capabilities

Built for the people who own the service floor.

Shipped today, plus what's next — labelled honestly.

Plain English to SQL

Tuned to queue-management tables, not generic. Understands tickets, tokens, counters, service types, no-shows and abandonment.

A knowledge base of your schema

Nexia syncs your own tables, columns and KPI definitions into a knowledge base it reasons over. Re-syncing after a schema change is one click, and it is instant.

An agent, not a search box

It asks a clarifying question when your request is ambiguous, then shows every step it took to reach the number.

Dry-run validation

Every generated query is dry-run against your SQL Server before it executes. Failures come back as sentences, not stack traces.

Live filters

Date, region, branch, counter, service. Adjust and re-run without rewriting the question.

Custom dashboards

Pin any answer as a widget, then drag, resize and arrange a dashboard for a region or a business line — trends get lines, comparisons get bars, single numbers get a tile.

Templates & report builder

Start from a library of standard operations reports, or build and save your own for the whole team to reuse.

Exports

CSV, Excel and PDF, formatted for circulation rather than for a database client.

Scheduled deliveryPlanned

Send a saved report to a distribution list every Monday at 08:00, or when an SLA threshold is breached.

Use cases

The questions people actually ask on a Monday morning.

Head of Branch OperationsBanking workspace

Which branches missed the 10-minute wait SLA last week, and which counters caused it?

Nexia answered

3branches over SLA14.8mworst average wait31.2%tickets breached

5 branches · 42 ms · dry-run passed

Also asked by this team

01Teller utilisation by hour against staffing roster
02Abandonment rate before and after the new token flow
03Wealth vs retail service times in the same branch
04Branch ranking for the monthly performance review

Each one is a saved report in the same workspace — no new build, no new ticket.

Security & control

Two questions your risk team will ask first.

Can it break something, and can it invent a number? Both answers are architectural, not aspirational.

Reporting queries are SELECT-only

Generated reporting SQL is checked before it runs: a batch beginning CREATE, ALTER, DROP or TRUNCATE is rejected rather than executed.

Nothing runs before a dry run

Each query is first sent to your SQL Server under SET NOEXEC ON, which compiles and validates it without executing it. Only a query that survives that pass is allowed to run for real.

Every number has a visible source

The SQL behind any figure is on screen and one click from your clipboard. If a report goes to a regulator or a board, someone can reproduce it without Nexia in the room.

Deploy where your data lives

Wavetec cloud, your own VPC, or fully on-premise for institutions that cannot send branch data outside the country. Model calls can be routed to a private endpoint.

Access mirrors your org chart

Row-level filters are applied before the query runs, not after the results come back. Users cannot ask their way around a permission.

Full audit trail

Questions, generated SQL, execution results and exports are logged per user and retained to your policy. Available to your SIEM.

Compliance documentation, DPA and penetration-test summary available under NDA — request the security pack.

Behind Nexia

Wavetec has been counting these queues for thirty years.

0+Years in customer-flow systems

0+Countries with Wavetec deployments

0Sectors served: banking, telecom, government, healthcare

Get started

Two ways in.

New to Nexia

Twenty minutes, your questions run against a sample workspace. Bring the report your team argues about most.

Book a demo