---
title: "How do I tell my customers about the course builder?"
description: "How to plan and word your own customer announcement for the course builder, including a template you can adapt and the points that are easy to get wrong."
canonical_url: "https://support.coassemble.com/articles/how-do-i-tell-my-customers-about-the-course-builder-TH8kJOWRuP"
md_url: "https://support.coassemble.com/articles/how-do-i-tell-my-customers-about-the-course-builder-TH8kJOWRuP.md"
---
# How do I tell my customers about the course builder?

> How to plan and word your own customer announcement for the course builder, including a template you can adapt and the points that are easy to get wrong.

Because the course builder is opt in, you control when your customers see it and what you tell them. Announce it when you actually turn it on for them, describe it as a new way to create courses rather than a replacement, and be clear that their existing courses are untouched.

## What do my customers actually need to know?

Three things, in this order:

1. **What is new.** They can build a course by describing it to an agent, and arrange screens from blocks instead of picking a fixed screen type.
2. **Whether anything changes for what they already have.** It does not. Existing courses stay where they are, open the way they always have, and keep their learner experience.
3. **What to do next.** Where the new option appears in your product, and whether it is on for everyone or a group.

Leave the flag, the API and the word "embeddable" out of it. That is your integration, not their experience.

## What is easy to get wrong?

**Timing it to our release rather than yours.** The course builder becomes available to you at a release, but your customers see it when you enable it. Announce on your timeline.

**Implying existing courses will move.** A course lives in the builder it was made in, and a migration mechanism is being worked on. If you say courses will move across, you are making a promise on a date nobody has yet.

**Announcing features you have not enabled.** The builder has toggles you control, including AI narrations, translations, Google Drive and OneDrive import, Loom recording and publishing controls. Describe what you have turned on.

**Forgetting the learner side.** Courses built in the course builder have a rebuilt learner view with sections, a progress bar and an outline sidebar. Courses built before it keep the old view. Your customers' own learners will eventually see both, so say so before someone raises a ticket.

## Customer announcement template

Adapt this into your product voice rather than sending it as is.

**Subject:** A new way to build courses in [your product name]

Hi [customer name],

We have added a new way to create courses in [your product name], and it is available to you now.

- **What is new:** Describe the course you want, or upload a document you already have, and an assistant builds it with you. Screens are made of blocks you arrange yourself, so you are not choosing a fixed screen type and fitting your content into it.
- **What happens to your existing courses:** Nothing. They stay exactly where they are, open the way they always have, and your learners see no change.
- **What to do:** [Where the option appears, and who has it.]
- **One thing to know:** Courses built the new way have an updated learner experience, with chapters, a progress bar and a course outline your learners can navigate. Courses you built before this stay as they are.

If you have questions, [your support route].

Thanks,
[your team]

## What if my customers ask when their old courses can move across?

Say a migration mechanism is being worked on and you will let them know when there is something to share. Avoid giving a timeframe. If a customer needs a course in the new builder now, the answer is to build it there.

## Frequently asked questions

### Should I announce it to everyone at once?

That is your call. Because `legacy` is set per builder session, you can enable it for a pilot group first and announce more broadly once you have seen how your customers use it.

### Do I need to explain that it is in public beta?

Decide based on how you have positioned it. Public beta means it is stable and ready for real work and will keep improving. If you tell customers, frame it as an invitation to give feedback.

### Where can I get help with positioning?

Email vip@coassemble.com. Include what you are trying to say and who you are saying it to, and we will come back to you.