Customer Intelligence for multi-site networks

Every customer conversation,
turned into a case with an owner

We run the channels your customers talk on and read every conversation into cases your network can act on — each carrying the sentence behind it. Automotive dealer networks are where it runs today.

Book a 30-min walkthrough

Official Partner of

Empowered by

Aalto University

The opportunity

Your network already knows
what is about to go wrong.

What leadership cannot answer today

Which customers need attention right now.
Who missed the follow-up, and at which location.
Where the revenue starts leaking away.

Example — one vertical. A dealer network is where this is easiest to show; the loop itself is not automotive.

Close-up of a dark crescent-shaped casting mark on a light automotive trim piece. — Example — one vertical. A dealer network is where this is easiest to show; the loop itself is not automotive.

The future of network performance is not more communication. It is control over what communication already reveals.

What it answers

The pattern no single case can show.

Every case closes with the customer it belongs to. What it leaves behind is a fact about the outlet that produced it — and the layer holds those facts for every outlet at once.

Example — the outlets are illustrative. What the layer reports is the kind of finding, not a score.

What we deliver

We supply the conversations,
not only what we read out of them.

Channels we run

Running today

Outbound as well as inbound, on lines we operate — not a listener attached to yours.

WhatsApp

out Templates go out

in Replies come back — voice notes, photos and documents

AI voice bot

out Places the call

in Answers it, in the language the customer chose

Direct call

out One click from the open case to the customer

in A way back to your team from the web

Also captured

Email Feedback forms Photos & media Dealer notes Social — Meta DMS / CRM records Car software
Airfra

Running today

Read from every conversation
- Transcript
- Summary
- Issue type
- Urgency
- Next action
- Language
Sentiment

negative neutral positive How the customer actually felt, read from what was said — not from a survey they never filled in.

PSF & NPS

0–6 detractor 7–8 passive 9–10 promoter NPS 0–10 · PSF 1–10 Whether they come back. A weak score is an early signal of churn — and of the location that keeps producing them.
The system it lands in

Ready to connect

What your systems receive
- Cases
- Tasks
- Alerts
- Reports
- Approvals
- Location scorecards
- BI dashboards
- CRM / DMS updates
- Audit trail
Every output above already exists. Wiring it into the system you already run is our work, not a project on your side.

Today

Our own case system: cases, escalations, team tasks and analytics in one place.

On request

No system of your own, or one that does not fit — we assemble it. CRM and ERP follow the same path.

Ahead

The loop run the other way — a service coming due, a policy about to expire, a customer nobody has spoken to since delivery. Built with the first network that asks for it.

Use cases

What it catches
in an ordinary week.

Ten scenarios

Drag or scroll

Delivery slips

WhatsApp

The date moves and nobody calls. The next message says so, and a case opens with an owner on it.
Handover complaints

WhatsApp

What went wrong at collection, classified and routed before a survey would have gone out.
Silent customers

WhatsApp · no reply

Someone who stops replying is a signal, not an absence.
Calls both ways

Direct call

Outbound from the case, inbound from the web — the same transcript either way.
Detractors, same day

NPS / PSF

A weak score reaches the person who can still act, while the customer is in the loop.
Escalation with a name

Escalation rules

Not a shared inbox: a state, a named manager and a time on every step.
Photo of the fault

Photos

A customer photographs what is wrong instead of describing it. The image is read with the message, not filed as an attachment nobody opens.
The form that goes somewhere

Feedback form

A feedback answer lands on the case it belongs to while that case is still open, instead of in a monthly export.
Email is the same conversation

Email

A complaint arrives by email in the middle of a thread that started on WhatsApp. Both are one history, read the same way.
What the adviser wrote down

Dealer notes

The note typed into the dealer system reads as part of the case, not as a field the network never sees.

Unique edge

Bots are easy to copy.
Workflow memory is not.

Anyone can put a bot on WhatsApp in a week. What nobody can start with is what a deployment leaves behind: playbooks for the requests your network actually gets, classification logic tuned to your categories rather than a generic set, and escalation paths with your own owners on them. Every rollout adds to all three, and none of it transfers.

How you check it

Every verdict comes with
the sentence that caused it.

Examples — three conversations from a dealer network, on three different channels

Airfra bot

Your service booking is confirmed for Friday, 14:00. We will message you when the car is ready.
customer · voice note

“They told me the car would be ready on Friday. Nobody called. I found out on Monday, when I drove over myself.”

The sentence the classifier quoted back as its evidence.

Issue: Delivery Delay one of 42
Sentiment: Negative
Urgency: High
PSF: 3 of 10
NPS: 4 detractor, 0–6
Flags: Callback requested, action required

Phone call

customer · inbound call

“The car was ready on time. Nobody explained what was actually done to it.”

Issue: Unresolved Query one of 42
Sentiment: Neutral
NPS: 7 passive, 7–8
Next action: Human callback within SLA

Web form

customer · web form

“The handover took ten minutes and everything was explained. Best dealer experience I have had.”

Issue: Positive Experience one of 42
Sentiment: Positive
NPS: 9 promoter, 9–10
PSF: 9 of 10

Stored with: The quote it relied on, a confidence score, and the version of the model that produced it.
Attached to: The customer, the outlet, the salesperson and the vehicle the case is about.
Logged after: Every write that follows — who made it, from which value to which, and when.

The categories are the trade's own words, not abstractions — Delivery Delay, Late Handover, PDI Issue, Variant Mismatch, Registration Issue, Spare Parts, Warranty. Forty-two in all, and the classifier picks exactly one.

Who sees what

Everyone works in the same system.
Nobody sees the same thing.

In an automotive network that is the OEM and its dealers.

Head office sees

8842 · Turku · escalated
8851 · Monterrey · follow-up missed
8860 · Nagoya · resolved
8864 · Rotterdam · escalated
8871 · Bristol · resolved

Turku sees

8842 · Turku · escalated

Nothing from the other thirteen outlets — not their cases, and not their scores.

The boundary is not a switch in the interface — a view that is not allowed cannot be reached by editing the address bar. What enforces it on the server is in Security & control .

Who it is for

Built for leaders answerable for
customers other people serve.

If the people talking to your customers are not on your payroll — dealers, franchisees, importers, partner outlets — the conversation is where your visibility ends. Closing that gap should not cost those teams another portal to log into.

Where it runs

Automotive dealer networks

Running today

The same shape fits

Importers and national distributors
Franchise and multi-site service operations
Enterprise field and branch networks
Airline and passenger service networks
Industrial groups with field service
Manufacturers selling through partners
CRM, DMS and CX providers

We want to speak with

Chief Customer Officer
Head of Network Operations
Head of Customer Experience
Head of Aftersales
Head of Sales Operations
Head of Digital Transformation
CRM / DMS Product Owner
Regional Performance Director
Enterprise Innovation / AI Lead

Security & control

Who can reach what,
and where that gets decided.

Access: Three roles — head office, location admin, location agent. Accounts are invited from the head office rather than self-registered, and the first sign-in forces a password change.
Sessions: The session token carries the role and the location it belongs to, and every request is checked against it on the server before a row is returned.
Isolation: Not one interface with rows hidden from some accounts. The location side is its own build, with the scope written into the query behind it.
Channel keys: Credentials for WhatsApp and the calling platform stay server-side. Nothing that can send a message in your name is ever held in a browser.
Where it runs: Your own infrastructure by default: the layer is deployed on your servers, and the data never leaves them. Hosted with us on request — EU region on Microsoft Azure, a static front end, a serverless API and a managed SQL database.
Compliance: GDPR-aligned by design, contractual DPA, and EU data residency wherever we host.

Frequently asked

Before the first call

Is this a chatbot?

No. Chat and voice are channels we run; the product is the layer that reads every conversation and turns it into a case with an owner. A bot answering questions is one part of that, not the whole of it.

Do we have to replace our DMS or CRM?

No. We integrate with what you already run — through an API where there is one, by driving the interface where there is not. We only assemble a system if you have none, or the one you have does not fit.

What happens to conversations that are not in English?

Language belongs to the customer, not to a message or a setting. Transcription, classification and the reply all stay in the language that customer uses.

Can we check why the AI decided something?

Yes. Every classification is stored with the sentence it relied on, a confidence score and the version of the model that produced it, so a verdict can be taken back to the conversation it came from.

Pilot package

Start with one region.
Scale on what it finds.

We listen

What you already run, what you want to see, and how you want to try it. The scope is yours to name, not ours to propose.
Pilot on your scope

Day 0 — whatever you named: a market, a dealer group, an aftersales workflow. On the channels those locations already use.
Modifications

A report every week, and the classification and escalation rules change with what it finds.
Live

Day 30–60 — an integration plan for the systems you run, and a rollout plan for the rest of the network.

See what your customers are already telling you

Give us one workflow, one region or one communication channel — we will show how much hidden intelligence already exists inside your customer conversations.

Book a Demo Email Igor

Built for multi-site networks
CRM / DMS ecosystems
EU data residency
GDPR-aligned

Choose language

Every customer conversation,
turned into a case with an owner

Your network already knows
what is about to go wrong.

The pattern no single case can show.

Repeat, not incident Turku

Follow-up that never came Monterrey

One outlet pulling away Nagoya

Where it starts costing

We supply the conversations,
not only what we read out of them.

Channels we run

Airfra

The system it lands in

What it catches
in an ordinary week.

Delivery slips

Handover complaints

Silent customers

Calls both ways

Detractors, same day

Escalation with a name

Photo of the fault

The form that goes somewhere

Email is the same conversation

What the adviser wrote down

Bots are easy to copy.
Workflow memory is not.

Every verdict comes with
the sentence that caused it.

Everyone works in the same system.
Nobody sees the same thing.

Head office sees

Turku sees

Built for leaders answerable for
customers other people serve.

Who can reach what,
and where that gets decided.

Before the first call

Start with one region.
Scale on what it finds.

See what your customers are already telling you

Every customer conversation, turned into a case with an owner

Your network already knows what is about to go wrong.

The pattern no single case can show.

Repeat, not incident Turku

Follow-up that never came Monterrey

One outlet pulling away Nagoya

Where it starts costing

We supply the conversations, not only what we read out of them.

Channels we run

Airfra

The system it lands in

What it catches in an ordinary week.

Delivery slips

Handover complaints

Silent customers

Calls both ways

Detractors, same day

Escalation with a name

Photo of the fault

The form that goes somewhere

Email is the same conversation

What the adviser wrote down

Bots are easy to copy. Workflow memory is not.

Every verdict comes with the sentence that caused it.

Everyone works in the same system. Nobody sees the same thing.

Head office sees

Turku sees

Built for leaders answerable for customers other people serve.

Who can reach what, and where that gets decided.

Before the first call

Start with one region. Scale on what it finds.

See what your customers are already telling you

Every customer conversation,
turned into a case with an owner

Your network already knows
what is about to go wrong.

We supply the conversations,
not only what we read out of them.

What it catches
in an ordinary week.

Bots are easy to copy.
Workflow memory is not.

Every verdict comes with
the sentence that caused it.

Everyone works in the same system.
Nobody sees the same thing.

Built for leaders answerable for
customers other people serve.

Who can reach what,
and where that gets decided.

Start with one region.
Scale on what it finds.