Frequently Asked Questions

Five products on one data layer and one console. Robo Plus runs AI-led digital collections, Tele Plus handles intelligent tele-calling, Field Plus manages geo-tagged on-ground resolution, Legal Plus covers pre-litigation notices, and Settle Plus runs borrower self-service settlements. Every channel writes to the same borrower profile, so a case never restarts when it moves between products.

No. Most clients start with Robo Plus and Tele Plus because those two cover the early buckets where recovery value is highest, then switch on Field, Legal or Settle Plus as specific buckets mature. Because the products share one data layer, adding a product later is a configuration change, not a new integration.

Robo Plus works on alternate data sources, deep segmentation and behavioural science. It selects the best medium, the best time to connect, the best content and the best language for each borrower, then executes the campaign and reads the dispositions back into its analytics. Cases that digital channels cannot close are referred out to the call centre or the field automatically.

IVR, SMS, WhatsApp, email and bots for digital outreach; tele-calling for the voice layer; geo-tagged field visits for accounts that need a physical conversation; and physical or digital legal notices for the pre-litigation stage. Channel preferences and opt-outs are respected across all of them.

Settle Plus targets accounts with extended delinquency, typically 180 days or more. The borrower receives a secure link or webpage showing the defaulted loan details, proposes a settlement amount, can split it into parts and adds remarks. The request then reaches the lender for evaluation and approval. The system also predicts settlement amounts likely to be approved, so offers stay within lender policy while remaining feasible for the borrower.

Yes. Legal Plus puts every pre-litigation action on a single dashboard: notice delivery status, whether the borrower opened or clicked the notice, engagement outputs, payment status and remarks. The nudge mechanism responds to those interactions, so follow-up happens without manual chasing.

With Collections as a Service, we manage collections and you see results: FrenzoFinserv runs the technology, the people and the day-to-day operations against your outcomes. With Platform as a Service, you run collections and we power the platform: your team works in the console, on your playbook, while we maintain the stack underneath. Same products, same data layer, different owner of execution.

Three questions usually decide it. Do you already have a trained collections team that wants tooling rather than an outsourced function? Do you need to keep borrower contact fully in-house for policy reasons? And how quickly do you need recovery moving? Teams with people and process but weak technology lean PaaS. Teams that need recovery working in weeks, or that want to shed agency sprawl, lean CaaS.

Yes, and many clients do. A typical split is digital and tele collections run as CaaS while legal and settlement are handled by the in-house team on PaaS. Because both models sit on the same stack, the case history stays continuous and reporting stays comparable across the two.

CaaS is normally performance-linked and scoped per bucket, per volume and per model. PaaS is a platform subscription with onboarding and usage terms. Final commercials are agreed during scoping once portfolio size, bucket mix and channel needs are fixed.

The lender remains the data owner under both models. Access is role-scoped, our operating teams see only what their function requires, and data is purged on the agreed exit terms. Nothing about the commercial model changes that.

Yes. A common path is to begin on CaaS to stabilise recovery quickly, build the playbooks and analytics along the way, then bring execution in-house on PaaS once the team is ready. The platform, history and reporting carry over unchanged.

Compliance is enforced in the platform rather than left to individual agents. Communication windows, frequency caps and channel preferences are applied as policy on every outreach. Interactions follow approved scripts, conduct checks run on tele and field staff, and every action leaves an audit trail. Your compliance policy is encoded during onboarding, so the platform enforces your standard, not a generic one.

Yes. Call recordings, transcripts, message logs, dispositions and field visit trails are stored against the case and are retrievable for review and dispute handling. Retention is set to the term agreed in your contract.

Field Plus ties every visit to a named officer with certification and conduct checks on file, and captures location, timestamp and photo evidence for each visit. Agencies carry live scorecards on productivity, resolution and compliance, so allocation flows toward vendors that perform cleanly and away from those that do not.

Allocations move in through secured email, SFTP folders, platform upload or APIs rather than ad hoc file sharing. Access is role-scoped, sensitive fields are restricted by function, payment file mapping and purge routines run inside the platform, and administrative actions are logged. Detailed security documentation and control evidence are shared during diligence.

Yes. Pitches, message templates, notice wording, settlement terms and approval workflows are all configurable to your policy. Approvals stay with your team, so the platform accelerates the work without changing what your staff are permitted to offer.

Four to six weeks for a standard deployment, against six to twelve months for a typical build-and-integrate programme. The difference comes from the platform already being assembled: channels, analytics, scoring and reporting exist, so the work is mapping your data and encoding your policy.

A sample allocation file with field definitions, the payment file format you can provide, your channel and communication policy, and the scripts or notice templates you want enforced. From there we map the fields, set the campaign plan and run a pilot bucket before full volume.

Yes. Language is treated as one of the outreach variables alongside medium, timing and content, so a borrower receives communication in the language most likely to get a response. Messaging is available across the major Indian languages used in your portfolio.

Everything sits on the platform itself: recovery and bucket movement, channel performance, disposition breakdowns, agency and officer scorecards, and settlement status. You can upload payment files, purge data and raise queries directly, and scheduled reports can be triggered to your team on a fixed cadence.