You have deployed a clienteling tool. Your advisors are not using it.

He does not open it. The tablet sits behind the counter, four metres away. He would have to unlock it, search for a name whose spelling he is not sure of, scroll through two screens. While he did so the client would be waiting, and waiting ranks among the very first causes of disappointment that luxury clients cite. So he relies on his memory instead. He welcomes her well, he advises her well, he sells. That evening the record is not completed, because the day finished with a stock count.

Three weeks later the boutique manager opens the adoption dashboard and sees what most retail leadership teams see at this stage: a respectable login rate, a weak data-entry rate, and a handful of advisors who between them account for nearly every record that has been filled in.

This scene does not describe a flaw in a piece of software. It describes the gap between an available tool and a gesture that was never built.

A clienteling tool does exactly what is asked of it

This has to be said plainly before going any further, because the opposite conclusion would be both unfair and useless. The clienteling platforms on the market do their job properly. They unify a client history scattered between the till, the e-commerce site and handwritten notes. They make a preference consultable from the sales floor. They allow a personalised message to be sent without going through the marketing department. These are real functions, and many networks are not yet equipped with them.

What a tool does not do is decide at which moment in the conversation a record can be consulted without breaking the relationship. It does not decide which piece of information deserves to be noted and which is a detail with no future. It does not decide how to make contact again with a client six weeks later without giving the impression of chasing a sale.

Software transmits a capability, it does not transmit a behaviour. The clienteling tool adds to that limitation a difficulty most enterprise applications never face: it is used standing up, in the client's presence, within the very short time of a conversation. A desktop tool is consulted between two tasks, with no witness. Here, every second spent on the tablet is a second taken from somebody who is watching.

Why does adoption really stall?

The usual reflex is to treat the subject as a problem of getting to grips with the interface. A training session on the tool is scheduled again, the crib sheet is redone, a reminder is added to the team meeting. That generally produces a brief upturn, and then the curve falls back.

The reason is simple: advisors know how to use the tool. The interface is not the point at which things block. What they have never practised is the relational sequence into which the tool fits.

Three blockages come back, and none of them is technical.

The first is a blockage of tempo. Consulting a record while a client is speaking feels like taking your eyes off her. Nobody has shown the teams how to do it without opening up a silence, nor how to turn the act of consulting into a sign of attention in itself.

The second is a blockage of legitimacy. An advisor who reminds a client of a preference noted six months earlier is afraid of appearing intrusive. The border between attention and surveillance cannot be decreed in a charter: it is felt, and it is practised.

The third is a blockage of perceived value. Filling in a record costs time now for a benefit later, one that may well go to a colleague. Until the team has lived through the moment when a note left by somebody else rescues a visit, data entry remains an administrative task.

Accor's 3D training platform dealt with operational standards: documentation that was complete, current and available in a single gesture, which the teams were not opening. It is cited here because it isolates precisely the variable that is blocking your tool. What unlocked usage was neither a rewriting of the content, which stayed identical, nor an overhaul of its ergonomics, but the fact of having to use it in the situation in which it serves.

What has to be practised, in concrete terms

Adoption training that works is not about screens. It is about four decisions, and each one is built through repetition.

When to consult. On welcoming the client, during the fitting, after she has left? Each moment has a different relational cost, and the right answer depends on the type of visit. That is discovered by getting it wrong, not by hearing it described.

What to note. A size is useful. A planned trip is useful. A remark about the client's family can be precious or out of place depending on how it is reused. Sorting one from the other is a judgement, and a judgement is calibrated on cases.

How to make contact again. A message that recalls a real conversation has nothing in common with a message that revives a commercial opportunity. Advisors can tell the difference when they read it. They produce it far less easily.

How to pass it on. A record is written for a colleague who was not there. Writing for somebody else is a skill in its own right, and nobody works on it.

These four decisions have one thing in common: they are not learnt by reading a procedure. They are learnt by deciding, observing the consequence and starting again. That is the logic behind the clienteling programmes we design: short situations, playable between two clients, in which the advisor chooses and sees what her choice produces.

Picking up a deployment that has already launched

A tool already in place does not need to be relaunched. It needs to be accompanied by a practice scheme, and the order of operations matters.

Begin by identifying the two or three moments in the visit at which consultation or data entry ought to take place. Those are what become the situations to be played, not the features of the software. This work is done with boutique managers rather than from head office: they are the ones who know at which point in the flow a consultation is genuinely possible.

Then build sequences short enough to fit the rhythm of the boutique. An experience of eight to ten minutes slips into a lull in the day and can be replayed as often as necessary. That calibration is not a detail of format: it is what decides whether the practice takes place on the sales floor, or is deferred to a training slot that will never come.

What to look at to know whether the gesture is taking hold

A tool deployment is usually measured by the login rate, which is the least informative indicator of the set: it says that the application is being opened, not that a decision has been taken.

Three families of signal are worth more, and they have to be fixed before launch. The first come from the practice itself. A well-designed experience returns twenty indicators or more, in a GDPR-compliant dashboard, exportable to your LMS or to PowerBI: drop-off points, replay rate, time per sequence, results question by question. On this particular subject, the replay rate is the most eloquent of all. A sequence on making contact again that advisors replay spontaneously indicates that they find in it an answer to a real difficulty. A sequence played once and never taken up again indicates the opposite, whatever the satisfaction score.

The second come from the tool: the proportion of active advisors, records filled in relative to visits, the share of renewed contacts that result in a visit. The third can only be obtained by asking: boutique managers know which of their advisors consult a record without breaking the conversation, and at which moment they do it.

Cross-referencing the first two families genuinely answers the question posed. The usage signals from the experience say who has practised and what is resisting; the data from the tool says what has changed in the boutique. Taken separately, each one allows you to reassure yourself. Brought together over a period long enough to absorb seasonality, they say whether the behaviour has moved.

Two articles extend this one: clienteling training sets out the skills themselves, and clienteling beyond luxury shows how the discipline transposes outside the maisons. The underlying reasoning is developed in what a document cannot teach.

Frequently asked questions

Should you change tools if adoption does not take off?

Rarely. Before opening a new invitation to tender, check what was actually asked of the teams. If the only training they received was about the interface, the problem has not yet been addressed. Changing platform without building the gesture reproduces the same curve six months later, with a migration cost on top.

Should data entry be made compulsory?

It always ends up partly compulsory, and that is rarely what unlocks anything. An obligation produces records that have been filled in, not records that are useful: a first name, a size, a vague line. What changes the quality of data entry is the moment when the team sees that a note left by somebody else has rescued a visit. Making that moment happen in situation costs less than a control policy and lasts longer.

What should be done about the few advisors who account on their own for nearly every record?

Put them to work rather than hold them up as examples. A ranking displayed in a team meeting demotivates the others and explains nothing. Those advisors have found a moment for consulting and a form of words that work for them: the useful work consists of extracting those two things, turning them into situations the rest of the team replays, then checking that they hold in a boutique whose flow is different.

How many gestures can be installed at the same time?

Two, rarely more. A team asked simultaneously to consult at the right moment, to note the right things, to make contact again and to write for a colleague will install none of them. Choosing consultation during the visit and renewed contact after purchase, holding those for a quarter, then adding the rest, produces a visible result where the full ambition produces none.

Your tool is in place and the gesture is still to be built? Request a demo