Define success in operational terms
For Case Growth Solutions' implemented legal funnels, success means the configured CRM upsert or approved webhook returned an acceptable response. A browser click, valid local form, or analytics event is not enough.
That boundary keeps the visitor experience aligned with intake reality. It also gives support teams a clear place to investigate when submission fails.
Fail closed on missing or rejected delivery
The legal-marketplace production route returns a service-unavailable response when neither GoHighLevel nor an approved webhook is configured. The fire-claim route returns an error when its inbound webhook is missing, times out, or rejects the request. The survivor-intake flow documents the same no-false-success behavior when its CRM token is absent.
In each pattern, the form retains an error state so the person can retry. A disqualified path also remains separate and sends no lead.
Fail open on optional measurement
Warehouse inserts, funnel telemetry, and conversion API calls answer important marketing questions, but they are not the primary delivery destination. Case Growth Solutions' newer routes schedule that work after the response, while older-runtime paths bound it so a slow analytics dependency cannot hold the visitor indefinitely.
The inverse matters too: when CRM delivery fails, the system records the failure for triage and skips the lead conversion event. Optional measurement should not manufacture success.
Make failure observable
Lead Intel exposes CRM failures, conversion API status, retrying or failed postbacks, and records awaiting an assignment ID. The cross-platform dashboards also preserve provider-specific errors instead of blanking the full report.
A reliable system distinguishes missing configuration, invalid input, provider rejection, network failure, duplicate suppression, privacy blocking, and permanent failure. Each state has a different owner and next action.