Veridict
← Conversations

call · Meridian Telecom

Priya Raman

conv-0013 · 22 Jul 2026, 10:00 am · 9m 44s · en

NRIC breachHeld steady 0.0AUTO-FAIL

Auto-fail — score zeroed

NRIC was used as an authentication factor. Singapore's PDPC prohibits this from 1 January 2027. This conversation is counted as a compliance finding regardless of its other criteria.

Customer sentiment

0.0Held steady
opened -1.0closed -1.0

Sentiment was broadly unchanged across the call.

Agent tone (avg)0.0
Customer tone (avg)-1.0
goodflatbad#1 customer — frustrated#3 customer — frustrated#0 agent — warm#2 agent — professional#4 agent — dismissive#5 agent — warm#6 agent — professionallowest
CustomerAgentTurn order, left to right

Tone is judged from the redacted transcript — wording and what each speaker is reacting to. No voice biometrics, no emotion inference from audio.

Transcript

Needs attention
0:00 / 9:44

Click a flagged moment above, or a red region, to replay just that part.

Simulated playback — synthetic conversation, no audio
agent#00:00warm

Good morning, thank you for calling, my name is NAME. How may I help you today?

customer#12:17frustrated

My service has been down since Tuesday.

agent#23:23

Could you confirm your NAME number for me?

customer#34:35frustrated

It is NRIC.

agent#45:09dismissive

That is just how the billing cycle works.

agent#56:20warm

The duplicate charge is reversed — you will see the credit within three working days.

agent#68:45

Anything else before I let you go?

Chips mark personal data removed before this conversation was stored. The original values were never written to disk — only the counts were kept.

Scorecard

Meridian Telecom — Standard QA v3 — click a criterion to highlight its evidence.

Redaction summary

NRIC × 1PHONE × 1

Counts are retained as the compliance signal; values are not.