Do I need a CRM alongside my webshop?

Your webshop knows what someone ordered, not what you discussed with them. As long as all your contact is about orders and you close questions the same day, you can do without. The moment you make commitments that must be honoured later, or the same customer contacts you through multiple channels, you're missing contact history your webshop doesn't keep.

What's the difference between a CRM and a customer service system?

A CRM is organised around the customer and the relationship; a service system around the question and how it's handled. In a CRM you open a company and see contacts and open opportunities. In a service system you open a conversation and see the status, the timer and the customer alongside. They overlap on the customer card and differ in what happens in them daily.

Can I connect my existing CRM?

Usually yes, and the question that matters then is which side leads. If you have a sales team living in the CRM, keep company and contact details there and let the service system read along. Write down per field which side may edit, because two systems that can both write will diverge within a month.

How do I prevent duplicate customer cards?

Don't match on email alone. Phone number, order number and postcode with house number are usable together to recognise two cards as the same person. More important still is that merging is easy: as long as it's manual work it won't happen, and the number of duplicates grows every month.

CRM · Customer Relationship Management

What is a CRM and what belongs in it?

A CRM stores who your customers are and what you agreed with them. The value isn't in the storage but in what comes out of it during a conversation.

In short

A CRM, in full Customer Relationship Management, is the system where you record who your customers and contacts are, what contact you had with them and which agreements are open. It differs from a customer list in keeping history: not just current details, but what was discussed with whom and when.

Which fields do you actually use?

A CRM rarely fails from too few fields. It becomes unusable from too many. Every field someone has to fill is time per contact, and fields nobody reads get half-filled within a month. Half-filled fields are worse than empty ones, because you end up filtering on them by accident.

The test per field is simple: which decision do you make differently when this field is filled? If you can't name that decision, the field doesn't belong.

Identity: Name, email, phone number and company. This is what you match an incoming conversation to an existing customer on.
History: Every earlier conversation, across all channels. This is the field agents read most often in practice and the one that's rarely set up deliberately.
Agreements and commitments: What was promised to this customer, by whom and until when. Without this, you get the situation where the second agent doesn't know the first one's commitment.
Orders or contracts: Usually not in the CRM itself but through a connection with your webshop or ERP. What counts is that it's visible on the customer, not where it's stored.

Why a CRM without customer contact runs empty

A CRM agents have to update separately gets updated as long as someone is watching. The moment it gets busy, it's the first thing dropped. That's not a discipline issue: updating gives the person filling it in nothing, and the benefit goes to someone else, later.

A CRM that fills from the work itself does keep up. Every email, chat and call lands on the customer automatically. The agent does their job and the history appears as a by-product.

That's also the sharpest question when choosing a CRM: how much of the content appears by itself, and how much does someone have to type?

Why a sales CRM rarely fits customer service

The well-known CRM systems are built around an opportunity: a deal moving through stages to won or lost. That model fits a sales process, not a customer asking where their parcel is. That question has no stage and no value, only a status and a waiting time.

Teams that try anyway rebuild a pipeline with stages like Waiting on customer and Resolved. It half works: you miss the response timer, the channel connections and reporting by topic. What's left is a list of cards.

When do you have two, and how do you keep that workable?

Many companies have a sales CRM plus a customer view in their service system. That's not a mistake as long as it's clear which system is the source of what. Usually: opportunities and contracts in the CRM, contact history and open questions in the service system.

It goes wrong when both systems edit the same data without an agreed direction. Then you get a customer with two email addresses, two phone numbers and two versions of the answer to whether they're still a customer. Pick a source per field and let the other side read along.

CRM or customer contact system?

	CRM	Customer contact system
Centres on	The relationship and the opportunity	The question and its handling
Unit of work	Contact, account, deal	Conversation or ticket
Time	Stages without a clock	Response time and SLA
Channels	Usually email, sometimes calls	Email, chat, phone, social
Who uses it daily	Sales and account management	Customer service

If you sell complex processes with multiple touchpoints, you need a CRM. If you mainly handle questions about orders that already exist, you need a customer view attached to conversations, which is something else. Many teams have both and that's fine, as long as you know per field which system is the source.

Where it goes wrong

Free text fields where a list belongs

A field called Sector where everyone types their own gives you twenty spellings of the same thing. Filtering becomes impossible and nobody notices, because the list isn't empty but unusable.

Duplicate customers from a second email address

If someone orders privately and for work, you get two cards each with half the history. Match on more than email alone and make merging a one-click action.

Notes only the writer understands

"Called, it's fine" doesn't help the next agent. Write down what was agreed and until when it holds, or turn it into a task with a date.

Keeping customer data without a retention period

Personal data you no longer need is a liability under the GDPR, not an asset. Define per data type how long you keep it and make sure deletion is actually possible.

What to do this week

Open five customer cards of customers who had contact last month and see whether you can tell what was agreed last time without searching further. If you can't, that's your first problem, and no extra field fixes it. Then look at which fields are empty on those five cards: nobody fills those any more and they can go.

What this looks like in a system

In Cuego the customer card is the conversation seen from the other side. Every email, chat and call lands on it automatically, together with orders from your webshop, returns, tasks and appointments. An agent opening a conversation sees what happened before without looking anything up. If you already run a CRM, Cuego can use it as a source instead of replacing it.

CRM