Wanna know how I actually use CRM at the desk? Not the brochure version. The Tuesday version. People put Salesforce on a CV. CRM. Oracle. Zendesk. I put tools on mine too, when I can defend them. Then I sit down in Haarlem and do klantenservice in Polish and English. The logo on the login screen is not the work. The person on the line is.
I won't sell you a certification. A system does not calm a person. You do. The tool is only the drawer where the truth sits. If that drawer is a mess, the next agent starts from zero. That's on you. People don't want to be managed or processed. They want to be understood. A clean case note is one way you show that. A rushed status click is how you forget it.
Wanna know more? Here is how I set myself up. What I watch on every case. What I refuse to invent for your org.
What CRM actually is at this desk
CRM means customer relationship management. At this desk it is the book. Who called. What they asked. What you promised. What still hangs. Salesforce is one brand of that book. Oracle is another door into the same house. Zendesk. Freshdesk. The name changes. The job does not.
On a vacature they write Salesforce. Or CRM. Or "experience with ticketing systems." What they usually mean is simple. Can you open the record, find the person, and not invent a second story that contradicts the first.
I've worked where the system was heavy. Where a click took forever. Where three screens said three different things. I still stayed with the person on the line. I stay calm when others panic. I listen. I step in. I follow through. The system is the drawer. The person is why I opened it.
How I set myself up on day one
I'm not your Salesforce admin. I won't tell you which permission set to click. Every company builds a different house. This is how I set up my own desk inside whatever house they give me.
First week, I ask where the queue lives. Cases. Tasks. A shared inbox. Whatever they call it. I ask who owns a case when it is mine. I ask what "closed" means here. Closed for me is not the same as closed for the person who wrote. If those answers are fuzzy, I write them down and I ask again until they are not.
I find the search. Account. Contact. Case number. Order number. If I can't find a person in under a minute, I say so in the first week. Not in month three, when I'm already guessing and the customer has already repeated themselves twice.
I set the list views I actually use. My open cases. Waiting on customer. Waiting on another team. Escalated. Not seventeen folders I never open. If the view is empty and I know work is open, the filter is wrong. I fix the filter before I trust the green number on the dashboard.
Notifications matter more than people admit. Mail from the system. In-app badges. I turn on what I will answer. I turn off what is noise. If everything pings, nothing pings. I'd rather miss a badge than miss a human because I went blind.
Keyboard next. Shortcuts if they exist. Saved replies only for sentences I still mean every time. Never for empathy. Empathy that sounds like a template is worse than silence. If I can't mean the line, I don't save it.
I ask for a clean test account or a sandbox story if they have one. I click once on something I'm afraid of, with someone watching. Better a controlled mistake on Tuesday than a live one on Friday at four.
What to watch every single case
The person. Name. How they write. Are they tight. Did they already explain this twice. I read the last three notes before I type. If the notes are empty, I treat the case as new and I say that out loud. I don't see history here, so I will ask you from the start. That honesty saves more time than a fake "as we discussed."
The promise. Whatever I say on the phone, I put in the case. Date. Next step. Owner. If it is not in the system, it did not happen for the next agent. That is the rule I keep even when I'm tired. I own the outcome. The note is how I prove it.
The fields that lie. Status. Priority. Reason code. Sometimes the dropdown has no honest option. I pick the closest one and I write the real sentence in the note. The note is for humans. The dropdown is for reports. Both matter. The note matters more when someone is waiting.
Duplicates. Same person, three cases. I don't open a fourth because it is faster for my queue. I link. I merge if I'm allowed. I say which one is the living thread. Panic creates twins. Calm closes one door.
Hand-off. When I pass a case, I write what I already tried, what the person wants, and what I still owe them. "Please advise" is not a hand-off. It is a shrug in a suit. The next person should not have to reconstruct my afternoon from silence.
Attachments. Screenshots. PDFs. I name them like a person will search them later. Not IMG_4032. I check that the customer can see what I think I sent. Systems lie about "sent." I check.
Time. SLA clocks are real. So is a person at twenty to five. If I can't finish, I say what happens Monday. I put Monday in the case. Late is late. Then we fix the next step. The clock does not get to erase the human.
What I actually do in the screen
I open the account. I read what the last person wrote. If it is empty, I ask. I don't pretend I know. I write what I heard, in plain words, so the next person does not start from zero.
I own the outcome. Closed in the system means closed for them, not only for my queue. If I said I will check, I check. If I said Friday, I put Friday where someone else can see it. Panic does not move a backorder. Neither does a ticket with no note.
Salesforce will not do that for you. It will hold the date if you put the date. That is the whole trick. Oracle will not do it either. Neither will Zendesk. You still have to type the truth.
One more thing I watch: my own tone in the note. If I write like a machine, the next person will talk like a machine. I write as if the customer might read it. Because sometimes they can. And even when they can't, another human will.
When someone is loud, I don't hide behind the screen. I listen. I repeat what I think I heard. I say what I can do in the system today, and what has to wait.
Salesforce and Oracle, without the theatre
Salesforce at this desk is usually cases, accounts, contacts, sometimes a console with many tabs. Lightning. Classic. I don't care what they call the skin. I care that I can find the person and leave a trail.
Oracle can mean a different screen every company. Service. Order. Something finance owns. Same rule. Find the truth. Write it. Don't invent a field because the report wants a colour.
If a vacature stacks Salesforce, Zendesk, and "AI tools," I still ask in the sollicitatiegesprek: what does a normal Tuesday look like on that screen. If they can't answer, the tool list is decoration. I'd rather hear about queues, hand-offs, and what closed means than a row of logos.
What belongs on a CV
Put the tools you can defend in a sollicitatiegesprek. If you opened cases in Salesforce, say so. If you only watched a video, don't decorate the line. The first angry customer will find you. Same rule as languages. I already wrote how I write a CV for this job, if you want that walk-through.
Don't write "Salesforce expert" if you mean you can search and update a case. Write what you did. Cases. Orders. KYC. Mail. Phone. The person. The system name is enough.
In the Netherlands you will see klantenservice next to CRM on the same vacature. That is normal. They want someone who can talk and still leave a clean trail. Not a poet. Not a robot. Someone who owns the screen and still treats the human like a human.
What I will not tell you
I won't tell you which button is where in your company's Salesforce. Every org is different. I won't sell you a course. I won't pretend AI closed the ticket for you while you were away.
I can tell you how the work sounds from this side of the table. Haarlem. Klantenservice. A screen that sometimes lies. A person who is tired. You stay. You write the truth. You come back.
If you want practice without a live brand on the line, I built Biurko for that. My CRM for small firms: mail, phone practice, orders, invoices, training. It is a desk to learn on, not a miracle. The same rules apply. Write the promise. Own the close. Leave a trail another person can trust.
The rest of the desk
If you want the rest of the desk, it is here. How a first week starts with a person. What Polish and English at the desk actually means. How an order moves when someone is waiting. How I think about getting the work in the Netherlands. Troubleshooting without hiding behind a script.
Tools on the CV. Truth in the note. Calm when the queue gets loud.
I'm Patrycja Kozdrach. Nice to meet you. One practical thing: I do client service in Polish and English every day. Talk to me in whichever feels easier. If you write, write like a person.
How can I help you today?
I won’t sell you a poem. Customer service is hard. If you want someone who stays calm when it gets loud, knows the systems, and still treats the person like a person — write to info@kozdrach.com. I am in Haarlem. I reply.
If this helped: a gift, or support. One click. No subscription.