The playbook
Lead Capture Forms: Template and Field Guide
This lead capture forms template turns a broad task into a record another person can use. It captures field, qualification use, destination, 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
An initial service inquiry might need name, contact method, service need, and area. Ask for more detail later if it does not change the first routing decision. Include source context through appropriate hidden data rather than asking the visitor to reconstruct the campaign.
Copyable worksheet
| Field | Entry instructions |
|---|---|
| field | Record the field associated with this page or interaction record. Use a stable reference so later updates can be matched. |
| qualification use | Record the qualification use associated with this page or interaction record. Keep the value specific enough for another owner to interpret. |
| destination | Record the destination associated with this page or interaction record. Keep the value specific enough for another owner to interpret. |
| required status | Record the required status 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 field. Use the same reference throughout the record so notes are not attached to the wrong item. Then match fields to the offer and qualification needs. This establishes the information required before the worksheet becomes a request for action.
Next, explain the response visitors should expect. Use the observed problem and evidence fields to explain why that step is needed. A useful entry describes an actual condition, such as collecting many fields that nobody uses to respond, rather than a broad instruction to “improve performance.”
Finally, verify delivery attribution and duplicate handling. Put remove unused questions and collect deeper details later 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 | Collecting many fields that nobody uses to respond |
| Action | Remove unused questions and collect deeper details later |
| First check | Match fields to the offer and qualification needs |
| Follow-up check | Verify delivery attribution and duplicate handling |
| Outcome to define | qualified delivered leads |
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 qualification use 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 delivered leads connected to the item so the team can later assess whether the action was useful.
Design recovery as part of the experience. People enter incomplete information, use slow connections, and return to interrupted tasks. A clear error and a preserved input are often more useful than another decorative element.
Skip the manual steps. Let AgentixHUB run this for every client.
Start now