A website can launch successfully and still leave the client unsure what happens next. When an opening time changes or a promotion ends, they need a clear route to the update. A support agreement makes that route visible.
## Start with responsibilities
Separate three kinds of work: routine content updates, technical maintenance and new functionality. They need different skills and different decisions. Correcting an existing sentence is not the same task as changing a booking integration.
For each category, record who requests the work, who approves it and who checks the public result. Give the client a backup contact for periods when the usual person is unavailable. Do not imply that buying a content-editing tool transfers responsibility for hosting, security or integrations.
## Describe the service being purchased
A monthly fee might buy reserved time, proactive checks, or a set of requested edits. Write down which it includes. If unused time expires, explain that. If work outside the scope needs a separate estimate, make that decision before starting it.
A useful request template includes the page URL, current wording, approved replacement, deadline and reason. Ask where else the same information appears. An opening-time change may affect the homepage, contact page and a separate business listing.
## Agree a realistic response window
Distinguish acknowledging a request from completing it. “We reply within two working days” does not promise that every request is finished in that period. Define an urgent route for situations such as a broken booking path, and explain any separate charge.
Keep the agreement small enough to use. A long list of theoretical services is less useful than a clear answer to the client's next likely request.
## Make the first update part of handoff
Have the client perform one authorized change while you observe. Confirm what saving does, whether publishing is separate, and how to restore the previous wording. Use the [website handoff checklist](/blog/website-handoff-checklist-client-updates) to record the result.
If the existing editor works well, keep it. If the client prefers sending requests, a maintenance arrangement may fit better. ReCopyFast is another option for editing existing website copy after a developer installs it; it does not replace technical maintenance.
## Review the agreement using actual requests
After the first month, look at the requests received. Which needed clarification? Which were outside scope? Which could the client safely handle? Adjust the agreement together. Retention starts with a service both sides understand, not a promise that one tool will produce loyal customers.
## Start with responsibilities
Separate three kinds of work: routine content updates, technical maintenance and new functionality. They need different skills and different decisions. Correcting an existing sentence is not the same task as changing a booking integration.
For each category, record who requests the work, who approves it and who checks the public result. Give the client a backup contact for periods when the usual person is unavailable. Do not imply that buying a content-editing tool transfers responsibility for hosting, security or integrations.
## Describe the service being purchased
A monthly fee might buy reserved time, proactive checks, or a set of requested edits. Write down which it includes. If unused time expires, explain that. If work outside the scope needs a separate estimate, make that decision before starting it.
A useful request template includes the page URL, current wording, approved replacement, deadline and reason. Ask where else the same information appears. An opening-time change may affect the homepage, contact page and a separate business listing.
## Agree a realistic response window
Distinguish acknowledging a request from completing it. “We reply within two working days” does not promise that every request is finished in that period. Define an urgent route for situations such as a broken booking path, and explain any separate charge.
Keep the agreement small enough to use. A long list of theoretical services is less useful than a clear answer to the client's next likely request.
## Make the first update part of handoff
Have the client perform one authorized change while you observe. Confirm what saving does, whether publishing is separate, and how to restore the previous wording. Use the [website handoff checklist](/blog/website-handoff-checklist-client-updates) to record the result.
If the existing editor works well, keep it. If the client prefers sending requests, a maintenance arrangement may fit better. ReCopyFast is another option for editing existing website copy after a developer installs it; it does not replace technical maintenance.
## Review the agreement using actual requests
After the first month, look at the requests received. Which needed clarification? Which were outside scope? Which could the client safely handle? Adjust the agreement together. Retention starts with a service both sides understand, not a promise that one tool will produce loyal customers.