Define the minimum record
Start with source, consent, contact method, service, location, timing, and a free text note. Do not collect sensitive information unless the workflow truly needs it.
Learn / Operations + automation
Make lead intake easier to run.
A stepwise buyer guide for deciding what lead intake should collect, validate, route, and leave with a person.
01 / Practical sequence
Map the current path
Write down where a request arrives, which fields are required, who decides priority, and how the customer receives the next step.
Validate before routing
Reject missing or malformed records visibly. Keep a manual queue for duplicates, conflicting details, unavailable integrations, or language nuance. Use semantic structure, labels, keyboard access, and sufficient contrast consistent with WCAG 2.1 AA.
Test with labelled examples
Use synthetic examples such as “Example: Spanish language preference, Harris County, foundation inspection requested.” Do not present examples as client data.
Choose the smallest build
An n8n workflow may be enough; a focused Node.js tool may fit when the team needs a specific queue, permissions, or audit trail. Scope the review first.
02 / Control points
Make exceptions easy to resolve.
Automation can validate and move records, while people handle exceptions and judgment. Treat the pilot as a test of handoff reliability.
- Data boundary
- Collect only fields needed for the next decision, document consent and access, and keep sensitive details out of ordinary lead forms.
- Review queue
- Send duplicates, missing context, unsupported language, and failed integrations to a named person with an agreed response time.
- Pilot measure
- Count received, valid, assigned, reviewed, completed, and recovered records over a defined window.
- Recovery path
- Keep the original request with limited access and an agreed retention period, plus a manual route so a provider outage does not erase the request.
03 / Continue
Related paths.
Use the relevant service page to turn this guide into a clear first review.
Next / Review
Tell us where work gets stuck.
Share the current path, the failure point, and the evidence you can safely share. We will explain what to check first, what the work involves, and what the work involves.