Comms Hub
Internal Communications hub — Calendar, Compose, Newsletters, Campaigns, Triggers, and shared Audiences across Broadcast, News Feed, Surveys, and Recognitions.
MangoApps
Meet the agent
This app ships with a production AI agent — permission-aware, tenant-scoped, audit-logged, and governed by the Agent Development Lifecycle.
Comms Hub AI
One calendar across every channel · semantic search · gated scheduling.
Overview
Comms Hub is the internal-communications operating layer for MangoApps. 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.
Highlights
Capabilities
AI Authoring & Voice
-
AI Writer — generate, rewrite, and transform copy
-
Whole-issue AI draft from a one-line goal
-
Tenant-scoped Brand Voices trained on your own copy
-
AI hero-image generation for blocks
-
AI Audience Builder — natural language to a composition
-
Ask-AI Comms assistant — query upcoming sends, search content, schedule items
-
AI audio edition (podcast) generated per sent issue
-
Comms Grader — readability, bias, PII, inclusivity scoring
Newsletters (Publications & Issues)
-
Publications with nested, dated Issues
-
Block composer — text, image, hero, callout, button, divider
-
Dynamic blocks (open shifts, new hires, recognitions, courses, news, pulse, sites, events)
-
Blocks freeze at send time — content immutable after delivery
-
Email + in-app delivery channels
-
Public per-publication archive at /pub/<slug>
-
LinkedIn cross-post per issue
-
Reusable default block template cloned into every new issue
-
Schedule an issue to send at a future date and time
-
Send yourself a test issue before delivery
Calendar & Planning
-
Unified Comms Calendar across Broadcast, News Feed, Surveys, Recognitions, Newsletters
-
Annual Plan — 12-month editorial calendar from preset bundles
-
Idea Bank for day-to-day comms ideas
-
AI Planning Assistant suggests ideas
-
Promote an idea into a Campaign or a draft
Audiences
-
Composition over NotificationRecipientGroups (wrap / and / or)
-
Role refinement applied after composition
-
Rule-based membership (departments, locations, roles, users)
-
On-shift-at-location & within-radius audience types
Campaigns & Approvals
-
Multi-touch Campaigns wrapping comms items
-
Campaign KPI targets with a kickoff / end window
-
Ordered approval workflows with a reviewer role per step
-
Reviewer approve / reject queue
Triggers & Analytics
-
Event-driven trigger registry (onboarding, recognitions, policy, etc.)
-
Per-trigger throttle, quiet hours, and blackout respect
-
Per-recipient firing history with suppression reason
-
Issue open + click tracking (signed pixel + redirect)
-
Per-issue analytics dashboard with CSV export
Limits & Specs
-
Block types: 6 static + 8 dynamic
-
Brand Voice training: 3–10 samples, 50–5,000 words each
-
Public archive URL: /pub/<publication-slug>
-
Tier & License: Platform tier, license required (opt-in per business)
Use cases
Resources
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, recognitions, policy changes) without any webhook plumbing, and Brand Voices train on copy from your previous internal comms rather than generic web text.
Comms Hub doesn't replace Broadcast or News Feed — it plans and coordinates them. Those are single-message delivery channels; Comms Hub adds the newsletter primitive neither has (Publications and dated Issues composed from static + dynamic blocks) and overlays one editorial calendar that shows Broadcasts, Emergency Alerts, News Feed posts, Surveys, triggered comms, and newsletter Issues side by side (a single Comms Calendar pulls all of those source types together). Reach for Broadcast or News Feed to push one message; reach for Comms Hub to run a curated newsletter program and see your whole comms plan in one place.
Yes. From the pre-send panel you can send a test copy to yourself, choose the audience and any LinkedIn cross-post, then either send now or schedule delivery for a future date and time. If the publication uses an approval workflow, an issue can't be sent or scheduled until its latest draft is approved, and a contentless issue is blocked from test-send, review, and delivery entirely.
Every delivered email carries a signed open pixel and rewritten click-tracking links, recorded as per-recipient open and click rows. The per-issue analytics dashboard rolls up opens, clicks, and rates — including anonymous opens from the public archive — and exports the numbers to CSV. Analytics is an admin-only surface and is gated by the Analytics module toggle in Comms Hub settings.
Nothing — blocks freeze at send time. Delivery renders from each block's frozen payload, so a "this week's recognitions" block in a newsletter that already shipped keeps showing the recognitions that were live the moment you hit Send. Live data updates only affect drafts and not-yet-sent scheduled issues.
An admin creates a Brand Voice (a tenant-scoped Writing Profile), adds 3 to 10 samples of writing that sound like your company (50 to 5,000 words each), and analyzes it. The Writer can then apply that voice while generating or rewriting copy. Voices are tenant-scoped and never shared across customers.
Only when a Publication has its public archive enabled AND the Issue has been sent. URLs live at /pub/ (index) and /pub// (individual issue), with no authentication required. It is off by default.
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, and individual modules (Publications, Campaigns, Triggers, Analytics, and more) are toggled on per tenant in settings.