Short answer: A mortgage CRM case study is useful when it helps a buyer test comparable work in a current review. The published Cendera Funding story describes one historical implementation context: 50+ accounts and 70 loan officers, with originator-level CRM use and corporate-level campaigns. It is not a prediction of another team's timeline or result.
This page organizes the original BNTouch-hosted case-study source into questions a mortgage team can use when evaluating its own implementation plan. It retains the customer's context and clearly separates historical evidence from current product confirmation.
What the published source describes
| Source detail | Historical context | Question for a current review |
|---|---|---|
| Team and operating goal | Cendera Funding identified 50+ accounts and 70 loan officers. The customer described a need for both originator-level use and corporate-level campaign work. | Which roles need different views, permissions, reporting, and review points before launch? |
| Workflow change | The customer described moving loan-status communications from another service and setting up corporate lead-drip and post-funded campaigns. | Which live communications, audience definitions, approvals, and stop conditions need to be reviewed before a team changes a workflow? |
| Reported timing | The customer's published account says its onboarding took about two to three weeks. | What is the organization's own data readiness, user scope, workflow complexity, review process, and acceptance plan? |
Primary source: BNTouch CRM Implementation Case Study: Cendera Funding.
Use historical customer evidence responsibly
- Read the customer's stated context before treating a detail as comparable to your organization.
- Write down the records, users, communication paths, and workflow owners in scope for the current review.
- Use representative, non-sensitive records to test the expected state and exception path.
- Document the actual review result and the accountable person before relying on a workflow.
For a current implementation test, use the mortgage CRM go-live test. For a migration-oriented review, use the mortgage CRM transition guide.
What this evidence does not establish
The source is a historical customer statement. It does not establish current product scope, account configuration, connection availability, data movement, support terms, a standard implementation timeline, a required process, or an outcome for another organization. Confirm the current workflow with the records, people, and controls relevant to the organization evaluating it.
Scope: This is an evidence-reading guide, not lending, legal, privacy, advertising, or compliance advice. Use the organization's approved process and responsible reviewers for decisions involving borrower records, communications, workflow changes, or customer statements.
Review your implementation context with BNTouch
Bring one representative workflow and one exception to a BNTouch demo, then ask to see the current review points that apply to your team.
