2.4Tools: CRM & ticketing software
The essentials in 30 seconds
- CRM = the relationship's memory: customer sheet (details, history, preferences), tracking, reminders — anyone takes over with no repetition.
- Tickets = lose nothing: categories, priorities, statuses, deadlines (SLA), queue reviewed daily — a ticket with no owner is lost.
- Logging = 2 minutes that save 20: facts + decision + dated next step after each contact, audited until reflex.
Threaded mini-case — Rania absent, the case goes on
Rania is away the day Karim calls back about his parcels. Her colleague opens the CRM sheet: 3 orders, ongoing incident (reshipment, Friday-noon deadline, free delivery), Karim prefers SMS, decision-maker = him. In 30 seconds of reading, he takes over with no repetition — Karim, won over, notices nothing. Meanwhile, the ticket queue is sorted every morning: categories, priorities, one owner per ticket.
Sequel to cases 2.1–2.3 — Rania's qualification and deadlines now live in the tools.
1. The CRM: the memory of the relationship
Customer record (contact details, history, preferences), tracking (exchanges, commitments, due dates), automatic reminders: the CRM lets anyone pick up a case without making customers repeat themselves. An empty CRM is an expensive filing cabinet.
2. Tickets: prioritise and lose nothing
Categories (technical, billing, delivery), priorities (blocking/urgent/normal), statuses (new/in progress/pending/resolved), SLA (deadlines per priority). Queue reviewed daily: a ticket with no owner is a lost ticket.
3. Log it: 2 minutes that save 20
After every contact: facts + decision + dated next step (3 lines). Colleagues, managers, yourself in 3 months: everyone finds everything. Logging is monitored (record audits) until it becomes reflex.
🔎 Concrete example — 🔎 Hands-on example — Handover with no repetition
Fiche Karim : 3 commandes, incident 03/24 (résolu, geste 30 €), préfère SMS, décideur = lui, échéance vendredi → collègue en renfort : lit 30 s, reprend sans question, client conquis
Takeaway: 3 lines × N contacts = total continuity.
Lesson: audit 5 records a week until it becomes reflex.
Section vocabulary
- CRM
- Customer Relationship Management: a tool centralizing each customer's information and history.
Simple example: Karim's sheet: orders, incident, SMS preference, deadline.
What it is not: an expensive binder never filled, oral memory only.
Reflex: before any customer callback, open their sheet first.
- Ticketing software
- A tool tracking each customer request (ticket) from opening to resolution.
Simple example: Karim's ticket: delivery category, urgent priority, in-progress status.
What it is not: requests tracked from memory, with no status or owner.
Reflex: every ticket = category + priority + owner + deadline.
- Traceability
- Tracking each request, guaranteeing nothing is lost and everyone knows where it stands.
Simple example: Karim's ticket statuses and milestones visible to the whole team.
What it is not: a ticket with no owner that nobody reviews.
Reflex: daily queue review, no exceptions.
- Customer history
- The trace of all past interactions, sparing customers re-explaining everything at each contact.
Simple example: “I see your call yesterday about the parcels…” — Karim won over.
What it is not: “Explain everything from the start” at each contact.
Reflex: 3 lines (facts, decision, next step) after each contact.
- Service continuity
- A colleague's ability to take over a request thanks to traced information (absence, handover).
Simple example: The colleague takes over Karim's case during Rania's absence.
What it is not: a case stuck because “Rania handles it”.
Reflex: every sheet must allow a 30-second takeover.
In practice — Hands-on - Use a CRM and ticketing tools
- Centralise each customer's information and history in the CRM.
- Track every request in the ticketing tool (opening, progress, handling, resolution).
- Use history so customers don't have to re-explain everything, and follow-up so nothing is forgotten (callbacks, deadlines).
- Make it a discipline: log every interaction rigorously (a poorly filled tool is useless).
Ready-to-say script — taking over an unknown case (30 s)
“Karim, I'm taking over your case: I see your 3 orders and the ongoing reshipment, delivery guaranteed Friday before noon with SMS tracking — is that right? Rania passed me everything, you have nothing to re-explain. I'll check where the carrier is and SMS you within the hour.”
Say it after 30 s reading the CRM sheet, before any question to the customer.
Copy-paste template — CRM sheet + ticket
CUSTOMER SHEET: name _______________ / contact _______________ / preference _______________ / decision-maker _______________
HISTORY (dates + facts): _______________
TICKET: category _______________ / priority _______________ / status _______________ / owner _______________
AFTER CONTACT: facts _______________ / decision _______________ / dated next step _______________
CALLBACK SCHEDULED on: _______________
Small business / tight budget
A well-structured spreadsheet (one customers tab, one tickets tab) suffices before moving to a real CRM as volume grows.
Absence / handover
Sheets must allow 30-second takeovers: that's the continuity test (Rania's colleague case).
High volume
Daily queue review + deadlines by priority (SLA): handle by priority, not arrival order.
SME in Algeria
Note contact preferences (SMS, call, WhatsApp) and the real decision-maker: it avoids many missed follow-ups.
✓ Best practices
- 3 lines after every contact.
- Owner per ticket.
- Daily review of the queue.
✗ Common pitfalls
- Empty CRM (oral memory).
- Tickets without priority (all urgent = none).
- Logging "when there's time".
Key takeaways
- The CRM centralises customer history; ticketing tracks each request from opening to resolution.
- Benefits: traceability (nothing is lost), history (customers don't re-explain), follow-up, continuity, management.
- History spares customers from re-explaining everything at each contact — a major irritant.
- Value depends on rigorous use: a poorly filled tool is useless, even misleading.
48h Challenge — apply tomorrow
After each contact, log 3 lines (facts + decision + dated next step) and assign an owner to each open ticket. Do the queue review tomorrow morning. 15 minutes is enough.
- I trace requests and history (customers never re-explain).
- Each ticket has category, priority and owner.
- I did the 48h challenge or scheduled its date.
Frequently asked questions
Why is it so irritating for customers to have to "re-explain everything"?
Because it makes them feel neither considered nor followed — one of the most frequent and worst-lived irritants. Imagine: a customer already explained their problem in detail on a first call, then calls back, or is transferred to another department, or writes a follow-up email… and is asked to start all over from scratch, as if the previous exchange never happened. It's perceived as a waste of time, a lack of professionalism ("don't they talk to each other? don't they write anything down?") and above all a lack of consideration ("I'm just an anonymous number, my case doesn't matter"). It can turn a patient customer into an annoyed one. Conversely, a professional who, thanks to history (CRM/ticketing), already knows the customer's situation ("I see you contacted us yesterday about…") immediately makes a good impression: customers feel recognised and followed, save time, and perceive an organised, attentive service. That's precisely one of the great contributions of customer-relationship management tools: centralising history so that any contact person can pick up the thread without making customers repeat themselves. It's also an omnichannel challenge (level 5): a customer moving from chat to phone doesn't want to re-explain everything. The rule: customers should never have to repeat what they've already said, because the company must remember it (via its tools). Avoiding the "please explain everything again" is one of the most concrete ways to improve the experience — and it rests entirely on well-kept tools and accessible history.
Does a small customer service (or small business) need these tools?
Yes, as soon as there is a minimum of volume and follow-up over time — even if the tool can be simpler than a large solution. The misconception would be thinking "we remember our customers, no tool needed". In reality, as soon as you handle more than a handful of requests, human memory isn't enough: you forget callbacks (so you drop customers), you can't retrieve the history of a returning customer (so they must re-explain everything), you no longer know who handles what (so requests fall through the cracks). For a small organisation, CRM/ticketing — even lightweight, even free to start — brings a proportionally huge benefit: traceability (lose nothing), history (treat customers well over time), follow-up (keep commitments), and continuity (a colleague can take over during absences). The time and customers gained far outweigh the effort of maintaining the tool. The key is to choose a solution suited to your size (not a lumbering machine for ten customers — a simple tool, even a well-structured spreadsheet at the very start, can suffice, before moving to real CRM/ticketing as volume grows) and above all to feed it with discipline (a half-filled tool is useless). The size of the organisation doesn't change the principle: managing customer relations well means tracking requests and history. What varies is the scale of the tool, not the need for one. Going without tools means resigning yourself to forgetting, making customers re-explain, and handling customers "from memory" — with all the failures that implies. Even small, a professional customer service equips itself with suitable tools.
Rania is away and Karim calls back. What does the CRM sheet allow?