Communications

Communications is a licensed marketplace app. It is disabled by default and an administrator enables it per tenant from the Apps Marketplace — there is no automatic org-wide rollout.

A Post is social content. An Announcement is operational content that ranks above social. A Must-Read is an operational post that requires a persistent acknowledgement and carries a mandatory expiry — after the window closes it is archived and drops off the active feed. A Break-through leaves the feed entirely and delivers on email, SMS, and voice, escalating until it is acknowledged. Social content can never be made Must-Read, so acknowledgement cannot be forced on water-cooler chatter.

Every message goes to Everyone or is scoped to an audience. Audiences resolve from data MangoApps already has — departments, locations, roles, job titles, shift assignments, named users — and can be composed with AND / OR / wrap logic. The same audience serves a feed post, a break-through, a newsletter, and a campaign touch. You see an estimated reach before you publish, and the recipient list is frozen as a snapshot at publish so the compliance roster cannot drift afterwards. Who may post to Everyone is an admin policy.

The send is refused. Recipients are resolved immediately before the state transition, and if the audience resolves to nobody the message is not marked published or sent — it stays editable and tells you which audience needs attention. This applies to feed posts, break-throughs, scheduled and recurring sends, the API, and newsletter issues. A message is never reported as delivered when nobody received it.

No. Every AI capability in Communications produces a draft. Drafting, rewriting, channel-native copy, whole-issue newsletter generation, and the Ask AI admin assistant all stop at a draft that a person must explicitly confirm. There is no autonomous publishing or sending, and no setting that enables it.

There are two. A read-only help assistant answers questions about how Communications works and is available to everyone who can use the app. An admin assistant helps communicators draft and schedule, and is limited to administrators — every write it makes is a draft and requires confirmation. Publishing, cancelling, approving, and newsletter sending are deliberately not available to either assistant.

Partly, and we would rather be precise about it. Break-through messages support per-recipient translation into each recipient's language, with preview, edit, and stale detection. Feed posts have a reader-side translation service in the codebase, but there is no admin or reader setting exposed for it yet, and newsletter blocks are only partly covered. Treat full multilingual reading as not yet available.

Yes. Admins can enable or disable comments and the whole discussion layer, curate which of the 14 reactions are available (2–12), and auto-close discussions after an inactivity window. Users can report a comment; the report and reason are captured in an audit log, though it does not currently route to an admin review queue. Individual users can mute a post to silence their own notifications without leaving the conversation.

Not today. A send-time predictor exists in the codebase but is not wired into the send flow, so the product does not recommend or apply a send time. Quiet hours, per-trigger throttles, and blackout windows are respected for triggered communications.