An automation service can become difficult to deliver when every new request is treated as support. Fixing a broken link, changing opening hours and adding a new sales process are different kinds of work. Define them before the client needs help.
Separate incidents from changes
An incident means agreed behavior is not working. A change means the client wants different behavior. Some requests contain both: a client may report a failure caused by a new business rule nobody told the delivery team about.
Use these distinctions to route work, not to argue with the client. A clear intake question is: “What did you expect to happen, and what changed?” That gives the team a starting point for diagnosis.
Describe included maintenance
List the recurring tasks covered by the fee, such as checking failures, updating approved details and reviewing a defined set of reports. State any limits on revisions, channels or integrations in plain language.
If additional work needs a quote, explain the process and expected response. Do not wait until the task is complete to reveal that it was outside scope.
Define urgency operationally
Identify which failures interrupt a critical customer journey and which can wait for normal review. Agree who can classify an urgent issue and how it reaches the team. A support inbox is not useful if nobody knows when it is monitored.
Avoid promising response or resolution times the delivery arrangement cannot sustain. A response acknowledges the issue; a resolution fixes it. They should not be conflated in the proposal.
Make tickets reproducible
Ask for the affected record, approximate time, expected behavior and observed behavior. Include screenshots when they help, while avoiding unnecessary customer information. A concise, complete report reduces back-and-forth.
Keep the outcome in the same place as the request. Future team members should be able to see what changed and why without searching personal messages.
Review the pattern
Repeated requests may indicate unclear training, an incomplete service or a package that no longer fits. Use the evidence to improve the offer. Do not simply absorb more work every month and hope the margin survives.
A well-scoped support service helps the client get useful help and helps the agency price the responsibility honestly. The goal is clarity at the moment of need, not a long list of exclusions nobody reads.
Sources and further learning
Pricing and Scoping for Agencies, episode 180 — Parakeeto. Publisher show notes distinguish price, delivery cost and delivery risk. The recommendations here apply that distinction to agency operations.
Examples and checklists are proposed operating practices, not claims of measured ScaleGHL client results. Sources reviewed October 12, 2026.
Related agency guides
- Email setup belongs in agency onboarding, not the launch-day checklist
- Client retention: separate lost accounts from lost recurring revenue
Find the right upgrade for your clients
Start with a free client revenue expansion audit. Explore service fit, practical pricing and an agreed delivery scope.
Get my free revenue audit