Architecture

Deterministic where it must be. Generative where it pays.

Most AI collection tools hand the whole process to a language model and hope. Ayra splits it in two. The model never decides who gets contacted, how often, or what the record says.

Deterministic layer

Rules decide. Not the model.

Who enters treatment, when each contact fires, which channel is used, how many attempts are allowed, when quiet hours apply, when a case stops. Rule-driven, inspectable, identical every run.

  • Contact strategy and frequency caps
  • Quiet hours and consent enforcement
  • Negotiation limits you approved
  • Escalation triggers and stop conditions
  • The record written back to your system
Generative layer

The model reasons. It never executes.

Inside those rails the model does what it is genuinely better at than a script: reading the situation. It interprets intent, recognises a dispute, extracts what matters and decides what to say — but every action it can actually take is one the rules already authorised.

  • Natural conversation across voice and text
  • Objection handling and intent detection
  • Language switching mid-conversation
  • Hardship and dispute recognition
  • Recommends an action; never authorises one
How the work divides

An AI workforce handles the volume.
Your people handle what matters.

Agents work every account and escalate only what your rules say a person should see. You decide where that line falls.

82%Resolved by AI agents
18%Human
Autonomous treatmentExpert edge cases

Every account worked instantly

No queue, no shift, no waiting for a free agent.

The same standard on every contact

One approved playbook, applied identically at any volume.

People elevated, not removed

Your collectors take disputes, hardship and high-value negotiation.

Integration

It reads your system of record and writes every outcome back.

No migration, no rip-and-replace.

01

REST API

A read-write connection to your system of record. Ayra reads overdue accounts in real time and posts every contact, offer and resolution back against the same case.

02

Webhooks

Trigger a collection sequence from an event in your own system — an instalment failing, an invoice passing 30 days, a policy entering its cancellation window.

03

Scheduled file exchange

Where an API isn't available yet, Ayra works from scheduled report files and reconciles against them. Several live deployments start this way.

04

Dedicated mailbox

A mailbox allocated to the system, so inbound replies and payment confirmations match to the right case without anyone granting access to personal inboxes.

Your system LMS · billing · policy · core Ayra decide · contact · negotiate · confirm Same system every outcome written back overdue accounts in contacts, offers, outcomes out

Read in, work the account, write every contact, offer and resolution back against the same case.

Live today with Salesforce-based platforms. Tell us what you run and we will say plainly whether it is a connector we already have or work we would need to do.

See the architecture run on your book.

Book a demo and we'll walk your engineers and your compliance lead through it in the same call.