Marketing Response Rules When a Website or Booking Page Goes Down

Quick answer

A broken destination turns otherwise reasonable marketing into wasted effort and a poor customer experience. The response should not depend on whoever happens to notice the problem first. A short outage protocol assigns the person who verifies the fault, the person authorised to pause traffic, and the safe alternative customers can use while repairs are underway.

The operational problem

Paid posts continue sending visitors to a broken booking page, while the owner is unsure who should stop the promotion or tell customers. Distinguish a full website outage from a single broken form, a slow page, a payment failure, or a problem affecting one device. Do not announce that the whole site is unavailable after one failed test. Conversely, do not keep promoting a booking route simply because the homepage loads. Test the exact journey named in the promotion.

Recommended workflow

1. Keep a register of active campaigns, their destination URLs, spend status, and the person able to pause them.
2. When a failure is reported, reproduce it using a private browser window and a second device or network if practical.
3. Record the time, affected page, observed error, and a screenshot that excludes customer information.
4. Ask the named owner to pause or redirect promotion when the failure prevents the advertised action; do not wait for a weekly meeting.
5. Use an alternative contact method only if it is staffed, accurate, and suitable for the offer.
6. After repair, complete a fresh end-to-end test before resuming the original campaign.

Worked example

A coaching centre advertises a trial-class form. The homepage loads, but the form submission returns an error. The fallback may be a staffed phone number or a clearly maintained enquiry channel; it should not be an unattended inbox presented as an immediate response route. The team records how long the form was unavailable and which campaigns pointed to it.

Decision rule

Pause traffic when the promised action cannot be completed, the page displays materially incorrect terms, or the alternative route cannot handle enquiries. Keep activity running only when the unaffected destination still fulfils the advertisement honestly. For a minor visual issue, assess whether it blocks comprehension or completion before interrupting the campaign.

Copy-and-use template

Incident ID / detected at / affected URL / campaign owner / test performed / customer action blocked / pause decision / approved fallback / technical owner / retest evidence / resume time.

Mistakes to avoid

Do not send users to a generic homepage if the advertised discount or service cannot be found there. Avoid changing the destination to a personal account or unverified short link. If a tracking redirect is involved, verify the final URL as well as the first click. Preserve evidence for troubleshooting without storing unnecessary visitor data.

Track detection-to-decision time, outage duration, failed form tests, and unresolved enquiries attributable to the incident where this can be established. These measures diagnose readiness; they do not alone quantify revenue lost, because not every visitor would have converted.

Frequently asked question

Should every outage pause all marketing?

No. Pause the promotion whose promised action is broken; unaffected activity can continue if its destination remains accurate. Do not send users to a generic homepage if the advertised discount or service cannot be found there.

Prepare a small contact sheet for the technical owner, advertising account owner, booking-system supplier, and person authorised to communicate with customers. It should identify the route to reach each person during trading hours and outside them. Avoid publishing internal escalation numbers on the public page. For campaigns with scheduled spend, check whether pausing one ad also leaves related ads, boosted posts, or automated schedules active. The incident is not closed merely because the homepage returns; the exact customer action must work from the promoted entry point.

A useful edge case to rehearse

After recovery, ask whether the fault was visible to monitoring, whether the first report reached the right person, and whether a fallback route was genuinely usable. One short review can improve the next response without assigning blame.

Next step

Test high-value customer journeys before major campaigns and after material site changes. A rehearsed pause rule protects trust more reliably than an assumption that someone will notice a failure in time. For the first trial, use the record fields described above: Incident ID / detected at / affected URL / campaign owner / test performed / customer action blocked / pause decision / approved fallback / technical owner / retest evidence / resume time. As the next checkpoint, confirm this action: When a failure is reported, reproduce it using a private browser window and a second device or network if practical.