ChatKa FAQ

What is ChatKa?

ChatKa is an AI Root-Cause Analyst for Grocery Operations.
It explains why KPIs move by analysing data from your existing data warehouse and returning clear explanations inside Microsoft Teams or Slack.

Who is ChatKa for?

ChatKa is built for:

• online grocers and e-commerce fulfilment,
• supermarket chains with central fulfilment centres (CFCs),
• retailers with complex inbound and outbound operations.

Typical users include Supply Chain Directors, Heads of Online Fulfilment, Heads of Operations, General Managers of CFCs / DCs, and analytics or continuous improvement teams.

What KPIs can ChatKa analyse?

ChatKa is designed for operational KPIs such as:

• Perfect Orders
• On-Time Inbound
• Substitutions (e.g. by category such as chilled / ambient)
• Waste / Shrink
• Service Level / Fill Rate

During a pilot, we typically focus on a small set of high-value KPIs and locations to demonstrate depth of root-cause analysis.

How does ChatKa work with our data?

ChatKa connects to your existing data warehouse with read-only access.

Supported warehouse patterns include:

• Snowflake
• Google BigQuery
• Amazon Redshift
• Teradata
• SQL Server
• Oracle

ChatKa reads the relevant tables, applies your business logic for KPIs, and runs analysis to uncover the drivers of KPI movements. Data remains in your warehouse; ChatKa does not require copying or moving it to a separate store.

Does ChatKa require new dashboards?

No.

ChatKa is not a dashboarding tool. It works alongside your existing BI and reporting tools.

Insights are delivered directly inside Microsoft Teams or Slack, in the form of:

• short explanations,
• root-cause chains (e.g. supplier delays → shortages → substitutions),
• and estimated financial impact.

How long does it take to see value?

The aim is to show clear value in a 4-week pilot.

In that period we typically:

1. Connect to your warehouse with read-only access.
2. Map a small number of KPIs and locations.
3. Analyse recent KPI movements.
4. Deliver repeated root-cause explanations to your operational team inside Teams or Slack.

The goal is to reduce the time spent on manual investigation and give leaders a clearer view of what is driving KPI changes.

How is ChatKa different from conversational BI tools?

Conversational BI tools primarily:

• translate natural language questions into SQL,
• and return charts or tables.

ChatKa focuses specifically on root-cause analysis for operational KPIs. It does not aim to answer every possible data question, but to go deep on:

• why a KPI moved,
• what chain of events caused it,
• and what the financial or service impact was.

Does ChatKa train on our data?

ChatKa is designed so that:

• your operational data stays within your warehouse,
• and analysis is scoped to your environment.

Details of data handling, retention, and model usage are agreed as part of the pilot and depend on your internal policies and preferred cloud setup.

Which collaboration tools does ChatKa support?

ChatKa delivers insights inside:

• Microsoft Teams
• Slack

so operational teams can read and act on explanations where they already work.

How do we start a pilot?

If you are interested in a pilot, the simplest next step is to book an intro call from the homepage or contact us via the listed email.

We typically start with one or two fulfilment centres or regions and a focused set of KPIs.