Skip to content
attpro
Book a demo

Integrations

Plugs into the stack you have

16 integrations in 7 groups. Your LMS stays the system of lending record; providers for telephony, messaging, AI and payments connect under your own credentials, so you pay their price and revoke their keys without asking us.

Talk about your stackDeveloper docs
16 integrations · 7 groupswhose keys

10 of 16 under your credentialsrevoke without asking us

Integration directory: Loan management and core banking, 4; Telephony, 1; Messaging, 2; Speech and language models, 4; Payments, 2; Alternate MetaData, 1; Hosting and storage, 2. 10 of 16 connect under the lender’s own credentials.

Architecture

Which way the data moves, and whose keys it moves under

Your loan management system stays the system of lending record. We take the book, work it, and hand back state - while every provider that costs money runs on your own account.

Data in

  • Portfolio and allocationsCSV over SFTP, or REST push
  • Balances, closures, disbursalsREST, cursor-paginated
  • Payment confirmationsWebhook, or file ingestion
  • Do-not-contact and consentField on the record, honoured at dispatch

The engine

One run per borrower, gated on the campaign window, the batch and the conduct rules, and parked until a real signal arrives.

  • Flow validated before publish, no unhandled branch
  • Quiet hours and caps checked at dispatch
  • Every contact written with the rule that allowed it
  • Schema-per-tenant isolation, India-resident

Records out

  • Dispositions and promisesWebhook, signed and retried
  • Payments and receiptsYour gateway, matched to the loan
  • Recordings and transcriptsObject storage, pointer in the API
  • MIS, CRM and BIExtract on demand, or webhook
10 of 16 providers connect under your own credentials: you hold the contract, you pay their price, and you can revoke the key without asking us.
On this page

Loan management and core banking

The lender's system of record stays where it is. The platform takes an export, works the book, and returns state.

4 · attpro account

  • CSV over SFTP

    A nightly extract is enough to start. The upload wizard maps columns, dry-runs the file and commits, with saved mappings per lender.

  • REST API

    Push disbursals, balances and closures in; read dispositions, promises and payments out. Cursor-paginated, idempotent writes.

  • Webhooks

    Subscribe to dispositions, payments, PTPs, DNC changes and flow events, signed and retried.

  • MIS, CRM and BI

    Extracts on demand and webhooks out; the reporting stack you have keeps working.

Telephony

Calls are placed over the lender's own trunk, so caller IDs, recordings and billing stay with the lender.

1 · your keys

  • Exotel

    your keys

    SIP trunking, virtual numbers, Voice v3 and the WebRTC SDK for the telecaller console. Outbound, inbound and voice broadcast.

Messaging

SMS, WhatsApp, RCS and email from the same flow as every other channel, with delivery and read signals fed back.

2 · your keys

  • Helo.ai (VivaConnect)

    your keys

    SMS, WhatsApp Business and RCS. Templates bound to TRAI DLT registrations before dispatch.

  • SendGrid

    your keys

    Email with delivered, opened, clicked and bounced events resuming the flow.

Speech and language models

The voice agent's ears, brain and voice are swappable per agent. Indian-language providers first.

4 · your keys

  • Sarvam AI

    your keys

    Saarika speech recognition and Bulbul voices for Indic languages; the default cascade.

  • Deepgram, AssemblyAI, Whisper

    your keys

    Alternative speech recognition, with keyword boosting where supported.

  • Google Gemini, Anthropic Claude, OpenAI

    your keys

    Conversation models, including real-time speech-to-speech engines where the language allows.

  • Smallest.ai, Cartesia, ElevenLabs, PlayHT

    your keys

    Text-to-speech and voice cloning for agent personas.

Payments

Links, UPI, cards, netbanking and NACH, reconciled to the account in near real time.

2 · your keys

  • Razorpay

    your keys

    Payment links and the self-service portal; callbacks post payments to the ledger.

  • Cashfree

    your keys

    Payment links and collections, with the same reconciliation path.

Alternate MetaData

When the number is dead, the flow can request fresh coordinates and re-enter contact when they land.

1 · your keys

  • Alternate MetaData provider

    your keys

    Contact enrichment under a recorded, purpose-limited reason, on your own credentials.

Hosting and storage

Run on attpro's own account, in India. Listed on the Trust Center as sub-processors.

2 · attpro account

  • Indian-region cloud hosting

    Application, database and cache. Named in the data processing agreement.

  • Wasabi (Mumbai)

    Encrypted object storage for recordings, exports and backups.

Something not listed?

The channel and provider layers are adapters behind one interface. A new telephony carrier, messaging aggregator or model provider is a bounded piece of work, scoped in the proposal rather than promised here.

Ask about a provider

Sub-processors

Who runs on our account, and who runs on yours

Hosting and storage are attpro sub-processors and are listed on the Trust Center. Everything marked with your keys is your processor, under your contract with them.

Sub-processor listSecurity and architecture

Bring 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.

Book a demoTalk to an engineer