Map the lead journey
Start with the fields your team actually needs. Avoid asking for sensitive or excessive details too early. Define what happens after submission and who responds.
- Validate and normalise fields
- Capture consent and source appropriately
- Assign ownership and notification
- Record failures for safe retry
Choose an integration method
A supported native connector may be simplest. A custom API integration can handle unusual mapping or business rules, but needs authentication, error handling and maintenance.
Never rely on a browser-only success message as evidence a lead reached the CRM. Test the confirmation and the destination record.
Protect people and data
Limit who can see enquiries; define retention and avoid putting personal details in public URLs or analytics. Check the privacy notice against the actual flow.
Questions worth asking
What if the CRM is unavailable?
A resilient integration should flag the failed delivery and provide a safe retry rather than silently losing the enquiry.
Advice here is general; the appropriate implementation depends on the people, systems and constraints involved.