From website question to CRM: a handover checklist
Decide the data, permissions, owners and proof you need before a website AI employee sends leads to your CRM.

Define a finished handover
A message saying “I’ve passed this on” is not a CRM record. A handover is finished when the right system accepts a record, with the right owner and enough detail to act on.
In Aivah, you can connect CRMs such as HubSpot and Salesforce from the app catalog in Library → MCP tools. Each write, such as creating a contact, waits for your yes. Leads from a web experience’s lead form also land in Insights → Leads, ready to export.
Send the smallest useful set of details
Decide which fields your team really needs. Keep what the visitor said apart from what your system guessed. Leave open questions visible instead of filling gaps with guesses.
- A short description of what the business needs.
- The contact details the visitor chose to share, and their consent.
- The page or topic that started the enquiry.
- Questions already answered, and what is still open.
- Who gets it next, based on a rule you agreed.
Check connections and permissions
In Aivah, check Library → MCP tools and the account each app is signed in with. Connected apps are shared across the workspace, and each employee’s Tools tab can limit it to specific actions.
Give access only for the job. Test with harmless data in an approved place, and look at the result yourself. If an action isn’t supported, use the approved contact form or a manual handover.
Test failures and duplicates
A timeout is unclear: the system may have saved the request even if no reply came back. Check for an existing record before you repeat an action that could create a duplicate. Ask whoever owns your integration how retries and duplicates are handled.
Include a missing field, an expired connection and a refused permission in your tests. The visitor should get an honest next step, never a fake success message. Make sure failures reach a person who owns them.
Link measurement to delivery
Track attempted handovers, accepted records, rejected records and records waiting for review separately. Check that a person can act on what arrives. A form click or a chat starting should never count as a delivered lead.
Use campaign tags to see which content brought useful enquiries, but never put names, emails or other private details in tracking links. Review lead quality and connection failures together before you send more traffic.

















