Agreement overview
[Agency] + [Client] Lead Response Agreement
1. What counts as a delivered lead
A lead is delivered when it reaches the agreed destination and includes the minimum contact information required for follow-up. The delivery timestamp begins the response clock.
- Destinations: [CRM, shared inbox, call-tracking account, or webhook]
- Required fields: [name, phone or email, service requested, source]
- Excluded leads: [spam, duplicates within X days, out-of-area requests]
2. Response target
| Lead window | First human attempt | Owner |
|---|---|---|
| During business hours | [X minutes] | [Role] |
| After hours | [X minutes / next opening] | [Role] |
| Urgent or high-value | [X minutes] | [Role] |
Define a human attempt clearly. An automated acknowledgement alone should not stop the clock unless both parties agree.
3. Minimum follow-up sequence
- 1Attempt one through the lead's preferred channel within the response target.
- 2Attempt two through a second channel or at a different time within [X hours].
- 3Make [X] total attempts across [X] business days before marking the lead unreachable.
- 4Record the final disposition and a short reason in the agreed system.
4. Outcome definitions
Matches the agreed service, location, timing, and customer criteria.
A confirmed appointment or next sales step exists.
Fails a named qualification rule, with the reason recorded.
The minimum sequence was completed without a response.
5. Weekly accountability review
Review the same measures every week and assign a named action for every exception.
- Leads delivered and accepted
- Median first-response time and percentage within SLA
- Leads with no recorded attempt or outcome
- Qualification and booking rate by source
- Disputed leads and the evidence needed to resolve them
- One agency action and one client action for the next week