# Salesforce recipe, AI Source Standard v1.0

**Test status: documentation checked; live installation not tested.** Broadcastwell does not run this platform in the audited reference stack. Local fixture checks do not establish platform import acceptance or a live installation. An authorized person must verify the recipe in the adopter's existing system before publishing that installation.

CC BY 4.0, Broadcastwell. Documentation checked 7 October 2026. The client's administrator applies this in its own organization, beginning in its existing sandbox. Broadcastwell creates no Salesforce account, connection or credential.

<table><thead><tr><th>Object</th><th>Label</th><th>API name</th><th>Type and rules</th></tr></thead><tbody><tr><td>Lead</td><td>AI source</td><td>AI_Source__c</td><td>Picklist, exact ten v1 options, blank default, optional</td></tr><tr><td>Lead</td><td>AI question asked</td><td>AI_Question_Asked__c</td><td>Long Text Area, 2,000 characters, optional</td></tr></tbody></table>

In Setup, Object Manager, Lead, Fields & Relationships, choose New and the stated type. Set field-level access only for the staff who need it. Preserve the option order and exact spelling. Reuse existing compatible fields rather than making duplicates. For conversion, the admin can map to already-approved corresponding Contact fields in Map Lead Fields; any additional object fields require its separate authorization.

In Setup, Web-to-Lead, Create Web-to-Lead Form, select the existing identity fields plus these two custom fields. Generate the HTML. Its generated custom field IDs are the required input name/id values, not the API names above. Map the visible ai_source selection to the generated AI_Source__c input ID and the optional question to the generated AI_Question_Asked__c ID. Retain the generated organization ID and return URL from that actual organization. Do not copy IDs from an example. A hidden technical referrer field never replaces AI_Source__c. Do not create an additional field just to store a referrer if analytics already has it.

An existing form integration may write the two API fields directly. If the admin's approved intake has staging fields, a before-save Record-Triggered Flow on Lead creation can use those existing inputs: Configure Start, Lead, A record is created, conditions restricted to the intended intake, Optimize for Fast Field Updates. A Decision validates membership in the exact ten options; an Assignment maps the submitted values to $Record.AI_Source__c and $Record.AI_Question_Asked__c. Preserve blank answers and do not infer a source. If Web-to-Lead already writes the target fields, no copy Flow is needed. No email, task or owner action belongs in this recipe.

Debug in the existing sandbox using a controlled test identity, confirm optional blanks and exact values, and have the admin activate its reviewed change. Test conversion and the opportunity association rule used in the report. Remove only the controlled test record under the client's policy. Export deduplicated aggregates, never raw Lead or Contact rows.

Sources read 7 October 2026: https://help.salesforce.com/s/articleView?id=000393459&language=en_US&type=1 ; https://help.salesforce.com/s/articleView?id=000385435&language=en_US&type=1 ; https://help.salesforce.com/s/articleView?id=platform.automate_flow_build_triggering_record.htm&language=en_US&type=5 ; https://resources.docs.salesforce.com/latest/latest/en-us/sfdc/pdf/salesforce_lead_implementation_guide.pdf . No Salesforce organization was accessed in this run.