The playbook
Service Page Design: Template and Field Guide
This service page design template turns a broad task into a record another person can use. It captures service, scope, proof, then connects that information to a decision. Copy the table into your working document or system and create a separate record for each item in scope.
Put the task in context
For equipment installation, explain who the service is for, what the visit includes, what preparation is needed, and which conditions affect scope. Add relevant proof and answers to practical questions. Keep the inquiry action tied to that service.
Copyable worksheet
| Field | Entry instructions |
|---|---|
| service | Record the service associated with this page or interaction record. Use a stable reference so later updates can be matched. |
| scope | Record the scope associated with this page or interaction record. Keep the value specific enough for another owner to interpret. |
| proof | Record the proof associated with this page or interaction record. Keep the value specific enough for another owner to interpret. |
| questions | Record the questions associated with this page or interaction record. Keep the value specific enough for another owner to interpret. |
| action | Record the action associated with this page or interaction record. Keep the value specific enough for another owner to interpret. |
| Decision field | Entry instructions |
|---|---|
| Observed problem | Describe the actual condition and where it was observed. |
| Recommended action | State the smallest action that resolves the documented problem. |
| Evidence | Link to the record, observation, or test supporting the action. |
| Owner and next review | Name the accountable person and when the decision should be revisited. |
How to complete the worksheet
Begin with service. Use the same reference throughout the record so notes are not attached to the wrong item. Then describe scope eligibility and expected process. This establishes the information required before the worksheet becomes a request for action.
Next, show relevant work and common decision questions. Use the observed problem and evidence fields to explain why that step is needed. A useful entry describes an actual condition, such as using the same generic copy for every service, rather than a broad instruction to “improve performance.”
Finally, provide a service-specific next action. Put explain what changes in scope process and suitability in the action field only when it addresses the observed condition. If the problem is different, change the action. The template is a structure for judgment, not a reason to apply the same fix everywhere.
Illustrative completed decision
| Part | Illustrative entry |
|---|---|
| Problem | Using the same generic copy for every service |
| Action | Explain what changes in scope process and suitability |
| First check | Describe scope eligibility and expected process |
| Follow-up check | Provide a service-specific next action |
| Outcome to define | qualified service inquiries |
Adapt the fields without losing meaning
You can add fields required by your team, but each should change a decision or preserve necessary context. Keep factual observations separate from recommendations. If scope changes, record the new value and its effective date instead of silently rewriting the context of an earlier decision.
Use the record in a handoff
Ask the receiving owner to explain the next action using only the worksheet. Missing context becomes visible quickly during that exercise. Repair the record before applying the structure to a larger batch. Keep qualified service inquiries connected to the item so the team can later assess whether the action was useful.
Verify the actual visitor journey on a narrow screen and with a keyboard. A design can look complete while hiding an unreachable control or a missing confirmation. Record the task attempted and what happened at the end.
Skip the manual steps. Let AgentixHUB run this for every client.
Start now