Session Objective

Answer whether the form moved into the Lexington sidebar has the same mapping, forwarding, and email rules as the homepage form.

What Was Checked

• Live WordPress page: https://aguiarinjurylawyers.com/locations/lexington/
• Page ID: 6911
• Homepage page ID: 10
• Live handler files reviewed over SSH:
  • wp-content/mu-plugins/aas-sal-intake-rollout-v2.php
  • wp-content/mu-plugins/sal-custom-contact-intake-v2.php
• Playwright DOM inspection and intercepted submission test were run. The test intercepted POST requests before they reached the server, so no lead/email/Teams/Litify submission was created.

Findings

• The sidebar form reaches the same intake backend as the homepage path: /wp-json/sal/v1/contact-intake.
• That backend uses the same processing function, creates the same lead record pathway, and then attempts the same destinations: Litify webhook, configured email recipients, and Teams notification.
• The live rendered sidebar form is hydrated with attribution fields including gclid, gbraid, wbraid, UTM values, page title, landing page URL, and last page URL.
• The sidebar form is not an exact clone of the homepage shortcode. The saved page HTML does not include sal_contact_intake_nonce and does not visibly ask for email or injured status. Hydration fills email as blank and injured_status as Not sure yet.
• The homepage shortcode includes a nonce and a normal POST fallback. The sidebar form depends on JavaScript/REST; if that script path fails, the raw POST fallback would not pass nonce validation.
• In an intercepted Playwright click test, the sidebar form attempted POST requests to the REST endpoint. No live submission was allowed through.

Recommendation

Treat the sidebar form as functionally mapped to the same backend and notifications, but not identical to the homepage form contract. A cleaner follow-up would be to convert the sidebar form to a first-class canonical shortcode/variant so it keeps the compact design while inheriting nonce/fallback behavior, field normalization, and future handler changes automatically.

Suggested Next Steps

• Consider creating a sidebar-safe version of the canonical intake shortcode instead of keeping a raw HTML form in page content.
• QA should include one test with network interception and one controlled live intake test only if Sam approves a real test lead.