Life of an HR, Before and After Salesforce

Before Salesforce: Me, Excel, and a Lot of Copy-Paste

Every candidate meant a decision, and every decision meant an email. I drafted and sent selection and rejection messages one by one, changing the name, the role, the date, hoping I had not pasted the wrong template into the wrong message.

New hires meant employee IDs, created by hand, one at a time. And underneath all of it were the spreadsheets: candidate lists, employee lists, status columns. I spent a real part of every week cross-checking rows and columns, quietly afraid that one wrong click would overwrite something I could not get back.

After Salesforce: The System Just Does It

Now Salesforce does the parts that used to drain me. When I mark a candidate selected or rejected, the right email goes out on its own. I do not draft it, I do not copy-paste it, I do not double-check the name. It just happens.

Employee ID creation is handled by the system the moment a hire is confirmed. And instead of a folder full of Excel files I am scared to touch, every candidate and every employee is a record in one organised place. I search instead of scroll. Nothing gets overwritten, because nothing lives in a fragile cell any more.

What's Actually Doing the Work

People ask what the magic is. There is none, and honestly that is the best part. It is a handful of ordinary Salesforce building blocks my team set up once, each doing one job well. If you are curious what sits under all of this, here it is in plain terms.

• Every candidate is a record, not a row. The person, the role, and their application are each their own object - Candidate, Position, and the Job Application that links them. The application carries a Status field (New, Screening, Interview, Offer, Hired, Rejected), and changing that status is what sets everything else in motion. A Path bar across the top shows where each person is at a glance.
• The emails that send themselves. Every message is a saved email template with merge fields that drop in the name, the role, and the date on their own. When I move an application to Selected or Rejected, a record-triggered Flow notices and fires the matching template, then logs it on the candidate's timeline. There is always a record of exactly what went out and when.
• Employee IDs the system creates. When a hire is confirmed, an ID is generated automatically - either a simple Auto Number field like EMP-0001, or a Flow that only assigns one once someone is actually hired, so candidates who did not make it never get an ID.
• Onboarding that assigns itself. The offer runs through an approval process to the right manager, who approves in a click. Then a Flow builds the whole onboarding checklist as tasks and hands each to the right person - IT for the laptop, me for the paperwork, the manager for day one - while the offer letter is generated with the new hire's details and sent for signature through DocuSign, which writes the signed status straight back to the record.
• One place, with guardrails Excel never had. Field-level security hides salary from anyone who should not see it, permissions decide who sees which records, and field history quietly logs who changed a status and when. Nothing gets overwritten, and nothing hides in a forgotten tab.
• A door employees can open themselves. An Experience Cloud portal lets staff raise HR requests as cases, track their onboarding, and read policy articles from a knowledge base before they ever need to message me.

The Part I Did Not Expect: an HR Agent

This year we added an Agentforce HR agent, and it changed the shape of my week more than anything else. Half my day used to be the same three questions: how much leave do I have left, how do I change my direct deposit, what is the parental leave policy.

Now an AI agent answers those in Slack, where people already work - grounded in our own policy documents and knowledge articles, not made up. It handles the routine ones and only escalates to me when something genuinely needs a human. Salesforce says its own HR agent resolves the large majority of employee questions without a person, and I believe it, because my ticket pile is a fraction of what it was.

One Honest Thing About Salesforce and HR

I should be straight about something. Salesforce is not a Workday. It does not run payroll or benefits administration out of the box, and it is not sold as a core HR system. What it is, is a platform flexible enough to model exactly how our HR actually works, with automation and AI layered on top.

That is precisely why it fit us better than a rigid HR product: nothing was forced into someone else's idea of a process. Salesforce and Workday even announced a partnership in 2024 to pair Salesforce's AI and service layer with Workday's HR records, which tells you how the two are meant to sit together. For us, the Salesforce side was enough - and it is the same set of building blocks the Cloudsheer team assembles for clients every week.

What Actually Changed for Me

I never imagined a tool could change my day-to-day this much. Work that used to take hours now takes minutes, and it comes with far fewer errors. The small anxieties - did that email go to the right person, did I overwrite a row, where is that candidate's status - are simply gone.

It Changed How I Experience HR

Salesforce did not just simplify my work. It changed how I experience being in HR. The hours I used to spend on emails, IDs, and spreadsheets now go to the part of the job that actually needs a human: the people.

The best part is that none of this is exotic. It is Flows, templates, and records - the same building blocks Cloudsheer uses on client projects every day. If a repetitive, error-prone workflow is eating your team's week, it can almost certainly live in Salesforce instead. If you want to see what that would look like for your team, book a free call at cal.com/cloudsheer-consulting/30min.