Comms: internal newsletter that captures the actual week

A communications director told us her internal newsletter had a 12% open rate and a 0.5% click rate. The newsletter was beautifully formatted. It was also generic — the same template every week, padded with whatever announcements people had submitted, rarely capturing anything that actually happened.

The internal-newsletter AI employee writes what happened. It reads the org's signals — wins, decisions, milestones, questions — and produces a newsletter people read because it tells them something they didn't know.

The shape of the role

Title. Comms AI — Internal Newsletter Specialist.

Mission. Assemble a weekly internal newsletter capturing real organisational moments. Open rates and engagement track the change.

Outcomes. Open rate, click rate, employee survey on internal-comms quality.

Reports to. Head of Comms or VP People.

Tools. Slack/Teams read access for major channels (with appropriate permissions), commit/PR data, customer-win data, calendar integration for major meetings, voice eval for the company's tone.

Boundaries. Drafts and assembles. Comms director reviews and edits. Doesn't publish without approval.

What "actual" sounds like

Most internal newsletters say things like "Our values in action this week" or "Spotlight on the engineering team." The agent's drafting goes to the specifics:

"We shipped the new export feature on Tuesday. Three customers had asked for it; one used it within 4 hours of release."
"The Q2 OKR check-in moved one objective from 'green' to 'yellow' — not because we missed, but because the customer cohort changed shape and we're recalibrating. Notes here."
"Three new hires joined this week (intros below). Notable because we hired two of them through referrals from former coworkers — the strongest signal that current employees still recommend the company."

This level of specificity is what makes the newsletter readable. It also requires the agent to read the org's signals broadly — not just whatever announcements got submitted.

Source aggregation

The agent's source aggregation is the core value:

Slack/Teams highlights. Major announcements, meaningful threads, milestones celebrated.
Engineering wins. PRs that shipped notable work, with context (not just titles).
Customer wins. New logos, expansion deals, advocate stories.
People moments. New hires, role changes, anniversaries, kudos.
Company decisions. OKR updates, strategy adjustments, leadership-team decisions that affect the org.
External milestones. Industry events, press, awards.

The agent surveys the week and assembles. The director picks what makes the cut.

Tone calibration

Internal voice differs from external voice. Most companies want their internal comms to be:

Honest. Not corporate.
Specific. Not generic.
Brief. Newsletters that take 5 minutes to read get read.
Two-way. Open to feedback, not broadcast-only.

The voice eval captures these dimensions with paired examples. Drafts that don't pass don't reach the director. The team's voice survives the agent's drafting.

Editorial review

The director reviews the draft. Common edits:

"This story is too detailed; trim."
"We can't share this externally, but it's fine internally — keep."
"This shouldn't be in this newsletter; route to the leadership-only channel."
"Add a question prompt at the end; we want feedback on this."

Each edit feeds the eval. Within two quarters, edit volume drops to fine-tuning rather than rewriting.

Distribution discipline

The agent doesn't auto-publish. The director:

Reviews the draft.
Edits.
Approves.
Schedules the send.

For sensitive content (a personnel change, a strategy shift), the director may also route through HR or Legal before send. The agent's drafts include a sensitivity-flag pass to surface items that probably need additional review.

What this changes

A team running this AI employee for two quarters:

Open rates climb from 10-20% to 50-70%.
Click rates climb materially.
Internal-comms NPS rises.
The newsletter becomes the place people learn what's happening in other parts of the org.

The compounding effect: cross-functional awareness improves. Silo'd teams discover each other's work. Decisions get communicated more reliably.

What we won't ship

Auto-publishing. Director approves every send.

Sharing private channels' content. Privacy boundaries respected at every step.

Reposting external customer praise without the customer's permission.

Personnel decisions ahead of the affected employee being told.

The KPIs the comms director watches

Open rate.
Click rate.
Internal-comms NPS in employee surveys.
Time spent reading (where measurable).

If the third metric doesn't move, ask employees directly what's missing. The agent's source aggregation may have blind spots.

How to start

Run the agent for one month, in parallel with the existing newsletter. Director compares. Switch primary drafting to the agent. Track the metrics for a quarter.

Close

The internal-newsletter AI employee is a teammate whose job is to surface what's actually happening so the comms director can decide what to share. The newsletter improves because the source material improves. Open rates rise because the content rewards opening. Cross-functional awareness compounds.