Platform / Compliance
Compliance as physics, not policy
Quiet hours, consent, contact caps and evidence are enforced by the engine itself. A call that would breach the rules is not flagged afterwards - it is never placed.
How it runs
Compliance end to end
The same shape on every account: the flow acts, the world answers, the account is written. Nothing depends on someone remembering.
- 1ConfigureWindows in IST, caps per day and week, consent and do-not-call state.
- 2EnforceChecked at dispatch, not at design time, so a delayed queue cannot create a breach.
- 3RecordEach contact carries the rule that allowed it, the campaign and the outcome.
- 4ChainAudit rows are append-only and hashed, so alteration is detectable rather than deniable.
- 5ProduceOne borrower, twelve months, with times and outcomes, without a ticket to engineering.
A rule that changes applies to the next dispatch, and the old one stays on the old records.
What it does
The working parts
Each part is a real record in the platform, not a feature on a slide. 6 of them make up compliance.
Quiet hours in the dialer
Calling windows are enforced in IST at dispatch time, per campaign. Outside the window, the call does not exist.
Consent and DNC ledger
Do-not-call is honoured across every channel, tenant-wide and platform-wide. Consent state is a record, not a memo.
Evidence by default
Every contact, disposition and payment writes an audit row. Recordings and transcripts retain on the schedule you set.
Tamper-evident audit
Audit logs are anchored with a Merkle chain, so evidence produced in a dispute can be shown untouched.
Data lifecycle
Archive, purge and legal hold per DPDP - retention that a data protection officer can sign.
PII redaction and disclosure
Transcripts carry PII redaction; recording disclosure is played on every call by the engine, not by the agent remembering to.
- At dispatch
- Across channels
- Append-only
A call outside the window is never placed.
Voice and messaging counted together.
Written as the work happens, not rebuilt afterwards.
Controls and outputs
What you set, and what you get back
Every control is a setting in the admin app with an audit trail; every output is a record on the borrower, not a spreadsheet.
Settings are per tenant and per campaign, and every change is attributable. Outputs are written as the work happens, not assembled afterwards.
Part of one system
Compliance does not work alone
The signals it produces are read by the rest of the platform the same second. These two are the closest neighbours.
AI voice
A voice agent that holds the conversation, not a script
attpro's voice agents speak ten Indian languages plus Hinglish, listen through interruptions, and carry seventeen in-call tools - so a call ends in a promise, a payment link, a...
Open AI voiceAnalytics
The book, explained - not another export to Excel
Operations dashboards, AI cohort intelligence, recovery forecasts and agent performance, computed on the live book and rendered in the units Indian lending actually uses.
Open analyticsQuestions
Before a pilot on compliance
The questions a collections head or an infosec team asks first. Anything else, an engineer answers on the demo call.
Which regulations does this map to?
RBI's Fair Practices Code and outsourcing guidelines for collections conduct, TRAI DLT for SMS, and the DPDP Act for personal data. The compliance hub lists each control against each clause.
Can a borrower see and exercise their rights?
A borrower portal shows what is held and lets them raise a grievance, request a callback or opt out of a channel. Grievance handling has its own SLA clock and escalation.
How is data retention handled?
Retention schedules per record type, executed by the platform on schedule and logged. Recordings and transcripts age out on the policy you set, with legal holds where a dispute is open.
Further reading
Notes that go deeper
Written for practitioners, ungated, and specific to Indian lending.
Quiet hours in Indian collections: what the rules actually require
The Fair Practices Code's contact-hours expectation is short. Operationalising it across voice, messaging and field is not. A plain-language walk-through.
ReadDisclosure on a collections call: who you are, why you are calling
The opening fifteen seconds of a collections call carry most of its compliance risk and most of its chance of working. They are usually left to the caller to improvise.
ReadBring one delinquent cohort. We will run it.
A demo here is not a slideshow. Pick a segment of your book, watch a flow built for it, and hear an agent call a test number in your language.