Call webhooks

When a call ends and post-call analysis finishes, Lawtte posts a call_analyzed event to your firm’s webhook endpoint.

Payload

{
  "event": "call_analyzed",
  "call": {
    "call_id": "call_abc123",
    "from_number": "+12125550100",
    "duration_ms": 184000,
    "transcript": "Agent: Thank you for calling…",
    "call_analysis": {
      "call_summary": "Caller was rear-ended on the 405 last Tuesday…",
      "custom_analysis_data": {
        "caller_name": "Jane Doe",
        "case_type": "auto accident",
        "injured": "yes"
      }
    }
  }
}

Respond 200 with { "received": true } as soon as you have the payload, then do your own work asynchronously. Slow responses cause retries.

What Lawtte does with it

Creates or updates a lead

Caller name, number, and case type are extracted from the analysis, deduplicated against existing leads, and written to your dashboard.

Syncs to your case management system

Clio, MyCase, Filevine, and Lawmatics are supported, plus a generic sync endpoint per system.

Notifies your team

Email and Slack notifications go out with the summary and a link to the lead.

Verifying requests

Webhook requests are signed. Reject any request whose signature does not verify against your firm’s webhook secret, and treat the body as untrusted until it does.

Booking events

Cal.com booking events (BOOKING_CREATED, BOOKING_RESCHEDULED, BOOKING_CANCELLED) arrive on a separate receiver and drive appointment reminders. See appointments.

Get started

Guides

Payload

What Lawtte does with it

Verifying requests

Booking events

​Payload

​What Lawtte does with it

​Verifying requests

​Booking events

Payload

What Lawtte does with it

Verifying requests

Booking events