Compliance-first, not compliance-later

Designed around FCA Consumer Duty from the first line of script

Every call flow is reviewed against the four Consumer Duty outcomes before it ever reaches a borrower — and every call is fully logged, so nothing depends on trusting that it happened.

4
Consumer Duty outcomes enforced in every flow
100%
Of calls recorded, transcribed & logged
<1s
Target voice response latency
24/7
Coverage within permitted calling windows
OUTCOME 1

Products & services

Call flows are matched to the right treatment path for the account type — no one-size-fits-all script applied regardless of circumstance.

OUTCOME 2

Price & value

Where a call touches on fees, charges, or repayment plans, language is reviewed to be clear about cost — nothing buried or rushed through.

OUTCOME 3

Consumer understanding

Scripts are written in plain language, at a measured pace, with confirmation checks — not legalese read quickly to get through a call list.

OUTCOME 4

Consumer support

Any borrower can ask for a human, ask to pause, or flag financial difficulty at any point — and the call adapts immediately, every time.

FCA Consumer Duty
UK GDPR / DPA 2018
CONC & TCF-aligned scripting
Vulnerability detection & escalation
Common questions

What compliance teams usually ask us first

Is every call recorded, and where is that data stored?

Yes — every call is recorded, transcribed, and logged against the account by default, in line with UK GDPR and the Data Protection Act 2018. Retention periods and storage location are configured per client during onboarding to match your own data governance policy.

Can a borrower always reach a human being?

Yes. Any borrower can ask to be transferred to a live agent at any point in the call, and full context passes across with them so they don't have to repeat themselves. This is a hard requirement in every call flow, not an optional setting.

How does vulnerability detection actually work?

The system listens for language and conversational signals associated with financial difficulty or vulnerability during the live call, and escalates accordingly — either adapting the conversation or routing to a human, depending on your configured policy.

Who signs off on the call scripts before they go live?

Your compliance team does. Every flow is presented for review and formal sign-off before it's enabled for outbound calling — Amicorda doesn't push script changes live without that approval step.

Can we produce records for an FCA information request?

Yes — recordings, transcripts, and decision logs are exportable per account or per time period, structured to support internal QA and regulator review alike.

Bring your compliance team to the next call

We'd rather answer the hard questions early than after a pilot's already underway.