Common lead record
Minimum useful fields: unique ID, received timestamp, inquiry type, product/service, location, language, contact details, consent record, source, campaign and landing page, assigned owner, status, next action, follow-up due date, disposition, and delivery/integration status.
Delivery behavior
- Send a visitor confirmation without sensitive claim content.
- Send the staff alert to the correct queue or owner.
- Write the lead to the system of record before considering delivery complete.
- Use idempotency to prevent duplicates and a queue for transient failures.
- Retry with limits, surface permanent failures, and alert a named operator.
- Test spam protection, rate limits, file safety, and data minimization.
System choices
| Approach | Use when | Incremental allowance |
|---|---|---|
| Current dashboard + inbox | Volume is manageable and ownership is clear | $0–$20/mo |
| Existing AMS/CRM integration | It has a usable API/webhook and staff already work there | $20–$150/mo |
| Fuller lead stack | Measured volume and attribution needs justify it | $150–$600/mo |
Call tracking is approximately $45–$175/month before possible overages; scheduling can be $0–$20 per seat/month; SMS adds number, usage, carrier and A2P registration costs. Count tools once across programs.