Skip to main content

Salesforce Customization for Mortgage Servicing Company

Identifying a fresh approach, eliminating organizational pain spots, and made use of the features available with Salesforce Sales and Experience Cloud licenses

Published by jetbi
01 March 2023
Salesforce

Project Description

A client of JET BI previously used Salesforce Sales Cloud to handle lead submissions and customer information. The client is a US-based business that offers mortgage financing services to investors and consumers. The sales and account management team found it challenging to refer to customer information and any terms that were presented during earlier client encounters because this strategy was far from the all-inclusive solution that the organization required.


Project Challenges:

  • A flexible application is required to assist business activities rather than subjecting them to the system as a victim;
  • Enhancements to the engagement/transaction pipeline's overall UI/UX;
  • Coordination of activities across several teams within the company;
  • Automating the processes for managing and submitting documents; Automating the computations for loan commissions;
  • Providing customers with real-time updates, access to their loan information, and openness regarding the status of their application;
  • Development of more individualised marketing and social interaction.

 

Project Scope:

JET BI carried out an end-to-end business process evaluation in collaboration with important stakeholders. Together, the Team identified a fresh approach, eliminated organisational pain spots, and made use of the features available with Salesforce Sales and Experience Cloud licenses. The JET BI Architecture Team conducted a thorough evaluation before developing a transformative roadmap to make the most of the Client's Salesforce investment, maintain security, and adhere to corporate compliance:

  • Sales Cloud Reconfiguration and Customization;
  • Integration with CongaComposer and CongaSign;
  • Experience Cloud portal for customers;
  • Declarative development (Flows, Approval Processes, Email Templates);
  • Custom development (APEX Batch, APEX triggers, Visualforce pages, Custom LWC);
  • Pardot Implementation.

 

Project Results 

  • Salesforce Sales Cloud customization allows centralized management of all business processes - from application submission all the way through to funding approval. Management can now see the status of any deal and sales funnel generally; 
  • Document Checklist Component (Lightning Web Component) provides a simple way to collect the required documents from the customers, track the application submission progress, manage file uploads and approvals;

salesforce-mortgage-company-1

 

  • Loan Commission Calculator (Lightning Web Component) enables automatic calculation of commission, fees, rebates and net income based on loan data;

salesforce-mortgage-company-2

 

  • Integration and with CongaComposer and CongaSign allows creation of accurate digital documents using pre-built or customized templates automatically populated with data from Salesforce as well as their sending for signature; 
  • Experience Cloud-based portal allowed simplifying loan application process, tracking of real-time updates, communication between Cleint’s teams and their customers. From now on, customers can submit loan application documents through a customer portal. They can also track the loan application progress as well as communicate with their account manager on the deal status;

salesforce-mortgage-company-3

salesforce-mortgage-company-4

 

  • Pardot integration helped send out newsletters and organize data around a common view of leads and simplify the lead qualification process, giving personalization in sales.
Start your project now
Expertise
JET BI TEAM
  • 1 Salesforce Certified Consultant
  • 1 Salesforce Certified Developer
  • 1 ISTBQ Certified QA Specialist
TECHNOLOGIES
  • APEX
  • Experience Cloud
  • Salesforce
PROJECT TIMELINE
  • 3 months
Question to the expert
image

We have available resources to start working on your project within 5 business days

1 UX Designer

image

1 Admin

image

2 QA engineers

image

1 Consultant

image
Related Articles
All articles
image
Is Salesforce Winning the Public Sector Race?
An analysis of Salesforce's rapid expansion into the U.S. public sector, tracing its path from cautious early government licensing deals in the 2010s through the launch of Government Cloud in 2012, its pivotal role in COVID-19 vaccine rollouts, and its 2025–2026 push into military and intelligence work via Agentforce and Missionforce. The piece covers major 2026 contracts — including a $5.6 billion Army deal, a $1.6 billion VA agreement, and Pentagon Impact Level 5 authorization — alongside real-world case studies like California's REAL ID processing and the UK's NHS back-office operations. It also examines the structural obstacles still facing Salesforce and other vendors in government tech: legacy IT systems decades old, outdated federal procurement rules, budget constraints, and organizational caution around AI adoption, plus the competitive pressure from Palantir, Microsoft, and Oracle in the race for public sector AI spending.
28 August 2026
image
Why Your Salesforce Flows Are Agentforce's Biggest Problem
This article argues that the most underestimated risk in Agentforce deployments isn't data quality — it's the automation layer: years of overlapping Flows, Process Builder processes, Apex triggers, and managed package logic that no one has reviewed end-to-end. It explains why AI agents inherit automation complexity without the tribal knowledge human admins carry, why technical debt only becomes visible after an agent hits it in production, and why a clean demo is no indicator of production readiness. The article closes with a concrete, tool-by-tool inventory approach using Flow Trigger Explorer, Salesforce Optimizer, Setup Audit Trail, Apex Debug Logs, Agent Builder, and Health Check — scoped to the specific processes the agent will actually use rather than the whole org.
23 July 2026
image
How to Wire Multiple Salesforce Projects in One Org Without Breaking Everything
This article maps the real integration patterns that emerge when multiple Salesforce projects — both managed packages and unpackaged code — share a single org. It covers four concrete patterns: attaching custom triggers to package-owned objects, calling global members exposed by managed packages, writing directly into another project's objects, and runtime-guarded reads of package data. It then addresses access control for authenticated and guest users, including the Master-Detail wall and the without sharing elevation pattern. The piece closes with eight concrete risks (compile-time dependencies that block uninstall, upgrade coupling, silent cascade failures, access invisible to admins) and six actionable recommendations for keeping cross-project coupling manageable.
08 July 2026