Configure the CRM for a client website integration

Implementation steps

1. Write a small implementation brief

   Fictional example: an agency is connecting a renovation company’s enquiry form. Record the target workspace, form purpose, required contact route, classification, owner and next action. Separate these decisions from the website’s visual design. Never use the agency workspace simply because it is already selected in your session.

2. Configure the pipeline and stage definitions

   In CRM settings, review the lead pipelines available to the current workspace. For the example, the team may choose New enquiry, Needs clarification and Qualified, using the stage controls supported by that release. Define an observable exit condition for each: received, missing detail requested, or qualification recorded. Review the configuration before changing a pipeline already used by live records.

3. Map only supported CRM information

   Match the form’s name, response address and enquiry description to the available destination fields. Keep an explicit source/page reference where supported. Distinguish a form label from a custom CRM field: renaming an input does not create a server-side field. Do not promise extra field types or automatic assignment rules that are not available in the installed version.

4. Validate with the person who will receive the work

   Use a clearly fictional enquiry and inspect the saved record with the intended staff member. Check the workspace, mapped values, pipeline/stage and whether the responsible person can actually access it. Where assignment is manual, make that handoff explicit. Record missing configuration as a blocker instead of marking the integration complete because a form displayed a success message.