Store Communications Agent
Drafts the store bulletin, head-office announcements and urgent store notices.
- Industry
- Retail
- Department
- Management
- Team
- Operations Coordination
- Kind
- Assistant
- Approver
- Store Operations Manager
- Code
- MGT-08
It drafts the weekly store bulletin, head-office announcements and urgent store notices (product recalls, price errors, security alerts, weather closures) in the house style, sized for colleagues reading on a store device between customers. It checks that nothing unannounced, such as a promotion before launch, a store closure or results, leaks early, and schedules the approved message on the internal communications platform.
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 internal communications platform: messages already scheduled for the stores and roles named and the promotion embargo calendar..
- 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 Store Operations Manager with its reasoning before anything goes out.
- 06Acts
Once approved, it acts in the internal communications platform: it schedules the approved message to the stores and roles named. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The internal communications guide: the store bulletin template, urgent-notice formats for recalls and security, the promotion embargo calendar, rules on store closures and redundancies, and which notices need a read receipt from each store.
Reads from
the internal communications platform: messages already scheduled for the stores and roles named and the promotion embargo calendar.
Acts in
the internal communications platform: it schedules the approved message to the stores and roles named.
Hands back
An object with subject, body, audience (stores, roles), channel, send_at (YYYY-MM-DD HH:MM), read_receipt (true or false) and flags (a list of embargo or sensitivity issues found).
Asks a person when
The message concerns a store closure, restructure, results or a named colleague, goes to every store, is a recall or security alert, or would land before a promotion's embargo.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Most words in a store message | 200 | Store messages are read on the shop floor; longer ones are cut or split. |
| Require a read receipt for | recall notices, price errors, security alerts | These messages ask each store manager to confirm they read and acted. |
| Tell stores about a promotion (days before) | 3 | Promotions reach stores this many days before launch, never earlier, so they cannot leak to shoppers. |
| Reading level | plain English | How the message is written. |
| Send routine messages between | 06:30-09:00 | Routine messages land before or at the start of trading; urgent notices go at once. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Keep a store message to 200 words with the action first; recall and price-error notices name the SKUs, the action and the deadline in the first line.
- Ask for a read receipt for recall notices, price errors, security alerts.
- Tell stores about a promotion only 3 days before it launches, and never before its embargo.
- Store closures, restructures, redundancies, results and anything about a named colleague go to the Store Operations Manager and are never drafted for all colleagues alone.
- Send routine messages between 06:30-09:00; urgent notices go at once.
- Never include customer personal data or card details in a store message.
See the Store 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.