Connect LegalVoice to SmartAdvocate with explicit data and workflow boundaries.

LegalVoice describes only the actions supported by the configured SmartAdvocate path. Availability still depends on the firm’s account, permissions, field mappings, and enabled workflow.

• Look up possible contacts and cases using configured CaseSync endpoints.
• Confirm caller identity before exposing case-specific status or internal details.
• Add mapped notes, tasks, documents, or other approved case actions when the firm enables them.
• Use configured user-defined fields when a workflow requires data that is not present on the ordinary case response.

The connector should move only the fields required for the approved intake or follow-up action and preserve provider identifiers and result states for review.

• Caller identity and contact references used for safe matching.
• Case identifiers and status context returned by the configured tenant.
• Firm-approved notes, tasks, document references, and mapped user-defined fields.
• Action result, timestamp, error state, and staff-review context.

Begin with the narrowest useful connection, test it with controlled records, and enable additional actions only after the firm reviews the result.

• Create or select a SmartAdvocate CaseSync service user with the minimum required permissions.
• Save the tenant base URL and credentials, then validate JWT authentication.
• Review contact matching, identity verification, case mappings, and allowed actions.
• Test read-only lookup before enabling any mapped write action.

A connected credential is not blanket permission to read or write every record. Provider success, partial success, and failure must remain visible to staff.

• SmartAdvocate configuration, UDF names, permissions, and available endpoints vary by firm.
• A possible phone or name match is not permission to disclose case information.
• Writes remain action-specific and permissioned; connecting credentials does not authorize every possible update.

This example shows the operational sequence without using customer data or promising that every firm uses the same configuration.

• An existing client calls the firm and is classified before any case lookup occurs.
• LegalVoice finds possible contact and case matches and asks an approved identity question.
• After verification, the configured workflow supplies the safe status or captures the caller’s message.
• Any approved note or task is attempted separately and its result remains visible to staff.