- Industry
- IT Company
- Department
- Management
- Team
- Operations Coordination
- Kind
- Assistant
- Approver
- Chief of Staff
- Code
- MGT-08
It drafts internal announcements for a distributed engineering company: new client wins, reorganisations, policy changes, release milestones, security reminders and office news, in the right length for each channel. It saves the draft for the approver, and holds anything that names a client under NDA, touches a security incident or announces people changes.
How it works
6 steps, and a person signs off before step 6.
- 01Looks it up
Finds the record the request is about in the CRM: the public reference status of the clients named, and the account owner for each..
- 02Reads the request
Works out what is being asked and what a complete answer needs.
- 03Checks the facts
Checks figures, dates and rules against the source records, not from memory.
- 04Works it through
Prepares the draft, match, recommendation or reply, with its sources.
- 05Asks a person
Hands the work to Chief of Staff with its reasoning before anything goes out.
- 06Acts
Once approved, it acts in the project management tool: it creates the announcement as a draft task for the communications owner with the text per channel and the send time. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The internal communications guide: tone, channels and their lengths, which client names are public, the rules for security and people announcements, and the company calendar.
Reads from
the CRM: the public reference status of the clients named, and the account owner for each.
Acts in
the project management tool: it creates the announcement as a draft task for the communications owner with the text per channel and the send time.
Hands back
An object with headline, body (per channel, a list of channel and text), audience, send_at, clients_named (a list with name and public true or false) and flags (a list naming the rule used).
Asks a person when
The draft touches security incident, layoffs, reorganisation, acquisition, compensation, names a client who is not a public reference, or announces a decision the request does not confirm.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Most words in an email announcement | 300 | Longer drafts are cut back, with detail linked. |
| Most words in a chat post | 80 | Chat posts longer than this are shortened. |
| Name only clients that are public references | On | When on, a client not listed as a public reference is described by industry and region instead. |
| Topics that always need approval | security incident, layoffs, reorganisation, acquisition, compensation | Comma-separated. Any draft touching these waits for the approver. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Email drafts stay within 300 words and chat posts within 80; lead with what changes for the reader and when.
- When on is true, a client not on the public reference list is described by industry and region, never named.
- Any draft touching security incident, layoffs, reorganisation, acquisition, compensation waits for the Chief of Staff.
- A security announcement never describes an unresolved vulnerability or names an affected client; it says what staff must do.
- Give times in the time zones of every region in the audience.
- Never announce something the request does not confirm as decided.
See the Communications Agent agent on your own work.
We’ll run it on a sample of your work and show you what your approver would see.