Just thought to share — if you’re looking to gain experience and get a real feel for Salesforce and the day-to-day responsibilities, try volunteering. It’s a great way to build confidence, learn on the job, and strengthen your skills. 🫡

https://teams.microsoft.com/l/meetup-join/19%3ameeting_NTM0Y2ZhZDUtZWFhNS00ZTM0LWJlNGItY2RmZTExYjA3Yjhk%40thread.v2/0?context=%7b%22Tid%22%3a%221961aecd-e89e-4d66-91c0-eb15eae7bfb3%22%2c%22Oid%22%3a%22ee8429c1-f709-4167-8b9c-b5c734f508eb%22%7d

We ARE LIVE FAM💃

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