Skip to main content
Families & communication

Messages, broadcasts, newsletters, and events

For center admins: how to reach families with email and SMS announcements, build and schedule newsletters, and manage calendar events with RSVPs.

Last updated About 1 month ago

Messages is Bloomily's communication area. Use the content type that matches the job, then choose its delivery channel separately.

Content type

Use it for

Delivery

Replies

Direct message

A conversation with one family

Bloomily conversation; family alerts depend on their settings

Yes — replies return to Messages > Inbox

Broadcast

A short, one-way update to many people

Email, text, or both

No conversation is created

Newsletter

A longer, formatted one-way update with photos and headings

Email

No conversation is created

Announcement

A recipient-facing notice in a staff or family in-app feed

In-app, often with a push alert

Not an admin email/text composer

Email, Text, and In-app are delivery channels. Newsletter is a content type, not a channel. Scheduled is a status, not another type.

Messages navigation

Location

Purpose

Availability note

Messages > Inbox

Two-way family conversations, triage, and follow-up

Visibility depends on messaging permissions and scope

Messages > Requests

Approve, reject, or resolve routed parent requests

Shown only when the feature is enabled

Messages > Broadcasts

Write short one-way updates and choose Email, Text, or both

Review recipients and channels before sending

Messages > Newsletters

Draft, preview, and send formatted email newsletters

Customer-facing send gate

Messages > Library

Reuse saved newsletter layouts and content

Opening or editing a template does not send it

Messages > Recipients

Manage additional newsletter contacts and groups

Managing a contact does not send a message

Messages > Settings

Configure texting, limits, quiet hours, and inbox routing

Organization-level configuration

All sends are customer-facing. Preview the rendered content, confirm the recipient count and delivery channels, and obtain any required approval before sending. Afterward, use the ledger's delivery evidence rather than the button click alone.

Send a broadcast

Use a broadcast for a closure notice, reminder, or other short update that does not need a reply.

  1. Go to Messages > Broadcasts and select New broadcast.

  2. Write the subject and message. For a long, formatted letter, use a newsletter instead.

  3. Choose the audience, such as all parents, selected rooms, or named recipients.

  4. Open Review & send and choose Email, Text, or both under How it reaches them.

  5. Review the reachable recipient count, exclusions, channel eligibility, and timing.

  6. Confirm only after the preview and delivery details are correct.

A broadcast creates no conversation. If families need to answer, start a direct message or tell them how to contact you in the broadcast.

Delivery depends on the selected channels, recipient eligibility, contact data, consent, quiet-hour rules, and provider result. Verify the resulting ledger state before saying a family received it.

Check who missed it

Open the broadcast row in Messages > Broadcasts or the broadcast's own record page and select See who missed it. Each row names the person, shows the address or number that was tried, and gives one plain reason, such as "No email on file" or "This email address does not exist," with a line on what to do next. The list covers every channel the send used, including a text that did not go through even when that same person's email arrived.

Create and send a newsletter

Use a newsletter for a longer update with formatting, photos, headings, links, or files.

  1. Go to Messages > Newsletters and select New newsletter.

  2. Create and save the private draft first; then open its full editor for audience, content, preview and sending.

  3. Add images, links, headings, and attachments as needed.

  4. Choose the audience and review the recipient count.

  5. Preview the rendered email before sending or scheduling it.

  6. Confirm the send only after the content and audience are correct.

Newsletters are delivered by email. They do not become direct-message conversations, and Newsletter should not appear as a delivery channel in history.

Where announcements fit

Staff and family surfaces may use Announcements for recipient-facing in-app notices or feeds. That word does not name the admin's email/text bulk-send tool. In Admin OS, use Messages > Broadcasts for short bulk sends and Messages > Newsletters for formatted email updates.

Events

Events and closure days belong in More > Calendar. Use a broadcast or newsletter when people also need a one-way reminder about an event; creating the event itself does not prove a reminder was delivered.

Best practices

  • Need a reply? Start a direct message instead of a broadcast or newsletter.

  • Keep channels explicit: Email, Text, and In-app describe delivery; they do not replace the content type.

  • Use the right length: Broadcast for short updates, Newsletter for rich long-form content.

  • Review evidence: Confirm recipients and rendered output before sending, then verify delivery status afterward.

Still need help?

Newsletter writes require an organization administrator, and outgoing content requires the appropriate announcements access and send gates. Messaging access alone does not grant sending permission. Parent conference booking remains available from Home > Conferences when offered.