Use case
Amarnex for Collection and Finance Institutes
Turn financing and collection handoffs into visible, accountable customer journeys.
How this tenant works
Each institute operates its own tenant with private agents, policies, scripts, credentials, risk notes, and portfolio analytics. A shared pipeline is created for each client organization or portfolio, exposing only approved case data and status.
Customer and partner interactions
- 01
Case intake, customer identity and contact verification, consent and preference review.
- 02
Finance application or collection segmentation, document requests, eligibility or policy checkpoints.
- 03
Calls, SMS, email, reminders, promise-to-pay capture, payment instructions, and follow-up.
- 04
Exception handling, disputes, rescheduling, escalation, settlement or closure steps.
- 05
Receipts, statements, case outcomes, service feedback, and authorized reporting back to the originating tenant.
Shared pipelines between tenants
Developers or property operators assign approved cases into a shared portfolio pipeline. The institute updates contact attempts, requirements, commitments, payment status, exceptions, and outcomes. Sensitive internal assessments, credentials, unrelated portfolios, and user data stay inside the institute tenant.
Sharing principle
Each shared pipeline exposes only approved records, fields, stages, documents, tasks, and performance indicators to named counterpart tenants. Every tenant keeps its own users, credentials, social-media accounts, communication channels, internal notes, and unrelated customer data. Permissions, ownership, edit rights, expiry, and audit history are configured for every relationship.
Recommended modules
Browse the module catalogCase and Portfolio Management
Organize assigned customers by client, project, aging, stage, and priority.
Collections Workflow
Plan reminders, conversations, commitments, follow-ups, receipts, and escalation.
Finance Application Workflow
Coordinate document and status steps when financing services are in scope.
Omnichannel Communications
Maintain an authorized history of calls, SMS, email, and chat.
Documents and Evidence
Manage required files, payment evidence, statements, and audit records.
Shared Pipelines and Reporting
Return approved status and service information to the originating tenant.
Recommended features
Browse the feature catalog- Portfolio segmentation and prioritized work queues.
- Customer contact timeline and follow-up tasks.
- Promise-to-pay and payment-status tracking.
- Role-based approval and escalation.
- Controlled document exchange.
- Shared dashboards by client, project, stage, agent, and outcome.
- Consent, suppression, and recording controls.
Example connected journey
- 01
A developer assigns an approved case.
- 02
The institute verifies the required information.
- 03
The institute communicates through permitted channels.
- 04
The institute records documents and commitments.
- 05
The institute updates milestones for the developer.
- 06
The institute resolves exceptions.
- 07
The institute closes the case with an auditable outcome.
Business benefits
- Clear ownership of every case and next action.
- More consistent customer communication.
- Earlier visibility of risk and exceptions.
- Less manual reconciliation between institute and developer.
- Auditable service performance without exposing private portfolio data.
Why this configuration matters
Collection and finance work depends on timely, trustworthy status exchange. Shared pipelines keep the customer experience connected while protecting the institute’s regulated processes and internal decision information.
Governance and rollout
Start with the pipeline stages, information ownership, sharing rules, service levels, and success measures agreed by the participating tenants. Configure the required modules, train each team for its role, and review performance without exposing unrelated tenant data. Availability of each module, connector, AI capability, and automated action remains subject to the purchased scope, local requirements, and implementation validation.
Other use cases
Design Your Tenant Workflow
Confirm stages, information ownership, sharing rules, and the modules this tenant needs.