Connecting a form to a CRM is easy to demo and easy to get wrong in production. The demo covers the happy path. Production covers double submissions, CRM outages, unknown routing values, interrupted responses and credentials that expire. A brief that covers those cases before code starts saves most of the rework.
Start with definitions, not endpoints
Define what received, saved and assigned mean. A visitor message that says "message sent" should match the system state. If the CRM must confirm the record, say so. If the request is stored durably and processed later, the confirmation should describe receipt, and the team needs a way to find requests that stay unprocessed.
Map fields by business meaning. A person, a company and an enquiry are different records. An existing contact with a new enquiry needs a new activity or lead, not an overwritten message.…