Staff hear about an AI agent long before it goes live, usually through rumour. A staff communication plan for an AI agent rollout replaces rumour with a schedule: who needs to know what, when, from whom, through which channel, and how they can raise concerns. The template and a filled sample follow.
What should a rollout communication plan achieve?
Three things. People understand what the agent will and will not do, in their own work. People know what changes for them, including any change to their role or workload. And people know how to raise a problem, with the assurance that raising it is welcome. Each stage of train, shadow, certify, widen gives a natural moment to communicate.
The plan is not a marketing campaign. Staff can tell when they are being sold something. Plain, early, specific information builds more trust than enthusiasm. The wider approach is covered in how to communicate an AI agent rollout to staff and how to get staff to accept AI agents.
When should you use it?
Start it when the decision to pilot is made, not when go-live is near. Map it to each stage of the AI agent deployment plan: pilot, shadowing, certification, each widening. Include a message for the case where things go wrong and the agent is rolled back; the rollback plan should reference it.
Staffing changes need their own care. If the agent will take volume that people used to handle, plan the conversation about roles alongside capacity planning for AI agents, and involve HR before any announcement.
How do you fill in each field?
- Audience is specific. "Staff" is not an audience; "billing handlers in team B", "approvers", "team leads", "customer-facing staff in other teams" are.
- What they need to know is written from their side. Handlers need to know what the agent drafts and what they must check. Approvers need to know what they will see in the held queue.
- Message owner is the person they trust for that message, usually their own manager, not a project team.
- Channel fits the message. Role changes need a conversation, not an email.
- Feedback route gives a named person or channel, and says what happens to feedback.
- Timing ties each message to a deployment stage.
The template
| Field | Guidance |
|---|---|
| Message ID | Reference |
| Stage | Decision, pilot, shadow, certify, widen, rollback |
| Audience | Specific group |
| What they need to know | Key points from their perspective |
| What changes for them | Tasks, tools, targets, roles |
| Message owner | Person delivering it |
| Channel | Team meeting, one-to-one, briefing, written note |
| Timing | Date or stage trigger |
| Questions expected | Likely questions with answers |
| Feedback route | Named person or channel |
| Follow-up | When and how feedback is answered |
A filled sample
A hypothetical bank's mortgage servicing team, four messages.
| ID | Stage | Audience | What they need to know | Owner | Channel |
|---|---|---|---|---|---|
| M-01 | Decision | Servicing team | We are piloting an agent to draft replies to overpayment and payment date queries. It will not send anything; you will. No roles are changing during the pilot. Six volunteers needed | Servicing manager | Team meeting, then written note |
| M-02 | Shadow | Whole servicing team | The agent will work alongside you on live work for four weeks. You will see nothing different. We will compare its work with yours and share what we find | Servicing manager | Team meeting |
| M-03 | Widen | Approvers | From next month, payment date changes up to the agent's limit will be completed by the agent. You will approve anything above the limit or flagged. What you will see in the held queue, and what to check | Head of servicing | Briefing with walkthrough |
| M-04 | Widen | Servicing handlers | Simple date changes will no longer reach you. Your time goes to arrears, complex cases and quality checks. Training dates attached | Servicing manager, with HR | One-to-ones, then team meeting |
Questions expected for M-04: "Is my job at risk?" Answer prepared with HR, specific and honest about what is and is not decided. Feedback route for all messages: a named team lead and a monthly open session, with answers posted to the team page within a week.
M-02 includes a promise to share what shadowing finds. Keep it. Sharing results, including the agent's mistakes, is the strongest message in the plan.
Questions people ask
Should staff be told before the pilot is approved?
Tell them once the decision to pilot is made. Telling them earlier invites speculation about something that may not happen; later invites the sense of being kept in the dark.
Who should deliver messages about role changes?
The person's own line manager, supported by HR, in a one-to-one. Never by email first.
What if staff refuse to work with the agent?
Find out why. Objections often point to a real gap: unclear checking duties, unrealistic targets, or a fear of being blamed for the agent's errors. Fix the cause before pushing on.