Why campaigns reach the support queue before the results report
A campaign brief is written for the people who make the campaign. The campaign brief template settles the objective, audience, offer, channels, budget and timing; the Creative BriefA short document telling the people making creative work what it must achieve, for whom, with which message and within which limits. takes the creative direction further. Neither is written for the people who will answer customers about it. Yet the first evidence of how a campaign is landing usually arrives in the support queue: questions about whether a product is included, complaints that a code did not work, confusion about a banner, customers who bought the day before asking for the discount. An unbriefed campaign is one of the causes the diagnosis for support ticket volume that is rising separates when the queue grows faster than the customer base.
The site already covers support readiness for other kinds of change. The product launches hub names support readiness for a product launch, and the launch planning and tiers guide sets the briefing by tier; the guide to communicating a price change briefs sales and support before customers hear. This tutorial covers the case those pages leave out: a marketing campaign or promotion, run by marketing, that changes what customers ask for a fixed period. The sale promotion readiness checklist checks the offer, site, stock, media, owned channels and measurement; the support brief is the item to add beside it.
There is a compliance reason too. The planning promotions guide records, as the site's pricing guidance states it, that in the UK the Competition and Markets Authority enforces consumer protection law covering misleading pricing practices, such as reference prices that were never really charged and urgency claims that are not true, and that the Advertising Standards Authority's codes cover price statements in advertising. An agent who improvises the terms of an offer, or adds a promise the campaign never made, can create exactly the problem the campaign's own checks were designed to avoid. Agents should answer from the same approved wording the campaign uses. This is general direction, not legal advice.
Before you start
- Have the campaign plan. The offer, dates, channels and eligibility should be decided, as the planning promotions guide sets out. The support brief copies them; it does not decide them.
- Know the support set-up. Which channels customers use and how the team runs them, as the support channels and self-service guide describes, decides where the questions will land and how the brief reaches agents.
- Find the last similar campaign. Pull the support contacts from the previous campaign of the same kind and the notes, if any, from its review. Expected volume and likely questions come from the business's own history, not from a rule of thumb.
- Agree who writes, approves and receives the brief. A RACI matrix settles it in a few lines: usually the campaign owner writes it, the support lead and whoever approves claims sign it off, and every agent who answers customers receives it.
- Have the claims approved. If the business keeps a claims library, the campaign's claims should already be in it with their approved wording.
The steps
Tell support the date before the creative is final
As soon as the campaign is in the calendar, send the support lead the dates, the channels and a line on the offer. Ask what questions the team expects and whether anything clashes with their plans, such as reduced cover or a system change. This early warning lets support plan the rota from its own experience of past campaigns, and it often surfaces a question the creative should answer before anyone asks it.
Write the offer and its exact terms
Write the offer exactly as customers will see it, then the terms in full: start and end date and time, who is eligible, what is included and excluded, minimum spend, whether it combines with other offers, how codes work and what happens to orders placed just before the start. Link the Landing PageThe page a visitor arrives on from a campaign, built to turn that visit into one action. where the terms appear. Agents should never have to infer a rule from the creative.
List the claims the campaign makes
Copy every claim from the ads, emails, landing page and social posts into the brief in its approved wording: the saving, the reference price, the deadline, product claims, delivery promisesA store's claim about what delivery will cost and when an order will arrive, made on product pages, at checkout, in confirmations and in ads.. Note where each is substantiated. Agents repeat these words when asked and never add to them, which keeps their answers within what the campaign itself was cleared to say.
Predict the questions from past campaigns
Read the contacts from the last similar campaign and list the questions customers asked, roughly in order of how often they came up. Add the questions this campaign's offer is likely to cause: products that look included but are not, eligibility edge cases, customers who bought just before the start. Ask a few agents to add what they remember; they often recall the awkward questions better than the data does.
Write saved replies for the top questions
For each predicted question, write a saved replyA pre-written answer a support agent inserts and then edits for the customer in front of them, keeping facts and tone consistent across the team. in the team's tone, with gaps for the agent to personalise and a link to the relevant help content or terms. The tutorial on building a library of saved replies covers how replies are structured, owned and reviewed. Mark campaign replies with the campaign name and end date so they can be retired cleanly.
Say what agents may and may not offer
Decide in advance how agents handle the requests the campaign will cause: a customer who bought the day before, a code that failed, a product that sold out, a request to extend the deadline. For each, write what agents may do, what they must not do and who can approve an exception. Leaving these to individual judgement produces different answers for different customers and can contradict the offer's published terms.
Set the escalation route for campaign problems
Name who support contacts, by what route, when something is wrong with the campaign itself: a price showing incorrectly, a code that does not work, a broken link in an email, a claim customers find misleading. Give the route an owner on every day the campaign runs, including weekends if it runs then. If the campaign coincides with a delay or disruption, agree how customers will be told and who writes the message, within the standards the service and support hub sets for every channel. The tutorial on proactive service messages covers what to say, in which channel and when to update.
Agree how support feeds back during the campaign
Set a simple, regular route from support to the campaign owner while the campaign runs: a short daily note of the top questions and anything unexpected, or a shared channel where agents post patterns as they see them. Agree what counts as urgent and goes through the escalation routeA short written route naming who front-line staff contact, how and how fast, when a problem is beyond what they can decide alone. instead. Treat the feedback as campaign data alongside the KPIA metric tied directly to an objective., because it often explains a dip before the dashboard does.
Brief again for the end date and switch-off
Before the offer ends, remind agents of the exact end time and what they say to customers who missed it. Agree when banners, codes and saved replies are switched off, and who checks that they are. Prepare the reply for customers who ask after the end, and for those whose orders were in progress at the deadline.
Review what support heard
Soon after the end, hold a short review with the support lead and the campaign owner. Go through the questions that came up, the ones the brief missed, the escalations and the fixes made during the campaign. Record what to change next time: a term to state more clearly, a reply to keep, a creative choice that caused confusion. Keep the notes with the campaign so the next brief starts from them.
The one-page support brief: a template table
| Section | What it holds | Who writes it |
|---|---|---|
| Campaign and dates | Name, start and end date and time, channels, audience | Campaign owner |
| Offer and terms | The offer as customers see it; eligibility, inclusions, exclusions, minimum spend, codes, combinations | Campaign owner, checked by whoever owns pricing |
| Claims | Each claim in approved wording, with where it is substantiated | Campaign owner, from the claims library |
| Links | Landing page, terms, help articles, the ads and emails customers will see | Campaign owner |
| Expected questions | The likely questions in rough order, from past campaigns and agents | Support lead with the campaign owner |
| Saved replies | Links to the campaign's saved replies, marked with the end date | Support lead |
| What agents may offer | Allowed actions, things never offered, who approves exceptions | Support lead with the campaign owner |
| Escalation | Who to contact for campaign problems, by what route, on each day | Campaign owner |
| Feedback | How and when support reports patterns during the campaign | Support lead |
| End and switch-off | End time, reply for latecomers, who switches off codes, banners and replies | Campaign owner |
Keep the brief to one page and link to everything else. A long brief is not read in the minutes before a shift, and copies of terms or replies inside it go out of date when the originals change.
A mattress retailer briefs its support team for a sale (illustrative)
Snuzmora Mattresses briefs support a week before its sale
Snuzmora Mattresses, an invented online mattress retailer with 6 support agents, plans a 5-day sale with 20% off most mattresses. A week before, the campaign owner sends the support lead a one-page brief: the exact terms, the excluded sizes (cot and custom sizes), the wording of the 100-night trial claim from the claims library, and links to the landing page and terms.
The support lead reads the contacts from the last sale, which brought about 430 contacts over its 5 days, and finds the top questions: whether the discount applies to bed frames, how the trial works with a sale purchase, and price matching for customers who bought just before. The team writes 7 saved replies, agrees that agents may refund the difference for orders placed in the 3 days before the sale, and sets a same-day route to the campaign owner for any pricing error.
On the first day, agents' notes show 38 chats asking whether frames are included, because the homepage banner reads "20% off beds". The campaign owner changes the banner to "20% off mattresses" on the second morning, and frame questions fall to 6 the next day. At the review, the team adds the banner wording to the next campaign's checks.
Verify it worked
- Open the one-page brief. Every row of the template table is filled, from dates and terms to feedback and switch-off.
- Compare the brief with the landing page and creative. Dates, exclusions and claims match the approved wording, and no banner promises more than the terms.
- Ask an agent to answer each predicted question from the brief and saved replies alone. Nobody has to guess or ask the campaign owner.
- Check the escalation row. A named owner and route exist for every day the campaign runs.
- Check the switch-off row. Campaign replies carry the campaign name and end date, and someone is named to remove codes, banners and replies.
If it goes wrong
- Agents give different answers about a missed offer. What they may offer was left to individual judgement. Write allowed actions, limits and who approves exceptions into the brief.
- Contacts pile up on a question the brief did not predict. The creative may say more than the terms. Pass the pattern to the campaign owner, fix the wording and add a reply.
- A code fails or a price shows wrongly. This is a campaign problem, not a support one. Use the escalation route to the named owner, and do not improvise a fix.
- Codes, banners or replies stay live after the deadline. Nobody owned the switch-off. Name who checks it, remove them and use the prepared reply for latecomers.
Next steps
- Read the saved replies library tutorial to give each campaign reply an owner and a review date.
- Run the sale promotion readiness checklist beside the brief, so support readiness is checked with the offer, site and stock.
- Read the planning promotions guide to settle offer, dates and eligibility before they reach the brief.
Common mistakes
- Briefing on launch morning. Agents need time to read the terms and ask questions before customers do.
- Copying the creative, not the terms. A banner is not a rule. Agents need the exclusions, dates and conditions in full.
- Letting agents improvise. Answers that add promises or extend deadlines case by case contradict the offer's terms. Decide in advance what agents may offer.
- No route for campaign problems. Support often spots a broken code or a wrong price first. Without an owner and a route, the problem runs until someone in marketing notices.
- Ignoring support's feedback. The questions customers ask during a campaign are early evidence of what is confusing them. Read them daily.
- Forgetting the end. Codes, banners and saved replies left running after the deadline make the deadline untrue and confuse agents.
- No review. The same questions return with the next campaign unless someone records what support heard.
