How do I tell my customers about a Coassemble release?

What Coassemble sends partners before and after a release, what your own customers need to hear, and a template you can adapt.

Coassemble emails you a sequence of notices around every release that affects partner integrations. Take what matters to your end-users from those, translate it into your own product voice, and send it when your customers will actually see the change.

What Coassemble sends partners

For every release that affects partner integrations, you'll receive a sequence of partner emails:

• Preview, 2 to 4 weeks before release: early notice of what's coming.
• Reminder, 1 to 2 days before Standard Release: a heads-up before the Standard Release server goes live.
• Standard Release confirmation, day of release: confirmation that Standard Release is live.
• Controlled Release confirmation: confirmation when the Controlled Release server catches up. The gap between the two varies by release, so the confirmation email is the reliable signal rather than a fixed number of weeks.

For releases that don't affect your integration, you'll receive a short note so you're aware of the update.

This article uses current server terminology, Standard Release and Controlled Release, with previous names shown in brackets where relevant.

What your customers actually need to know

End-customers don't need every technical detail. They typically care about three things:

1. What's new: what can they do now that they couldn't before? Does something look different in their experience?
2. Whether they need to do anything: is it automatic, opt-in, or does it require a settings change?
3. What it looks like: a brief visual (screenshot or short GIF) can make the change instantly clearer.

Lead with these points. If deeper technical detail is needed, link to a follow-up resource rather than adding complexity to the announcement.

Customer announcement email template

Use this as a starting point and rewrite it in your own brand voice. The example below is about course creation.

Subject: New in course creation: [feature name]

Hi [customer name],

We've just rolled out a new feature in our course creation tools: [feature name]. Here's what it means for you.

• What's new: [One or two sentences describing the capability in plain language. Avoid jargon.]
• What changes for you: [Is this automatic or opt-in? If opt-in, link to where they can turn it on. If automatic, describe what they'll see.]
• Why we think you'll like it: [One concrete use case. Example: "If you've been struggling with X, this means you can now do Y."]

If you have any questions, reply to this email or visit our help centre.

Thanks, [Your team]

Principles for partner-to-customer release comms

• Put it in your own voice. Coassemble release emails are written for partners. Your customers are end-users, so reframe the update in terms that matter to them, with visuals appropriate to your product.
• Time your message to the customer experience. A message timed to Standard Release can confuse customers who won't see the change until Controlled Release. Send your announcement when your customers will actually experience the update. Many features are opt-in for Embed partners, so your team decides when they go live for your customers.
• Use your own examples. Tie the feature to customer workflows and outcomes rather than describing abstract capability.
• Keep it short. Most customers skim. Provide links for more detail instead of burying key points in long explanations.

When you need help

If you're unsure how to position a new feature for your customers, or whether it's opt-in or automatic, reply directly to the partner release email and we'll come back to you quickly.