How do I ask monthly support to undo a live Webflow change?

Name the live page that should change back

A review before publish is for work that is still off the live domain. This request starts after the live page already shows the change you do not want. The first lines should say that, so the note is not treated as a new design.

Write the page path and say it is the live version. Example: 'Live page /pricing already shows the new annual price. That version should not stay.' A note that says 'undo the last thing' can point at the wrong page when two requests were open.

Use the same thread as the request that made the change, when that thread is still the one you both have. A new channel that says 'please revert' is easy to miss, and it can be read as a second job.

If you have not published the change to the live domain yet, this is the wrong note. The review guide is the check you do before that domain changes. Hold, on that page, means the live site stays as it is.

Paste the version that should return

The request needs the previous version in words, not only the word undo. Paste the heading, the button label, and any sentence that should come back. If the change was a layout, describe the layout that was there: what sat above the form, and what the button said.

Example: 'Put back the heading Plans and the button Write to us. The old sentences are in the message from Tuesday. The three prices on the page can stay.' That note can be done. 'Make it like before' cannot, because before is not in the thread.

If you do not have the old copy, say so in the same note. Attach the last file that had the approved line. If that file does not exist, write the final copy the page should show now. Asking for a reconstruction from memory spends the hour on a guess you may undo again.

Point at the earlier message when the old copy is already in the thread. You do not need to paste a long page twice. Name the message and the lines that should return, and say what should stay as it is now.

Leave a full site restore out of this note

A full site restore puts an older copy of the site back. That is a different decision from repairing one live section. The backup guide is when to save a restore point, and it says a restore is not the default fix for a single page.

Do not write 'restore yesterday's backup' when the job is one heading and one button. A restore can move more than the page you meant. Ask for the named page to be edited back to the copy you provided.

Example: the pricing heading is wrong, and the blog posts from this week are right. The note should change /pricing only. A restore that also rolls the blog backward is a larger request, and you should say that only if you mean it.

If you already saved a backup and you do want that whole-site restore, say so as its own decision, with the backup description you used. Do not hide that choice inside a one-line undo. The person doing the work should not have to guess which of the two you meant.

Say whether the live domain updates now

The note should say where the correction goes. 'Update the live domain now' means visitors should see the previous version. 'Prepare it, and do not update the live domain until I reply' means you want another look first.

Example: 'Put the old heading and button back on /pricing, and update the live domain. Do not restore the whole site.' A second version, when you want another look: 'Put that copy on staging only. I will reply before the live domain changes.'

Those are different outcomes. A note that stops at 'please undo' leaves the destination unstated. Say which one you want in the same message as the old copy.

If other open work sits on the same page, say whether that work should remain. Example: 'Restore the heading only. Leave the new testimonial row that was added underneath.' Two changes on one page need one instruction about which one survives. The same-section guide is what to do when two notes already describe that area.

Keep the undo inside the monthly plan

Putting a named page back is work on the site you already have. It uses the hours in the current period. Unused hours expire at the end of each monthly billing period and do not carry over, so a delay while you look for the old sentence does not bank the time.

If the undo would pass the included hours, wait for the written estimate. Additional work is $75 per hour and starts only after you approve it. The undo note is not that approval. Memberships cannot be paused while you decide.

Communication stays written. There is no call to point at the old layout. The page path, the previous copy, and the domain you want updated are the whole request.

The Webflow retainer is the monthly plan this undo belongs to: $999 per month, including 10 hours of Webflow work. The retainer guide explains which ongoing work those hours cover. Use this page when the live site already shows a change you want taken back.