Town hall · customer operations
From 1 September, customer-facing teams move to a single Customer Operations model: one support queue, one set of case tooling, and shared weekend coverage. Nobody's employment changes. This page explains what does, and when.
ABC Corp is a fictional company. Every name, number and date is invented. This is a reference artifact generated with an LLM coding agent; the brief that produces it is at the bottom of this page.
The three regional queues merge into a single global queue with routing by product area, so a case lands with the right team first time instead of being forwarded between regions.
We retire the two legacy ticketing systems and move every team onto the case tooling already used by the Project Lighthouse pilot, with full case history migrated before go-live.
Weekend cover moves from volunteer overtime to a planned rota shared across all Customer Operations teams: roughly one weekend in eight, scheduled a quarter ahead and compensated with time in lieu.
What stays the same: your contract, grade, salary, and office location.
order-gateway and batch-billing are switched off two weeks later.What stays the same: your contract, grade, salary, on-call arrangements, and office location.
What stays the same: your contract, grade, salary, and office location.
Weekday working patterns are unchanged. Your contracted hours and your usual weekday schedule stay as they are. The one scheduling change is weekend cover for Customer Operations teams, which moves from volunteer overtime to the planned rota described above: roughly one weekend in eight, published a quarter ahead, with time in lieu.
No. Office locations and contracted hours are unchanged. The only scheduling change is the weekend rota for Customer Operations teams, which replaces today's volunteer overtime and is compensated with time in lieu.
The full team mapping (every person, team, and manager) is shared with you and your current manager on 1 July. If anything in your mapping looks wrong, raise it with your manager or the comms mailbox below before 18 July.
Open cases and their full history are migrated to the new tooling during the last week of August. Honest caveat: attachments older than three years move to a read-only archive rather than the live system. They remain searchable, just not editable.
No, and we want to be straightforward about that: the rota is part of the new model for Customer Operations teams. It is designed to be light (roughly one weekend in eight, published a quarter ahead, with time in lieu) and individual constraints, such as caring responsibilities and study schedules, are taken into account in planning.
Ask at the town hall on 15 June, raise it with your manager, or write to the programme comms mailbox:
lighthouse-comms@abc-corp.example. Every message gets a reply within two working days.
For team leads running the follow-up conversation. Lead with what is not changing.
From this comms brief [paste], create a one-page HTML announcement: headline, what's changing, a key-dates timeline, a 'what this means for you' section switchable by role (Operations / Engineering / Customer support), and an FAQ. One file, no images, calm corporate tone.
Paste the brief into any capable LLM: GPT, Claude, Gemini, Grok, DeepSeek, or the assistant your company
provides. Iterate a few rounds on layout and content until it reads well. Save the final answer as a
.html file and open it in any browser. Expect similar output, not identical: every model has its
own taste, and that is fine.
This reference artifact was built with Claude Code, an LLM coding agent, over several iterations. Treat it as the bar to aim for, not as a guaranteed first answer. All data on this page is fictional.