How to communicate Coassemble feature releases to your customers 

When Coassemble releases new functionality, you may need to inform your own customers—especially when a change affects your partner integration. This guide explains what to expect from Coassemble release communications and provides a customer-facing email template plus best-practice principles you can adapt to your product voice.

What Coassemble sends partners

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

• Preview (2–4 weeks before release): Early notice of what’s coming.
• Reminder (1–2 days before Standard Release): Heads-up before the Standard Release server goes live.
• Standard Release confirmation (day of release): Confirmation that Standard Release is live.
• Controlled Release confirmation (~2 weeks later): Confirmation when the Controlled Release server catches up.

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

Note: This article uses current GTM server terminology (Standard Release and Controlled Release) with previous names shown in brackets where relevant.

What your customers and end-users 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 (Adaptable)

Use this as a starting point and rewrite it in your own brand voice. The example below is related to 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 in the UI.]
• 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 effective partner-to-customer Release Comms

• Translate—don’t copy—our voice. Coassemble release emails are written for partners. Your customers are end-users, so reframe the update in terms that matter to them with visual resources that are appropriate.
• 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 of our features are opt-in for Embed partners, so your team determines 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 vs. automatic—reply directly to the partner release email. We’ll get back to you quickly.