Multi-Portfolio Tenancy
One floor, many lenders.
Portfolio-scoped isolation enforced at the data layer. Each lender gets its own custom fields, bucketing rules, dialer campaigns, and reporting — without a separate instance.
Portfolio Aggregate
3 PortfoliosCredit Card / Bank A
Yield: 8.4%
₹42.0M
Personal Loan / FinTech B
Yield: 9.4%
₹30.0M
Auto Loan / Bank C
Yield: 10.4%
₹18.0M
Capabilities
What this layer does for your team.
Outcomes a recovery manager actually feels — captured by the platform, not the agent's memory.
Book a walkthrough- Portfolio types — recovery, sales, support — chosen at onboarding
- Data-layer isolation per portfolio, not just an application filter
- Custom fields per portfolio (14 field types supported)
- Bucketing rules, DPD bands, and escalation thresholds per portfolio
- Bulk import templates with auto-detected column mappings
- Assignment rules — round-robin, skill-based, geographic, custom
- Reporting and leaderboards filtered by portfolio
Deep dive
BPOs running several lenders on the same floor need real isolation, not a permission filter and a prayer.
A collections team running three lenders on the same agent floor doesn't want three separate instances. They want one platform where agents see only their assigned portfolio, where each lender's custom fields stay separate, where each lender's reports are independent, and where the data layer refuses to leak rows even if application code has a bug.
Defense in depth, not "trust me"
Tenant scoping is enforced at the data layer — not just by application code. If the application forgets to filter, the data layer still does. If a query escapes both, audit logging surfaces it.
Configurable, not hard-coded
Each portfolio defines its own custom fields, its own DPD bands, its own bucketing rules, its own escalation thresholds, its own templates. The platform doesn't impose a single "collections schema" on every customer.
Outcomes
What changes when you ship this.
- BPOs add a new lender without standing up a new instance
- Agents see only their assigned portfolio — accidentally or otherwise
- Per-lender compliance reports come out clean, not as a manual export
- Schema differences between lenders stop being a custom-engineering problem
Keep exploring
Book a 30-minute walkthrough
See Credmux run a real recovery workflow.
We'll show calling, Smart Collect attribution and decisioning, payment-link orchestration, and field visit evidence — using common DPD bands and industry-standard workflows.
Or write to hello@credmux.com