Platform / Flow builder
Draw the strategy once. The engine runs it a lakh times.
A recovery strategy is a graph: contact, wait for what happens, branch on the outcome, escalate. attpro's flow builder makes the graph visible, validates it before publish, and executes it per borrower, continuously.
How it runs
Flow builder end to end
The same shape on every account: the flow acts, the world answers, the account is written. Nothing depends on someone remembering.
- 1DrawBuckets, channels, waits and escalation on a canvas, with branch labels on every edge.
- 2ValidatePublishing is refused while any documented branch is unhandled. The graph is the whole policy.
- 3DispatchOne run per borrower, gated on the campaign window and the batch it belongs to.
- 4ParkThe run waits on a real signal: a receipt, a disposition, a promise date, a payment.
- 5ResumeThe signal arrives, the branch is stamped, and the next node is dispatched.
A run can stay open for weeks and still take the correct branch when the signal finally lands.
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 flow builder.
Visual canvas
Nodes for every channel and decision, edges labelled with real outcomes: answered, promised, paid, no response in 72 hours. The whole strategy on one screen.
Branch-complete validation
A flow cannot publish unless every outcome of every node has a branch. The engine never improvises when a borrower does something you did not draw.
Park and resume
Flows wait on the real world - a payment landing, a visit completing, a message being read - and resume the moment it happens, or take the timeout branch you chose.
Versioning and publish gates
Edit safely while the published version keeps running. Publishing is explicit, validated and audited.
Five node families
comm.* contacts the borrower, logic.* branches and gates, wait.* parks on a signal or a timer, data.* enriches and scores, alloc.* re-allocates and suppresses. Everything the floor does is one of those.
Generate it from plain English
Describe the ladder and the composer draws it; hand-edit on the canvas from there. Non-technical operators build these.
- Per borrower
- Every branch
- Timeout
Not a batch job with a filter on top.
The validator will not publish a dead end.
A signal that never comes still moves the account.
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
Flow builder 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 voiceMessaging
Messages that report back, not broadcasts into the dark
SMS, WhatsApp, RCS and email run from the same flow as every other channel. Delivery, read and reply signals come back into the engine and decide the next step for that one...
Open messagingQuestions
Before a pilot on flow builder
The questions a collections head or an infosec team asks first. Anything else, an engineer answers on the demo call.
Can we change a live flow?
You edit a draft, the validator checks it, you publish. Running borrowers continue on the version they started on unless you choose to migrate them; a restart is one action on the account.
How do timeouts and quiet hours interact?
A wait node can carry a named timeout branch. Every outbound node checks the campaign's active hours and the tenant's quiet hours in IST before it fires, and defers rather than skips.
Do we start from a blank canvas?
No. A template library ships with bucket-wise strategies the ATTPRO floor runs, and a description-to-flow composer drafts a first version from a paragraph. Both are starting points, not constraints.
Further reading
Notes that go deeper
Written for practitioners, ungated, and specific to Indian lending.
What a collections flow engine actually does
Every lender has a recovery strategy. Most of them keep it in a policy document, a set of Excel filters and the head of collections memory. A flow engine is what happens when you write it down once and let it run.
ReadDesigning an escalation ladder that stops at the right rung
Escalation is easy to design going up and almost never designed going down. The result is an operation that spends its most expensive resources on borrowers who would have paid after a message.
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.