NEWEmail, voice, and public reviews - now scored on one comparable scale. See how →
The customer journey

Every step of your customer's journey, mapped and measured.

StatQuestions traces the customer journey from pre-sale to billing — across email, voice, and public reviews — surfacing exactly where friction spikes and which trends are statistically real.

app.statquestions.com · customer journey
Total effort
11,332
Issues
4,133
Routine effort
7,199
Issue rate
36.5%
1,8424.2%issue rate0 issues · 1,842 effort91735.2%issue rate323 issues · 594 effort2,37411.9%issue rate282 issues · 2,092 effort1,40191.1%issue rate1,277 issues · 124 effort2,97429.7%issue rate883 issues · 2,091 effort1,82475.0%issue rate1,368 issues · 456 effort
Pre-Sale / Quoting
Order Management
Logistics & Delivery
Product Experience
Warranty · Service · Returns
Billing & Financial
Total effortIssuesIssue trendWave height = relative volume
630K+
customer messages classified and scored
χ² · p
significance tested on every trend, not assumed
3-in-1
Email, voice, and public reviews on one scale
×7→1
duplicates collapsed into one canonical record
Figures reflect the current production corpus.
American Bath Group
Case study

One intelligence layer across email, voice, and public reviews.

Read our case study

American Bath Group set out to scale customer interactions across a portfolio of brands - converging email, voice, and public reviews with statistical significance, then layering the findings with manufacturing expertise.

Here is how they unified three fragmented channels into one tested, defensible view.

The problem

Counting mentions is not insight.

Most feedback tools tally keywords and call a rise a trend. But a jump from 5 mentions to 7 can be pure chance. StatQuestions tests whether a change is statistically real before you spend a dollar chasing it, then shows you the confidence and the caveats side by side.

Classify

Stop counting mentions. Start classifying.

A hybrid pipeline reads every message and files it into one canonical taxonomy, so the same issue lands in the same place every time.

01

Canonical taxonomy

One agreed structure of issues and sub-issues, enforced at the database layer so it never drifts.

02

Hybrid pipeline

Regex for the obvious, a trained classifier for the rest, and an LLM only where it earns its place.

03

Confidence you can see

First-pass confidence moved from 28% to 52% as the taxonomy tightened. The number is on the screen, not hidden.

Explore Email Intelligence
Classification
message → taxonomy → confidence
RAW EMAIL"Tub arrived with a cracked corner, second damaged unit this month from the same carrier."
Logistics & DeliveryFreight damageL3 · in transit
first-pass confidence0 - 100
was 28%now 52%
Deduplicate

The same complaint, counted once.

One angry customer who emails, calls, and posts is one problem, not three. StatQuestions collapses duplicates into a single canonical record and keeps count of how many collapsed in.

01

Canonical records

Near-identical messages merge into one record with a stable identity you can track over time.

02

Multiplicity kept

Every merge carries a count, so volume stays honest and nothing gets silently dropped.

03

Counts you can defend

Report the real number of distinct issues, not an inflated tally of restated duplicates.

See the Waste Audit
Deduplication
seven duplicates → one canonical record
"Cracked corner, freight damage in transit."
"Second damaged unit this month, same carrier."
"Box crushed on one side again."
"Driver left it curbside, dented panel."
×7 merged
Freight damage in transit
L3 · Logistics & Delivery
6 duplicates removed → 1 canonical record
Prove

Significance shown, not implied.

A control chart tells the difference between normal variation and a real shift. Every trend arrives with a test attached, so you know what deserves action.

01

A test on every trend

χ² and p-values run on the movements that matter, so a spike is labeled real or random.

02

Signal versus noise

Control limits mark the band of normal variation. A point outside it is worth a meeting.

03

Confidence and caveats

Sample size and limitations sit next to every finding, so the claim is only as strong as the data.

Open Causal Analysis
Control chart
freight damage, weekly · UCL breached in wk 9
UCLmeansignal
χ² p<0.001Cramér's V 0.34wk 1–8 n.s.
One scale

Email, voice, and public. One scale.

A complaint in an inbox, on a call, and in a public review is the same complaint. StatQuestions scores all three on one comparable scale so you can rank them together.

01

Comparable by design

Every channel scores 0 to 100 on the same Handle scale, so the numbers actually line up.

02

Voice scored like email

Calls are transcribed and scored on the same rubric, not stranded in a separate tool.

03

Public reviews included

What shows up in the open counts too, weighted alongside private channels.

See Voice Intelligence
One Handle scale
same theme, scored across every channel
VoiceEmailPublic
Freight damage
VOICE
62
EMAIL
58
PUBLIC
71
Missing parts
VOICE
48
EMAIL
51
PUBLIC
44
The platform

One platform, every view.

Six connected modules over the same tested, deduplicated corpus.

Complaint Dashboard

Root-cause view across brands and business units, with significance on every trend.

Causal Analysis

Control charts and χ² tests that separate a real shift from normal variation.

Waste Audit

Find the duplicated, misrouted, and low-value work hiding inside the queue.

Email Intelligence

Classify and score the full inbox corpus, confidence shown on every record.

Voice Intelligence

Calls transcribed and scored on the same Handle scale as email and public.

Decision Catalyst

Turn a tested finding into a ranked, owned next step, not another chart.

StatQ Org Health

Statistical rigor applied to employee experience. Eight dimensions, scored and triangulated.

Security

Enterprise security by design.

Your customers' words are sensitive. StatQuestions handles them with encryption, tight access control, and careful PII treatment.

SOC 2 alignedEncryption in transit & at restPII handling & redactionRole-based access control
From the blog

The thinking behind the numbers.

Field notes on statistical rigor for customer feedback, written for the people who have to act on it.

Read the blog
Statistics · Signal

Most of your complaint trends are noise.

Sample size, significance, and the multiple-comparisons trap, in plain terms for feedback teams.

Get started

See it on your own data.

Bring a slice of your feedback. We will show you which trends are real and which are noise, on the same call.