Two focused changes: reveal a restriction reason where staff need it, and route new web inquiries while preserving work already underway.
Reconstructed from verified Salesforce configuration · synthetic example
Staff needed to identify the type of restriction without searching older records and activity. I kept the existing checkbox and added a single-select reason that appears when the checkbox is checked.
The decision preserved existing statuses and avoided assigning invented reasons to historical records. On the verified Lightning page, the reason is required when it is shown.
One reason, required on this page when Blacklist is checked.
Try checking the box, then select a reason. Labels and choices follow the retrieved configuration; the visual presentation is a portfolio reconstruction.
Form activity can arrive after a lead has been created. I built a routing flow that checks the lead’s current owner and status before assigning it to admissions. Call activity, converted leads, and leads already owned or worked by a person receive no owner change from this flow.
My role: updated 24 intake forms and mappings, added the SMS opt-in field to the lead page, and personally built and tested the routing flow. An independent tester completed QA. The delivery lead originated the request and the integration triggers.
A newly created activity must be marked as a web-form submission and created by the integration service. It must link to an existing, unconverted lead that is still owned by that service with Status = New. The destination queue must also exist.
The exhibit isolates this flow. It does not simulate other automations, delivery latency, or a Salesforce save failure.
These paths reflect the active configuration verified in production. Nothing is submitted or written to Salesforce.
Alongside the form and mapping work, I added SMS Opt In to the lead interface. The verified page places it immediately after Marketing Opt In, so the two fields are available together in Contact Information.
Synthetic unchecked values. This excerpt shows verified field placement, not a captured client record or a claim that consent was obtained.
The evidence supports the implemented behavior and my stated contribution. The case study does not assign a measured time saving or error reduction. The visual layout of this exhibit was created for the portfolio; it is not a screenshot of the client application.
Interactive reconstruction prepared with AI assistance from verified configuration. Return to selected work.