As of 13 August 2026, AI can only partly add website enquiries to your CRM.

What to actually do

1. Hand it to a person

   The route this page recommends

   A person who owns the outcome does this end to end, worth it when the failure is dear.

2. Use a tool built for this

   Second choice

3. Do it yourself

   The distant third

   A chat interface, power-user skill, and roughly 1 hour until you can act on the result.

   How to actually do it

   1. Open the website form settings and your CRM's developer or integration documentation, then record the platform names, versions, form fields, CRM fields and available authentication methods without copying any passwords or API keys.
   2. Paste those details into the prompt and ask the model for the field mapping, integration method, configuration steps, error handling and test plan.
   3. Create a test form or non-production CRM destination, then configure the proposed connection with restricted permissions and placeholder credentials rather than changing the live workflow.
   4. Submit dummy enquiries covering a normal submission, a missing optional field, a duplicate submission and a spam-like submission, then compare each resulting CRM record with the form submission.
   5. Check the CRM activity log and integration logs for failed requests, retries, duplicate records, incorrect field types, timestamps and source-page values.
   6. Ask a colleague who understands your CRM and data handling to inspect the permissions, retention, notification and deletion behaviour before approval.
   7. Send one controlled live test, confirm that the correct team receives it, and only then enable the workflow for all website enquiries.

   Prompt

   Design a safe implementation for sending website enquiries into my CRM.
   
   Website form platform: [name and version]
   CRM: [name and version]
   Available form fields: [list each field]
   CRM fields available: [list each field]
   Required outcome: create one CRM enquiry for each valid form submission and preserve the source page and submission time.
   
   Give me:
   1. A field-by-field mapping table.
   2. The simplest suitable integration method using the platforms' documented features or APIs.
   3. The exact configuration steps, including authentication, permissions and where each value belongs.
   4. Any code required, with clear placeholders and no invented API details.
   5. Handling for failed submissions, duplicate submissions, missing fields and spam.
   6. A test plan using dummy data only.
   7. A rollback plan.
   8. A checklist for checking UK data protection responsibilities before sending personal data to the CRM.
   
   Do not ask me to paste passwords, API keys or live customer data. Do not claim an integration is supported unless the relevant platform documentation confirms it. Mark every platform-specific detail that I must verify. Assume I will test in a non-production environment before enabling the live form.

   Open it prefilled in ChatGPT or Claude, or copy it into Gemini, which takes no prefill link.