Check whether the Sam Aguiar site chatbot fires rules to alert Alert Communications / the call center, and compare against the recent custom form routing fix.
sail-forms guidance for contact-form/call-center alert behavior.https://intaker.azureedge.net/widget/chat.min.js with firm slug samaguiarinjurylawyers.https://chat-api.intaker.com/api/v2/Chat/...; no calls to WordPress /sal/v1/contact-intake, Alert Communications, Zapier, or local webhook were observed during load/open.wp-content/mu-plugins/sal-custom-contact-intake-v2.php over SSH. It processes form submissions through Litify, Litify attribution, email, and Teams only./var/www/html/contact-intake-config-v2.php. litify_webhook_url and teams_webhook_url are set; email recipients are internal firm addresses only. No alertcommunications.com recipient or explicit call-center destination was found.wp_sal_contact_leads and wp_sal_contact_attempts. There are 68 stored form leads from 2026-04-09 through 2026-05-13. Latest row: Litify sent, email sent, Teams failed HTTP 400. No newer rows prove a post-repair successful form alert.teams_alert_health routine. It expects the live handler to contain application/vnd.microsoft.card.adaptive, but the live handler still sends the old simple Teams payload shape array('text' => $text).+15024431333, but that only proves a call option, not lead forwarding/rules into Alert Communications.https://dashboard.intaker.com with saved credentials and inspect Integrations / Zapier / notification rules, especially Zapier activation /integration/zapier-activation/16.