Salesforce Client-Retention System
Completed · DecisionHR
Built a 'Client Health Check Ups' Salesforce object that tracked health status through flows, created new records on a Lightning page, and emailed the client owner to prompt follow-up. The health data then fed into a Power BI leadership dashboard.
The challenge
Stakeholders needed an accessible way to review client health status, track outreach activity, and support timely client engagement.
My role
Process Analysis and Automation Intern. Gathered requirements, designed the 'Client Health Check Ups' object, built the flows and Lightning page, and connected the data to Power BI.
Research & requirements
Met with business stakeholders to understand how they currently tracked client health, mapped the existing outreach process, and documented which data mattered for retention conversations.
The solution
Built a custom 'Client Health Check Ups' object to capture health status, used flows to create new records on a Lightning page, and emailed the client owner when follow-up was needed. The resulting data was then modeled in Power BI so leadership could monitor retention trends.
Technical approach
- Custom 'Client Health Check Ups' object with health status fields modeled around the retention workflow
- Salesforce flows that create new records on the Lightning page and email the client owner to reach out
- Lightning App Builder pages assembling related records and flows into one stakeholder view
- Salesforce data connected to Power BI for leadership reporting and trend monitoring
- Data modeling and requirements gathering to define relationships and data quality expectations
- Testing, validation, and documentation to support end-user adoption
Tools used
- Salesforce
- Salesforce Flow
- Lightning App Builder
- Custom objects
- Scheduled flows
- Power BI
Business impact
Gave stakeholders a structured view of client health, outreach activity, and retention trends in support of client-engagement efforts. Internal results and implementation details are confidential.
What I learned
Requirements conversations are where most of the design happens. Understanding how people actually work before building saved rework, and small automation choices made the difference between a page people tolerate and one they use.