Collection work that leaves a trail a regulator accepts.

Billing records, reminder cadence, promise-to-pay, and reconciliation in one flow – over WhatsApp, phone, or email, with every attempt recorded against the customer.

Collection is where a suite either respects the customer or harasses them. This module enforces a cadence per segment, records every attempt and its outcome, and refuses to call a number on the do-not-call list.

The reconciliation view is the part finance asks about first: which promises were kept, which broke, and what is still outstanding today.

  • CadenceAttempt limits per segment, enforced
  • PromiseDate and amount recorded, then tracked
  • DNCChecked at dial and at send time
  • TrailEvery attempt with outcome and channel
Billing

The outstanding balance is the source, not a spreadsheet.

Billing records carry the amount, due date, ageing bucket, and segment. Reminder cadence is defined per segment, so a first reminder and a final notice are different flows rather than different tones of voice.

  • Amounts, due dates, and ageing buckets per customer
  • Segmented cadence with attempt limits
  • Reminder templates per channel and stage
  • Outstanding list per collector and per branch
hospital · queue display
Antrean Poli Penyakit DalamLive
Sedang dipanggilA-014
BerikutnyaA-015
Menunggu: 6Rata-rata tunggu: 14mLewat target: 1
Promise to pay

A promise is a dated record, not a note.

When a customer commits to a date, it is recorded with amount and channel. On the date, the promise is checked against payment; broken promises escalate to the next cadence step automatically, and kept promises are visible in reconciliation.

  • Promise date, amount, and channel recorded
  • Automatic check against received payment
  • Escalation on broken promise
  • Kept-promise rate per collector and segment
hospital · queue display
Antrean Poli Penyakit DalamLive
Sedang dipanggilA-014
BerikutnyaA-015
Menunggu: 6Rata-rata tunggu: 14mLewat target: 1
Compliance

The rules that keep the operation legal are enforced in code.

Do-not-call lists, attempt caps, contact windows, and recorded consent are enforced where the action happens – in the dialer and in the message sender – not in a policy document nobody opens.

  • DNC enforcement at dial and at send
  • Contact window and attempt cap per segment
  • Recording and transcript retention per policy
  • Exportable attempt log for audit
voice · agent workspace
RARani Anggrainiantrean Poli Penyakit Dalam · menunggu 00:4202:18
HoldTransfer poliWhisperAkhiri
Konteks pasiendari CRM
Kunjungan2 kunjungan terakhir: Poli Anak (Mei), Poli Dalam (Agu).
JanjiJanji temu hari ini 09:40 — belum check-in.
CSATSurvey otomatis dikirim setelah panggilan berakhir.

What Collection covers

Billing records

Amount, due date, ageing bucket, segment.

Cadence

Per-segment reminder flow with attempt caps.

Promise to pay

Dated commitment tracked to payment.

Reconciliation

Outstanding, kept, and broken promises.

Compliance

DNC, contact window, attempt limits, audit log.

Channels

WhatsApp, voice, email, with one history per customer.

Questions before moving collection in-house

Can we import the ageing file daily?

Yes, through the staged import with validation before write.

Does it stop calls to DNC numbers?

Yes, the list is checked at dial time and the attempt is refused, not just flagged.

Who sees the customer history?

Collectors see their segment; supervisors see the branch; permissions are per team.

Is the recording admissible?

Recordings and CDRs are stored with retention under your policy; admissibility is a legal decision for your counsel.

See this app running on your own data.

We install the suite on your server or in our cloud, then walk your team through the exact flow you described.

Trusted by industries

Development

API siap produksi untuk tim yang membangun pengalaman sendiri.

Selain aplikasi siap pakai, PDS membuka jalur programmatic: kirim pesan, kelola percakapan, dan tarik data operasional dari endpoint yang sama dengan yang dipakai aplikasi internal — lengkap dengan webhook, API key per tenant, dan pencatatan setiap percobaan pengiriman.

Messaging API

Satu endpoint untuk WhatsApp, SMS, dan email. Nomor pengirim diatur per channel, status pengiriman dilaporkan balik lewat callback.

Learn more →

Webhooks

Event percakapan, tiket, dan pembayaran dikirim ke URL Anda, ditandatangani dan dicatat ulang bila gagal terkirim.

Learn more →

Omnichannel connector

Channel yang belum tersedia bisa ditambahkan sebagai driver sendiri: mapping field, signature, dan aturan balasan Anda tentukan.

Learn more →

Data & export

Rekaman percakapan, CDR, tiket, dan dataset operasional bisa ditarik lewat API atau diekspor terjadwal untuk gudang data Anda.

Learn more →