A promotion page can stay online after the offer expires and keep promising a discount the customer can no longer get. The review needs a date, an owner, and a clear split between the offer details and the lasting policy. That preparation turns an expiry from a scramble into a routine update. This guide is written for the knowledge manager who owns the article and the support lead who fields the questions after the offer changes.
Why promotion articles age badly
A promotion article is written for a short window, but it often lives in the same library as evergreen policy pages. The article may include dates, eligibility rules, and a call to action that only makes sense while the offer is live. When the end date passes, the page can remain accurate about the product and wrong about the offer. Customers then arrive with a screenshot and a reasonable expectation that the discount still applies.
The problem gets worse because promotion language spreads. The same offer may appear in a help article, a saved reply, a chat macro, and a banner. Editing the main article does not fix the copies. A review that checks only the page will leave the team answering the same expired offer in three other places. The review has to follow the promise, not just the file.
Promotion articles also attract links from marketing campaigns and social posts. A customer who bookmarked the page may return months later and see the old offer. The page does not know the campaign ended. A dated review is the only reliable way to catch that gap before a customer does.
Give the article an expiry date and an owner
Add an explicit review date to the article record, separate from the last edited date. The review date should be a few business days before the offer ends, not the day after, so the team has time to stage the replacement. Store the date where the content calendar can see it. A date buried in the body text is easy to miss when the page is copied into a new template.
Name one owner for the review, even if several teams contribute. The owner is the person who confirms that the replacement text is live and that the old offer is gone. A shared owner is often no owner, because each team assumes another team checked. Put the owner's name and the review date in the same record so the handoff is unambiguous.
Set a second check for the day after the offer ends. The first review prepares the change, and the second check confirms it happened. The second check can be short, but it should look at the live page and the saved replies. A prepared change that never deployed is still an expired promise.
Separate the temporary offer from the lasting policy
Rewrite the article so the offer details sit in one clearly marked section. Keep the durable policy, such as the return window or the eligibility rule, in a separate section that does not depend on the promotion. That structure lets the team replace the offer section without rewriting the whole page. It also makes the review faster because the reviewer knows which part to inspect.
Label the temporary section with a visible end date in the body, not only in metadata. A customer who reads the page should see when the offer stops. The label should use a plain date and avoid vague phrases like while supplies last unless the supply limit is real and explained. A clear end date reduces the number of customers who arrive after the deadline expecting the discount.
Decide what the page should say after the offer ends. Some pages should redirect to the current offer, some should become a general policy page, and some should be retired. Write that decision into the review notes before the end date. The person doing the update should not have to invent a new page under time pressure.
Stage the replacement before the end date
Draft the replacement text while the offer is still live. The draft can be reviewed and approved without changing the customer experience. When the end date arrives, the team publishes the approved text instead of writing from scratch. This staging step is what keeps the change from slipping into the next week.
Test the replacement with an agent who answers promotion questions. Ask the agent to read the new text and say what a customer would ask next. The agent will notice missing details such as whether an order placed before the deadline still qualifies. Fix those gaps in the draft rather than after the first confused customer arrives.
Prepare the internal message at the same time. The message should tell agents what changed, which offer ended, and where to send a customer who asks for an exception. If the team plans to honor a short grace period, say so in the message and in the article. An undocumented grace period becomes an inconsistent exception.
Check every place the offer appears
Search the knowledge base for the offer name, the discount code, and the end date. Include articles, macros, saved replies, and templates that agents copy. List each match with an owner and a required action. The main article is only one row in that list.
Check the links that point to the article as well. A campaign page or a partner page may still send customers to the old offer. If the team cannot edit the external page, ask the owner to update it or add a note to the article that explains the change. The customer should not have to reconcile two pages that disagree.
Review automated messages that mention the promotion. A welcome email or an order confirmation may include the old offer long after the article is updated. Those messages often live outside the support tool, so the review needs a named contact for each system. Add the contact to the review record for the next cycle.
Brief the team and record the change
Send a short brief before the change goes live. Include the end date, the replacement text, and the one sentence agents should use when a customer asks for the expired offer. Keep the brief in the shift handoff so the next shift sees it. A brief that arrives after the first complaint is a repair, not a preparation.
Record the review date, the owner, the pages changed, and the systems checked. Store the record with the article so the next promotion can reuse the process. The knowledge article expiry review covers the broader calendar, and the promotion code exception log covers the cases that arrive after the deadline. The next owner should be able to read the record without asking the previous reviewer what changed.
Close the review with a check of the live page. Confirm that the old offer is gone, the new text is visible, and the saved replies match. A dated screenshot or a short note is enough evidence for the next reviewer. The goal is not a perfect page but a page that stops making a promise the business no longer keeps.
