A small property management company in Birmingham uses Salesforce to track the buildings they manage and the maintenance requests raised by tenants.
But here’s the problem:
🔧 All maintenance issues are being logged under the Account record, using messy custom fields.
📄 Tenants sometimes call in more than once, but there’s no easy way to track previous requests.
📊 Reports are confusing — managers can’t see how many requests came from each building.
👷 Engineers don’t know which issue is linked to which tenant or which building.
You’ve just been hired as the new Salesforce Admin.
The company wants:
✅ Each Building to be tracked as a record
✅ Each Maintenance Request to be tied to the correct Building
✅ Ability to report on number of issues per building, and status of each request
✅ Clear visibility without cluttering the Account object
What would YOU do to fix this?
Which objects would you use?
Would you create a custom object or use something standard?
What kind of relationship would you build — and why?
Drop your answer in the comments below 👇
#WhoCanFixThis #DataModel #SalesforceAdmin #SimpleScenario #PathwayToSalesforce