Connects LegalVoice to a firm-configured Lead Docket tenant. No official partnership is implied.Lead Docket integration
Send structured personal injury intake to the Lead Docket form your firm approved.
LegalVoice can create a Lead Docket opportunity after an eligible intake when the firm has configured its tenant URL, opportunity form, field contract, case-type mappings, and sync policy. Contact and matter fields are filtered to that tenant’s approved form; additional detail can be folded into the mapped summary, and a fuller intake note can be added only when the tenant API key and created opportunity ID are available. Rejections and connection failures remain visible for retry or staff review.
Make intake operational
Start with the firm’s actual Lead Docket form contract
Lead Docket opportunity forms are tenant-specific. LegalVoice therefore needs the correct submission endpoint, allowed field list, case-type field and value map, marketing-source configuration when used, and an explicit agency activation rule.
A mapping that is correct for one firm should not be copied to another tenant without review. Narrow forms may accept only identity, contact, case type, source metadata, and a summary.
Create the opportunity with mapped fields, not a generic payload
The sync builds a provider payload from the LegalVoice intake and then filters it to the configured tenant fields. A LegalVoice intake identifier can be included for traceability, while case-type and source values use the firm’s configured Lead Docket IDs rather than guessed labels.
- Skip existing-client callers from the new-opportunity path.
- Run automatic submission only for the enabled intake origins and agency profile.
- Treat an HTTP success with a rejected Lead Docket response as an error, not a completed sync.
Separate the opportunity form from the optional intake note
When a tenant form is narrow, configured intake detail can be folded into its Summary field instead of sending unapproved keys. After the opportunity is created, LegalVoice can add a fuller human-readable intake note through the tenant API only when the required API key, tenant base URL, and external opportunity ID are present.
The optional note is a second-stage write. A note failure does not erase a successfully created opportunity, so staff should be able to distinguish opportunity status from note status.
Keep rejected mappings and delivery errors reviewable
Rejected opportunity writes and connection exceptions are recorded as retryable errors. Existing external IDs make repeat processing idempotent, while incomplete or tenant-incompatible field mappings require correction rather than repeated blind submission.
field map
Lead Docket opportunity mapping checklist
The configuration layers to approve before enabling an intake-to-opportunity write.