Practical automation · 4 min read
Move website leads into Salesforce with a clear owner
A saved website lead still needs someone to follow up. Review assignment, duplicate handling, and lead conversion so your team can find and act on each request.
Your website says the form was sent, but the person who should call back cannot find the request. Start with one submission and trace its saved record, owner, and next action. A useful handoff makes the request visible to the right person and gives failed submissions a review path. It also keeps a repeat customer's request connected to the right account.
What to take away
- Inspect the assignment option your integration sends, then verify the saved owner.
- Handle a possible duplicate deliberately. Check the configured rule and the API response.
- Keep record creation, lead qualification, and conversion as separate steps with checked results.
Our recommended handoff review
Trace one request
Start with a controlled website submission. Keep its request reference and the Salesforce response.
Check the saved owner
Read the record that was saved. Confirm the person or queue responsible for the next action.
Review possible duplicates
Give uncertain matches to staff. Avoid merging people based on a shared phone number or company name alone.
Convert when qualified
Define who decides that a lead is ready to convert. Verify any existing Account and Contact before using their IDs.
Verify follow-up
Confirm the assigned person can see the request and its next action. Keep failed requests in a review queue.
These are our recommendations. Test them against your Salesforce configuration and your team's working process.
Check the assignment option and the saved owner
Salesforce's REST assignment header, Sforce-Auto-Assign, defaults to TRUE. TRUE applies active assignment rules; FALSE skips them. A valid AssignmentRule ID applies the specified rule. Skipping a rule does not establish that a record has no owner.
Our recommendation: record the option sent by your form service and inspect the resulting owner. Agree on a fallback for requests that miss your intended routing conditions. A saved Lead ID proves creation; it does not prove that the right person saw the request.
Give duplicate responses a review path
Salesforce's REST duplicate rule header is available from API version 52.0. Its allowSave option defaults to false. For actions with an alert enabled, true allows acknowledging the alert and saving the duplicate. This does not mean every duplicate rule can be bypassed.
Our recommendation: test your actual rule and request options. Read the API response before showing success. Keep rejected or uncertain requests for staff review, with enough context to locate the existing customer. Do not enable duplicate saves across every form just to remove an error.
Treat conversion as a checked decision
Salesforce documents convertLead() as a dedicated SOAP operation. It requires a saved Lead ID and a valid converted status. It can merge into an existing Account and Contact; a selected Contact must belong to the specified Account. Queue-owned leads need a user owner for conversion. Examine the returned conversion result before recording success.
Our recommendation: decide when a lead is qualified and who may approve the match. Inspect the conversion method your connector supports, its permissions, and the returned IDs. Creating a Lead alone does not complete that process. Person Accounts and other organization-specific settings need their own test cases.
Sources: Salesforce SOAP convertLead()
Walk through a blocked request and a saved lead
Consider a hypothetical body shop, not a client result. Its website accepts an estimate request. Salesforce rejects the attempted Lead create as a possible duplicate. The form service retains the request for review instead of claiming that a new Lead was saved.
Staff confirm the existing customer and attach the estimate request to that customer's approved follow-up process. There is no newly created Lead to convert in this branch. An uncertain match stays in review.
In a separate first-time-customer branch, the create succeeds and returns a Lead ID. Staff verify its owner and next action. If they later qualify it for conversion, they review the account match and check the conversion result. Each branch ends with a named person responsible for the request.
Keep this handy
Your pre-project checklist
- Trace one controlled website request through the API response and saved record.
- Check the assignment header and the resulting owner, including the fallback route.
- Test a possible duplicate with the actual rule and API options your integration uses.
- Confirm failed and uncertain submissions remain visible for staff review.
- Agree on qualification and matching decisions before lead conversion.
- Verify conversion results and the assigned person's access to the next action.
Prefer to write it down? Tell us about your project. No portal account required.
These examples explain how we would approach the work. They are not client results. How we write our guides or send a correction.