Connect intake to Filevine with identity checks and explicit write boundaries.

The connector requires a Filevine Gateway base URL, access token or configured token exchange, and the organization and user headers used for that firm. A saved disabled provider remains disabled, and missing authorization material prevents the connector from presenting itself as ready.

Provider discovery should stay read-only until an operator explicitly enables a guarded writeback policy and the firm approves the mapped actions.

A phone, email, or name lookup can produce possible contact and project matches, but a possible match is not permission to disclose internal Filevine details. The agent-safe view hides project IDs, client IDs, assigned staff, notes, tasks, injuries, documents, insurance, and raw case facts.

Normal verification can use a supported caller detail such as date of birth, last name, or address. If identity or the specific matter remains ambiguous, the safe outcome is a message, callback, or staff review—not a guessed case phase.

The Filevine provider catalog exposes mapped client, project, note, task, document, and related case-management actions. In a configured intake route, LegalVoice can create or locate the relevant record and then add approved context such as a human-readable intake note, a staff follow-up task, or web-intake attachment metadata.

Those capabilities should not be treated as enabled merely because credentials exist. Field mappings, action permissions, dry-run behavior, and the firm’s staff-review policy define what the connection may write.

The intake sync records retryable errors when the provider route fails. Attachment writes can also finish with a partial-error state after the case or client record has already been created, preserving the distinction between a successful core handoff and a failed secondary action.