Automation

Route form submissions into your CRM as qualified leads

A scenario prompt that converts a described contact-form-to-CRM workflow into an implementation-ready recipe, resolving spam, routing, and ownership-assignment ambiguity.

Works with Claude / GPT890 uses 4.5

The prompt

automation-form-submission-to-crm-lead
A B2B company describes their process like this: "When someone fills out our 'Request
a Quote' form on WordPress, I want a lead created in Salesforce, assigned to the sales
rep for their region based on the state field, and a Slack DM sent to that rep so they
reach out within the hour."

AVAILABLE TOOLS: [Gravity Forms (trigger), Uncanny Automator, Salesforce, Slack]

Turn this into an implementation-ready automation recipe, thinking through what the
plain description leaves ambiguous:
1. Trigger: the exact form-submission event, and how to filter out spam submissions
   from a honeypot or reCAPTCHA failure before they ever reach Salesforce, since a
   bot-filled lead assigned to a rep wastes their time.
2. Conditions: the exact state-to-rep mapping logic, and what happens when the state
   field is blank, misspelled, or the submission is from outside the mapped regions
   entirely (should it default to a round-robin rep or a sales manager).
3. Actions in order: create the Salesforce lead with source and campaign fields
   populated, assign owner based on the region lookup, then send the Slack DM only
   after the Salesforce record exists so the DM can link directly to it.
4. Failure handling: if the Salesforce API is down or rate-limited, should the lead
   data be queued and retried, or should it fall back to an email to the sales
   manager so the lead isn't lost.
5. One edge case specific to this exact workflow: the same person submitting the form
   twice in one day for two different projects. Decide whether that creates two leads
   or updates one, and how the rep is notified either way.

Replace the workflow description and available tools with your own.

Lead-routing recipes that skip the spam-filtering step end up burning rep goodwill fast, since a few bot leads a week is enough to make reps stop trusting the instant Slack DM. This prompt makes you decide the filtering and fallback logic up front instead of discovering the gaps after a rep complains.