A CRM integration says which record the website form will land on, and which box writes which field. The sentence “it goes to the CRM” is not a destination. The destination is a name: an opportunity, a person, or a request tied to both. If the field names do not match, the enquiry does not vanish. It lands in the wrong box, or the CRM rejects the row.
Where the form lands
If sales expects an opportunity, the record is an opportunity. If a returning customer should attach to a person card, the match key is one field, such as an email or a tax number. Without a key, every submission opens a new card. A pile of cards is a false sign that the link is working.
The field map
If the form says “quantity” and the CRM says “amount”, that pair is written down. If a required CRM field is missing on the form, the submission is rejected and the visitor often never sees why. The rejection is looked for in a test submission. HED Creative does not close that pair in Berlin or Ankara unless the CRM is yours and the test arrives in a mailbox you named.
Mail and the CRM are not the same job
Mail arriving does not mean the CRM row was born. A row being born does not mean the mail was sent. They are separate paths. If sales reads the CRM, the mailbox copy is a copy. It is not the record.
What is not mapped
A newsletter box, a “how did you hear about us” question and a free note are not forced into a required opportunity field. If they are, the first line sales sees does not describe the job. The map stays short.
To start, the name of the CRM, the kind of record the form should create, and the names of the boxes on the form are enough. A screenshot of one test submission shows why a row was rejected.
Add the map to the web app development job. The boxes on the form: quote form fields.