Comms Hub

Internal Communications hub — Calendar, Compose, Newsletters, Campaigns, Triggers, and shared Audiences across Broadcast, News Feed, Surveys, and Recognitions.

MangoApps

Request Demo

AI AGENT INCLUDED

Meet the agent

This app ships with a production AI agent — permission-aware, tenant-scoped, audit-logged, and governed by the Agent Development Lifecycle.

Best Fit

Comms Hub AI

One calendar across every channel · semantic search · gated scheduling.

Unified Comms Calendar, Cross-Channel Semantic Search, and Idea Backlog Discovery

Composes With

News Feed AI, Broadcasts & Alerts AI (Admin), Surveys AI, and Recognition AI

See full agent landing →

Overview

Comms Hub is the internal-communications operating layer for MangoApps Workforce. One calendar replaces the patchwork of newsletter tools, broadcast surfaces, trigger plumbing, and idea spreadsheets that comms teams stitch together today. Authors plan the year in the Annual Plan, capture day-to-day ideas in the Idea Bank, and draft Issues in a block-based composer that supports static text, dynamic data (open shifts, new hires, recognitions, course completions), buttons, callouts, dividers, and AI-generated hero images. The AI Writer drafts from a one-line goal and applies tenant-scoped Brand Voices trained on copy you already publish — so output sounds like your company, not like a generic model. Audiences are a shared primitive composed over existing notification recipient groups with AND / OR / wrap operations and optional role refinement, so the same target definition works for a newsletter, a campaign touch, and a triggered email. Approval Workflows route drafts through reviewer steps without leaving the app. Triggers fire event-driven comms with per-recipient throttle, quiet hours, and platform blackout respect built in. Newsletters can opt into a permanent public archive at /pub/; analytics roll up open + click activity (including anonymous archive views) to a per-issue dashboard with CSV export. Comms Hub is platform-tier and license-required — disabled by default, opt-in per tenant.

Platform

Highlights

One calendar across every internal-comms channel — newsletters, broadcasts, recognitions, surveys, triggers, ideas — instead of one tool per surface.

AI Writer + Brand Voices: generate drafts that sound like your company, not like a generic LLM, by training on sample copy from comms you already publish.

Annual Plan + Idea Bank give comms leads strategic and tactical horizons in the same product — bundle presets seed the year, ideas evolve into drafts.

Audiences as a shared primitive: the same group definition powers a newsletter, a triggered email, and a campaign — composed with AND / OR over existing recipient groups.

Newsletter blocks freeze at send time, so changes to dynamic data after delivery never alter what subscribers received.

Approval workflows with role-gated steps and a reviewer queue — drafts move through review without leaving the app.

Triggers fire event-driven comms with per-recipient throttle, quiet hours, and platform blackout respect built in.

Public newsletter archive (per-publication opt-in) gives every issue a permanent shareable URL; opens feed analytics anonymously.

Capabilities

Calendar & Planning

Unified Comms Calendar across newsletters, campaigns, triggers, and ideas
Annual Plan — 12-month editorial calendar from preset bundles
Idea Bank with AI Planning Assistant
Promote Annual Plan slots into draftable Ideas

Newsletters (Publications)

Publications + nested Issues with block-based composer
Reusable default block template per publication
Schedule, send-now, and archive lifecycle
Frozen blocks at send time — content immutable after delivery
Email + in-app channels
Public newsletter archive (per-publication opt-in)
Subject-line A/B testing

AI & Composition

In-product AI Writer (generate / rewrite / transform)
Tenant-scoped Brand Voices trained from sample text
AI whole-issue draft from a one-line goal
AI block-level rewrite
AI hero image generation
AI Audience Builder (NL → composition preview)
Comms Effectiveness Grader (readability, bias, PII, inclusivity)

Audiences

Shared Audience primitive across all comms surfaces
Composition over NotificationRecipientGroups (AND / OR / wrap)
Role refinement applied after composition
Legacy rule-based dynamic membership (departments, locations, roles)
Member count cache refreshed on definition change

Campaigns & Approvals

Multi-touch Campaigns wrap multiple Comms Items
Campaign theme + KPI targets
Configurable Approval Workflows with reviewer role per step
Reviewer queue with approve / reject

Triggers

Event-driven comms registry (onboarding, recognitions, policy, etc.)
Per-trigger throttle, quiet hours, blackout respect
Email + in-app channel toggles per trigger
Per-recipient firing history

Analytics & Tracking

Issue-level open + click tracking (signed pixel + redirect)
Per-issue analytics dashboard with top-clicked URLs
CSV export from analytics
Anonymous archive opens feed analytics

Limits & Specs

Pricing model: Per-employee, single SKU
Tier: Platform
License: Required (opt-in per business)

Use cases

Editorial calendar for an internal comms team of 1–5

Plan the year in the Annual Plan, evolve slots into Ideas, draft Issues with the AI Writer trained on your Brand Voice, route through Approval Workflows, send, and read open + click analytics — without leaving Comms Hub.

Frontline manager weekly digest

Create a Publication, define an Audience composed of all managers + above, set a weekly cadence, drop in dynamic blocks (open shifts, new hires, recognitions), and let the IssueDeliveryJob fan out at the scheduled time.

Onboarding nurture sequence

Wire onboarding-milestone Triggers (day 1, day 7, day 30) to email + in-app templates with throttle and quiet hours. Track per-recipient firing history to confirm new hires got every touch.

Policy update broadcast with mandatory acknowledgment

Compose an Issue, target a role-refined Audience (e.g., "all employees in California ∧ role: hourly"), require an approval workflow, send, and pull open + click rates from the analytics dashboard.

Public newsletter with permanent archive

Flip "public archive enabled" on a Publication and every sent Issue gets a stable URL at /pub/<slug>/<issue-slug>. Anonymous archive opens feed the same analytics rollups.

Resources

Comms Hub Overview

help-center

What Comms Hub is, who it is for, the key surfaces, and how to get started in your first hour.

Building your first Audience

help-center

Walkthrough of composition (AND / OR / wrap) and refinement, with examples for common targeting needs.

Brand Voices: training the AI Writer on your style

help-center

How to gather sample copy, run analysis, and apply a Brand Voice in the Writer.

Setting up a weekly newsletter

help-center

Create a Publication, pick a default block template, configure cadence, and schedule your first Issue.

Trigger reference

help-center

Every event the trigger registry supports, with example payloads, throttle defaults, and channel options.

FAQ

Comms Hub is internal — it knows your employees, departments, locations, roles, and shifts. Audiences are composed of real users and groups already in MangoApps, so you never sync a contact list. Triggers fire on platform events (onboarding milestones, policy changes, recognitions) without any webhook plumbing. Brand Voices train on copy from your previous internal comms, not generic web text.

Yes. Comms Hub is a platform-tier marketplace app that requires a license. It is disabled by default for every business; an admin opts in from the Apps Marketplace. Per-employee pricing, single SKU.

Members can read newsletters, see their inbox, view the public archive, and use the AI Writer if enabled. Authoring (publications, issues, audiences, campaigns), approvals, triggers, brand voices, and settings are admin-only by default. Per-app admin role lets you delegate Comms Hub admin without granting global admin.

Nothing — blocks freeze at send time. The IssueDeliveryJob renders from frozen_payload, so a "this week's recognitions" block in a newsletter that already shipped continues to show the recognitions that were live the moment you hit Send. Live data updates only affect drafts and not-yet-sent scheduled issues.

Admins create a Brand Voice (a tenant-scoped Writing Profile), paste 3–10 samples of writing that sound like your company (50–5000 words each), and click Analyze. The Brand Voice flips to "ready" with extracted style characteristics. The Writer dropdown then lets authors apply that voice during generation. Voices are tenant-scoped — never shared across customers.

Each trigger has per-recipient throttle (minimum minutes between firings), quiet-hours window, and a "respect platform blackouts" flag. Suppressed firings are recorded with the suppression reason so you can see why a trigger was skipped without losing observability.

Only when a Publication has `public_archive_enabled: true` AND the Issue has been sent. The Publication slug is globally unique. URLs are at /pub/ (index) and /pub// (individual issue). No auth required, no business identifiers leaked. Off by default.

Audiences in Comms Hub compose over the platform-shared NotificationRecipientGroup primitive — meaning any group that powers a Survey, Broadcast, or Recognition can also power a Comms Hub Audience without re-building it. Within Comms Hub, the same Audience can target a newsletter, a campaign touch, and a triggered email.