A website enquiry needs a clear next action and someone responsible for it. Norml builds a routing workflow around your WordPress form, qualification fields and sales ownership rules. Zapier coordinates the handoff; Pipedrive holds the sales record and Slack makes the assignment visible.
Start with the decisions your team already makes: which enquiries belong to which service, territory or account owner, and which need a person to review them.
We map the submission ID, contact details, requested service and routing fields. The form plugin determines the available trigger; WordPress itself does not supply a universal form-submission event. Spam and incomplete records follow an agreed review route before sales actions run.
Service and region rules produce one accountable owner. Existing-account ownership can take priority when the business requires it. We define rule order, conflicting matches and a fallback queue so a new dropdown value cannot quietly leave an enquiry unassigned.
Pipedrive receives the agreed person, lead or deal information, with an activity when that is part of the scope. Slack gets a concise assignment notice after the CRM write succeeds. Sensitive free-text fields stay out of the message unless they are needed.
Provide the form plugin, example submissions, Pipedrive field definitions and active owner list. Connection access must cover the selected CRM actions and Slack channel. We check the required plugin and Zapier plan capabilities before committing to a route.
A stable submission ID identifies a delivery already processed. Contact matching is a separate decision: one person can submit different enquiries. The scope includes a processing record and recovery steps for partial runs, including a CRM success followed by a Slack failure.
The default workflow assigns internal work. Prospect emails, marketing enrolment, enrichment and round-robin capacity calculations require their own rules and approval. A named administrator owns routing changes and the unresolved-enquiry queue after handover.
Review valid submissions, incomplete details and existing customers. Record the expected owner, CRM action and alert for each example before building the Zap.
Configure the supported trigger, branching and destination fields. Test a repeated submission, conflicting rules and a rejected CRM write without contacting prospects.
Check source IDs against destination records and alerts. Document how to pause routing, correct a record and resume only the missing action after a failure.