Dispatch
Send a matter to the right vendor category from inside your AI, with roster-first routing and a primary-then-network fallback.
What it does
Dispatch is the core action. Your AI describes a matter - a category, a jurisdiction, a short description - and Scope routes it to a credentialed vendor in that category.
Routing is roster-first. Scope offers the dispatch to your designated primary vendor, holds a window for them to accept, and opens it to the wider network if they decline or time out. You can read the routing state at any point in one tool call.
Scope supports twenty legal-services categories today, spanning court reporting, process serving, records retrieval, IME, expert witness, e-discovery, translation, interpretation, mediation, trial graphics, and more.
Why it matters
Sourcing a vendor used to mean leaving your workflow, emailing a panel, and waiting. Dispatch happens where the work is described, in seconds, against the vendors you already trust.
The primary-then-network fallback means your preferred vendor gets first refusal without you having to chase them, and coverage does not break when they are full.
How to use it
Your AI calls scope_dispatch_matter with the category and jurisdiction. Read the routing state with scope_get_dispatch_routing_state.
scope_dispatch_matter({
category: "court-reporting-stenography",
jurisdiction: "Kern County, CA",
description: "Full-day deposition",
})