The client has received the materials. When will they actually use them?
Plan the client's first real use of delivered materials: choose a task, remove obstacles and agree the limits of support.
Article language: English

In this article
Description: Plan the client's first real use of delivered materials: choose a task, remove obstacles and agree the limits of support.
The materials have been accepted, the invoice received and everyone has said thank you. A month later the client asks for the file again. Sometimes the message really was lost. Sometimes the file was there all along, but nobody decided which upcoming task should use it instead of the old way of working. A folder can preserve a project's output much longer than people remember why they ordered it.
Plan first use as a specific event in the client's organisation. Who will open the material, for what task, using which data and with whose approval? A provider can help prepare such a trial. They do not, however, manage another company's employees and should not promise implementation of a change whose conditions they do not control.
What should the client do after acceptance?
Distinguish delivery, acceptance and use. Delivery means the correct version has reached the agreed location. Acceptance confirms that agreed acceptance conditions have been met. Use begins when someone applies the result in their work. These events can happen on the same day, but none automatically follows from the previous one.
In a fictional example, a service company commissioned an enquiry qualification scheme: questions for the customer, three possible next paths and a note template. The manager accepted the work. The team still handles enquiries as before because nobody chose a first case to take through the new route. The author sends the instructions again, although their absence is not the obstacle.
A useful first result might be: an employee qualifies one new enquiry, identifies missing information and passes it with a note to the right person. They do not yet need to transfer the entire archive or cover every exception. They need a real case within the agreed scope and a way to consult someone about uncertainties.
The Multichannel Customer Onboarding study examined initial contacts of customers at one financial company and their later relationship with it. The authors note the limitation to one company and sector. We do not derive a deadline by which every B2B client must begin using materials. The useful idea is to treat the initial experience as a separate phase rather than reduce it to a welcome message.
Name the task in the client's language. “Activate the qualification process” may mean nothing to the person answering the phone. “For the next standard enquiry, check three conditions before promising a quote” describes an action. Only then choose the screen, document or meeting that will help.
If the client cannot identify a use situation, return to the purpose of the purchase. Perhaps the material was needed only for a particular event that has already passed. Perhaps the purchase was meant to prepare a future possibility rather than an immediate change. Before scheduling a trial, establish whether use makes sense now.
Who at the client can start the first trial?
Choose someone able to provide the conditions: time, a case to handle, access and a decision on the permitted scope. The person approving the purchase may have no direct influence on the team's daily work. A user may understand the material but lack permission to depart from the old procedure. Adding both people to every message is not the solution.
In the example the manager chooses an enquiry and agrees that the employee prepares the qualification, while a supervisor still approves the deadline and price. The provider explains the scheme's logic and takes questions about its content. They do not decide on the manager's behalf what offer the company should send its customer. This division reduces the risk of confusing help with taking over responsibility.
Record the agreement in a short message naming the task and review date. Confirm it with the person who will actually do the work, not only the purchaser. When several people handle the purchase and later service thread, shared handling of one enquiry (in Polish) can help. A message to the right company is not always a message to the right person doing the work.
Do not equate this with onboarding an employee to company knowledge (in Polish). Here people know their work and organisation. The tool or way of performing a selected part changes. Additional basic training may be unnecessary, but people do need to know exactly what they may do differently and what remains unchanged.
Before the trial, also ask about the owner's absence. If the date falls during the manager's leave, who will answer an exception? A complex cover structure is unnecessary for one piece of material. Agree whether the task waits, goes to another person or returns to the old route with the reason recorded.
How do you identify an obstacle before sending another reminder?
When the first-use date passes, ask about the last specific opportunity. Was there a suitable case? Did the person doing the work know about it? Did they have the current version? Could they act without further permission? These questions are more useful than a general “how is implementation going?”, which invites an equally general answer.
The GOV.UK guide to encouraging use of an online service recommends investigating why people choose other routes and not hiding help outside the digital channel. It concerns public services and does not prove the effectiveness of a particular B2B process. It does suggest a reasonable direction: establish the reason for behaviour before increasing communications.

Different causes lead to different decisions. No suitable case calls for postponing the trial. No access calls for restoring the right access. An unclear qualification condition calls for correcting the material. A contradictory instruction from a supervisor needs agreement on the client's side. One reminder with the same attachment fixes none of these four situations automatically.
In analysis of work waiting for the client (in Polish), identify the missing contribution and its effect. Here too, record what prevents the trial and who can change it. Do not label the client “disengaged” if nobody provided the conditions needed to do the task.
Prepare a small conversation card, not another questionnaire running to many pages:
- Which first case was meant to take the new route, and what actually happened to it?
- At what point was help or approval needed?
- Does the obstacle concern the material, access, a decision or available time?
- What will we change before the next trial, and who will confirm it?
If the material needs correction, describe the specific passage and intended effect. If the client also asks for an entire additional process to be designed, separate that from removing an obstacle within the accepted scope. Without this boundary, every post-purchase conversation can become a new project hidden under the word “help”.
How can you tell that use was real?
Opening a message, downloading a file and attending a demonstration confirm contact with the material. They do not confirm that the task was done. For the qualification scheme, evidence is a completed note and a decision on what happens next to the case. It can be checked using agreed, suitably prepared material without passing all customer correspondence to the provider.
Intercom's checklist documentation distinguishes manual completion from automatic completion based on events and user attributes. This is a feature of a particular tool. Even such an event must be related to the task's purpose: completing a presentation may confirm that instructions were viewed, but not that a later enquiry was qualified correctly.
Agree evidence sufficient for the purpose. For simple material, a conversation about one completed case may suffice. For a regularly used tool, another case without step-by-step guidance will be needed. Do not require detailed reporting of every movement merely because it is technically possible.
Also check the result “this cannot be qualified using the standard scheme”. Correctly identifying an exception can be a successful first use. The material should help people take the right next step, not produce a positive answer every time. Record who receives the exception and what information should accompany it.
After the trial separate two questions: could the person use the material, and did the material help with the task for which it was ordered? Someone can efficiently complete a form that helps nobody. They can also reach a useful result even though the instructions need simplifying. The distinction shows whether to improve the explanation, the solution's scope or the organisation of the work.
Do not directly compare a team that had one opportunity to use the material with a team handling dozens of suitable cases. Record opportunities, attempts and reasons for skipping them. This organises observations; it is not an automatic effectiveness measure. If there were no opportunities, non-use does not prove rejection. If there were opportunities and the team chose the old method every time, discuss that decision.
Also agree which version is the basis for the next trial. Changing a qualification condition may make the example used in the demonstration outdated. Point the change out to people using the material and check whether old links lead to the current version. Do not make them compare whole documents to find one important difference. A short note about the changed condition helps them return to the task after a break.
Do not turn the first trial into promotional material without a separate agreement. The client may agree to discuss the task but not to disclose case data, the result or the company's name. To improve instructions, a description of where someone got stuck and a suitably prepared excerpt are usually enough. Using the story on a website is a different decision from providing post-purchase help.
How much help is included after the service ends?
Before acceptance, agree where questions go, the period of availability and the kind of support. Explaining an unclear sentence in the material differs from conducting the team's first customer conversation for them. The choice between an individual and a group service (in Polish) should also follow from the task: a shared demonstration meets different needs from discussing a confidential case.
If the issue is presentation itself, first-step instructions on the website (in Polish) may help. They can connect version identification, the task and a route to help. They cannot replace the manager's decision about when the team will use the new method. The site explains the action; the client's organisation provides the opportunity to do it.
Aeneia Design can design that route on a site: the right materials after purchase, a clear first step and contact appropriate to the question. The scope must be agreed with the service owner, who approves the content and support rules.
At the end of the first trial, name the next step without promising full implementation. It may be independent use on another case, correction of one explanation or a conscious decision to defer the solution until conditions change. The last can also be an honest result. Delivered material does not become useful merely because it is sent again, even if the attachment has an exceptionally persuasive name this time.








