A landscaping maintenance caller may be reporting scheduled work, asking for an extra task, or enquiring about a new contract. Contract status helps route the request, but it should not become a blanket promise that every task is included.
Maintain an approved account reference with sites, service scope, contacts, current agreement context, and staff owner. Keep uncertain terms for review rather than asking the model to interpret a contract from conversational fragments.
Separate existing service from additional work
Ask which property and task the caller means. A known customer may request work outside the maintenance agreement or at a new site. Record those distinctions before creating a job or quoting an included-service answer.
Use explicit administrative categories such as schedule enquiry, service concern, additional-work request, and new-contract enquiry. Each needs an owner and a next action, not merely a tag.
Work through a fictional managed estate
A property manager calls about missed hedge work at a maintained site, then asks to add tree work at another building. The receptionist links the reported service concern to the correct site and captures the additional project separately.
It does not say the tree work is included because both buildings belong to the same manager. Staff review site coverage, scope, resources, and pricing through the company's normal process.
| Contract case | Required routing boundary |
|---|---|
| Scheduled maintenance question | Verified site and service owner |
| Missed-work report | Review linked to existing service |
| Extra requested task | Additional-scope decision |
| New property | Coverage and agreement review |
| Unknown agreement status | Owned staff clarification |
Preserve ownership across departments
A request can move between account management, estimating, and field operations. Record acceptance when ownership changes and keep the unresolved question visible. Forwarding an email should not automatically close the original task.
Contract-aware routing reduces manual sorting when account data is current. Broad automated interpretation creates more maintenance and dispute risk. A narrow workflow that finds the right owner can provide value without deciding entitlement.
Review old agreement references and site aliases periodically. Test one caller managing several similarly named properties. See multiple-property accounts for property selection and separate action tracking.
Questions about maintenance contracts
Can the agent confirm work is included?
Only from current approved information and authorized rules. Otherwise, capture the coverage question for the agreement owner.
Should a known customer skip intake questions?
Reuse verified context where appropriate, but confirm the property and requested work. Familiarity does not establish new scope.
What should happen when a contract has expired?
Follow the company's approved renewal or new-service process. Do not silently apply old pricing or attendance commitments.