Customer training LMS: how to teach customers to use your product

A customer training LMS organizes product education. Choose it around the tasks customers need to practice, the way they reach the training and the evidence your team needs to review their learning. Softbook can host the academy with courses, a knowledge base and groups, while your team maintains the instructions and decides how to help.

What should a customer training LMS help you teach?

A customer training LMS should help customers practice a defined task, with instructions and a place for their work, so the teaching team can see which parts need another explanation. Pick one task first. A tour of every feature can leave someone with plenty of vocabulary but no clear idea of what to do when they return to work.

Imagine a fictional inventory application. Its users need to create an item, enter a sample stock quantity and read a stock report before using the application in their shop. Those are capabilities of the invented application in this example, not inventory-management features of Softbook. Softbook hosts the training about that application.

Write the intended task in plain language, including the starting conditions and the result a customer should be able to check after following the lesson. Use sample records. The customer should know which screen or output to inspect and what to do if the exercise produces something unexpected.

Choose an audience for the first course. A shop administrator who configures the application and a staff member who updates quantities may need different explanations, even when both work for the same customer. Document the difference before building the lesson tree, then use the guide to online course structure to organize the practice.

What belongs in a course and what belongs in a knowledge base?

Put a sequence that needs practice into a course, and keep instructions people need to look up later in a knowledge base. Make the distinction visible. Someone following an onboarding lesson and someone searching for one setting have different immediate needs, even if both open the academy on the same day.

In the fictional inventory example, creating the first item belongs in the onboarding course because a customer needs to follow the sequence and try it. A field-definition reference can live separately. The lesson can point to that reference without forcing the customer to repeat the whole course whenever a label needs clarification.

Keep reference pages narrow enough to maintain. A page titled “What the stock quantity field means” gives an editor a specific piece of content to review when the product changes. A long page mixing setup, billing and reporting creates several places where an old instruction can remain unnoticed.

Softbook’s knowledge base uses categories, subcategories and articles. Its article editor supports text, headings, lists and links, while video and audio uploads are not supported in those entries. Keep demonstrations in course lessons. A written reference can accompany the lesson, giving customers somewhere to return when they need to check a field definition after completing the initial practice.

How can you plan a small customer onboarding pilot?

Plan a customer onboarding pilot around one audience and one task, then record what you expect to observe before inviting participants. Keep the scope manageable. The following example uses 12 customers and a 20-minute practice session to test the instructions, without presenting those figures as a recommended benchmark.

These times belong to the rehearsal. They do not establish how long a real customer will need, and the example assumes that your separate product provides the sample workspace and actions described. Prepare that workspace before the course invitation so the lesson does not become an exercise in finding access credentials.

Ask a colleague unfamiliar with the draft to follow it, using the same starting conditions you plan to give the customers and noting each point where an instruction is missing. Let them finish. A writer who explains every unclear step aloud can conceal the very problem that the pilot is supposed to reveal.

Choose a small piece of evidence for the practical task. A fictional report screenshot or a written description of the result can help an instructor see what the learner attempted. Use example data. Ask only for material needed for the review, and explain what customers should leave out of their submission.

How do you set up customer training in Softbook?

Prepare the course, customer group and access route in Softbook, then test the complete learning experience through a participant account before inviting the pilot group. Start with the manual route. A small pilot can expose missing instructions before a developer connects enrollment to events in your own application.

Softbook is a platform for online schools: courses, sales, CRM, email and Telegram campaigns, and a website builder in one place. You can add unlimited students, and the platform takes no commission on your sales.

Payment-provider fees may still apply. The customer training solution describes the product-academy use case. Your team still needs to define the training program and maintain its instructions.

1. Build the practical lesson. Add the explanation, demonstration and practice task to the course. Keep the exercise tied to a result the customer can inspect in your product, with the starting materials clearly identified.
2. Create the customer group. Open Education and Student Groups, then add a group with a name that identifies the pilot. Open Students to add participants manually or import a CSV or TXT file, mapping the student fields before starting the import.
3. Check course enrollment. A student can belong to a group without being enrolled in a course. Use the group’s enrollment action for the intended course, then check that the participant account can open the correct materials.
4. Prepare the written reference. Enable the knowledge base in General settings, create the relevant category and add the article. Check its title, content and publication status before pointing customers to it from the lesson.
5. Set the help route. Name the person responsible for the pilot and explain where customers should send a question. If you create a group chat, test who can see it and make the intended audience clear in the invitation.
6. Run the participant check. Open the invitation, enter the course, follow the task and inspect the reference article. Check access with the actual group arrangement, then record the result and assign any corrections before inviting the rest.

Groups help organize participants and course access. Do not assume a group is a separate customer portal with independent settings, and check the visibility of any shared community space before using it for different customer organizations. The school management tools provide the surrounding controls for your team.

How should customers reach the academy from your product?

Define the enrollment route separately from the learning content, including which customer action should lead to access and who will maintain that connection. Write the rule down. A purchase, an invitation and an account setup can be different events in your product, so avoid treating them as interchangeable.

Check API availability for your subscription on the pricing page before planning the integration. Softbook supports adding students through an API, with a developer setting up the connection from an external website or application. That work needs a defined trigger. Give the developer the intended course and group, then agree how the team will check a new customer record and the resulting course access.

Rehearse the manual process first. Use a new customer example to check the invitation and a second example to see how your own integration should handle an existing person, without assuming duplicate handling or account matching works in a particular way. Document those decisions in the integration requirements.

The academy’s learning activity and your product’s usage data are separate. Finishing an onboarding lesson does not automatically prove that someone completed the task inside your application. If you need to compare the two, define the product event and the connection your team will build before promising that report.

What should you review after the pilot?

Review lesson progress together with the practice submissions and questions, then choose a specific instruction or access issue to improve. Keep the evidence close. A completion count can show where to investigate, while the submitted work may reveal that customers interpreted the same instruction in different ways.

In Softbook, open the course card’s gear menu and choose Course Statistics to inspect participant progress and completed lessons. Filter by the pilot group. Export the filtered records as CSV if the team needs a working review sheet, and add the relevant question or task observation beside the progress entry.

For the fictional stock-report exercise, a customer might finish the lesson but submit a report for the wrong sample item. Inspect the wording that explains item selection. Another person may understand the task but lack access to the practice workspace, which calls for a different correction before changing the lesson.

Track support questions with their context. You can compare the questions received during the pilot with the materials customers were given, but that does not establish a guaranteed reduction in support work or customer churn. The LMS selection checklist can help your team decide which records it needs for a repeatable review.

How do you keep product training current?

Give each lesson and reference article an owner, and review both whenever the product workflow they describe changes. Maintain a small change list. An updated label in the application can affect a screenshot, a practice instruction and the answer to a knowledge-base question at the same time.

Record the product version or review date in the team’s working notes, alongside the task covered by each material and the person who will check it. Test from the customer view. A corrected lesson should still lead to the intended reference, and both should describe the same workflow after the edit.

Start the next pilot with the revised material and the same observed task so your team can describe what changed without claiming that a different result has only one cause. Keep any product changes visible too. Before the next invitation, ask the owner to repeat the exercise with the sample item and confirm the access route.