Supporting work sample · Salesforce · 2026
Making daily work
easier to navigate.
A reporting workbook translated into an interactive dashboard. A crowded action bar reorganized around the admissions team’s work.
My roleI rebuilt the KPI dashboard, added its tables and filter mappings, and checked the reporting definitions. I also restored the team’s primary Opportunity actions after new payment controls displaced them.
Work completed in Salesforce, alongside colleagues and with AI-assisted technical support.
Work completed in Salesforce, alongside colleagues and with AI-assisted technical support.
01 · From workbook to workspace
One view.
Two ways to explore.
The customer tracked each representative’s monthly calls and admissions in a spreadsheet. The dashboard brings those measures together, with Rep and Month filters connecting call activity to the admission funnel.
Try the filters. All six components update using a small, fictional dataset.
Contact Center · Reporting
ILLUSTRATIVE DATACC Rep KPIs Dashboard
Call activity, admissions, and cost per admit
8 fictional reps · 3 months
Calls by Rep & Direction
02InboundOutbound
Total Calls
03—
Fictional activity
Total Talk Time (min)
04—
Fictional minutes
DM KPI’s by Rep
05| Rep | VOB | Approved | Working | Admits | Qual. → admit | Rep CPA |
|---|
DM = digital marketing · CPA = cost per admit · all values fictional
Admits by Rep — DM vs BD
06| Rep | Channel | Admits | Total CPA |
|---|
BD = business development · CPA shown on each rep subtotal
A shared set of filters.
The same rep and period connect three source reports. In the delivered dashboard, call activity uses Activity Date; the admission funnel uses Created Date.
Reconstruction of the six-component layout verified in production. Component hierarchy and desktop grid proportions follow the deployed configuration; visual styling and chart values are illustrative. The supporting annotation occupies otherwise unused space. On narrow screens, this exhibit rearranges the cards for readability.
01
Keep the customer’s mental model.
Rep and Month mirror the workbook’s tabs and rows, while bringing calls, the admission funnel, and cost per admit into one view.
02
Make the filters mean the same thing.
I corrected the links between Opportunity Owner and call Assigned To, and mapped each report to the date field appropriate to its data.
03
Check the numbers behind the interface.
I reconciled the reporting definitions against the customer’s workbook and checked cost-field access. These illustrative numbers are not project results.
02 · Restoring task priority
Five visible slots.
The right actions first.
A payment integration placed six financial actions before the admissions team’s existing controls. With five visible slots, familiar tasks moved into the overflow menu. The customer asked to bring them back.
The change reordered existing actions and retained their visibility rules.
Desktop action bar · fictional Person Account opportunity
Before · payment actions lead
Verified pre-change orderThe primary admission actions are in More. Open the menu to see the original order.
After · admissions actions lead
Verified deployed orderThe first five slots restore Edit, Create VTX, Create PAA, Submit for Approval, and New Task. Financial actions remain in More.
Reconstructed from the documented before/after artifacts and the current retrieved page. These are inert action labels; only the stage selector and overflow menus are interactive. The incident affected desktop because financial actions already had desktop-only visibility.
Respect the existing workflow.
I restored the requested action hierarchy without adding controls or changing permissions. Payment actions remained available in the overflow menu for the same eligible records.
Preserve the conditional fifth slot.
When the record is Approved, Push to Kipu becomes the fifth action and New Task moves into the menu. The reorder preserved that existing behavior.
Contribution and evidence
Configuration work,
with a clear role.
These examples show my direct work on the interfaces people use to run a business: how information is grouped, how controls are prioritized, and whether the resulting behavior is dependable.
What I personally contributed
Customer requirements and feedback, dashboard reconstruction, Lightning tables, cross-report filter mapping, metric verification, and the Opportunity action reorder. Recorded work also includes a follow-up correction to cost-field permissions.
What I reused and shared
The solution uses Salesforce’s existing components. Colleagues supplied earlier reports, initial charts, and other implementation work. I extended those assets with AI-assisted technical support; I did not design Salesforce’s visual system.