Triage new enquiries and prepare the conflict check for a lawyer

IntermediateA design, not yet run for a business

For:Law firms

Post this as a projectFree to post. We call you within 2 working days to scope it with you.

The job

New enquiries arrive by web form, phone and email. The intake specialist reads each one, types every name into the practice system's search and writes up the hits for a lawyer. Some name a current client on the other side. The owner's question: "Do we answer good enquiries fast, without ever booking a consultation before the conflict check is done?"

Trigger and outcome

Trigger: a new enquiry lands in the intake form or the intake inbox. Outcome: a one-page conflict prep sheet for the responsible lawyer: the practice area, every person and company named, and possible matches in the firm's contacts and matters, each with where it was found. The lawyer decides; intake books or declines with approved wording.

Tools

  • OpenClaw collects new enquiries from the intake form export or inbox.
  • Jev sorts each enquiry by practice area and fit, using rules the lawyers wrote, with a reason for each.
  • Hermes extracts the names of the enquirer, the other side and related parties.
  • The Clio API (or the system's export) is searched for those names across contacts and matters, including closed ones.

Steps

Conflict check prep: a new enquiry arrives, the agent sorts it by practice area, pulls out every party name, searches past and current matters, the lawyer decides on conflicts and fit, then intake books or declines with approved wording

The agent finds possible matches; only a lawyer decides there is no conflict.

  1. Ask for less. The lawyers cut the intake form down to what is needed to check conflicts and fit: names of all parties, the type of matter, dates. Rule 1.18 protects what a prospective client tells the firm, and its comment advises limiting the first consultation to what is needed.
  2. Sort. Jev labels each enquiry by practice area and flags those the firm does not handle. Intake reads the reasons each morning.
  3. Extract names. Hermes lists every person and company named, with spelling variants and former names. Intake checks the list against the enquiry.
  4. Search. OpenClaw searches contacts and matters through the API, open and closed, and records each hit with the matter and role. Rule 1.10 imputes one lawyer's conflict to the firm, so the search covers every lawyer's matters.
  5. Lawyer decides. The prep sheet goes to the responsible lawyer, who clears, declines or asks for more facts. Waivers need informed consent confirmed in writing (Rule 1.7) and are the lawyer's call alone.
  6. Reply. Intake sends the approved booking or decline message; the record notes who cleared it and when.

Human checks

  • No consultation is booked and no substantive information is requested until a lawyer clears the conflict sheet.
  • Declines use lawyer-approved wording and give no legal advice.
  • Every outgoing message is approved by intake staff at the start; nothing is sent automatically.
  • Enquiry details stay in the firm's systems; extraction runs in a tool the firm has approved for client information, or on a local model.

Data needed

The intake form fields, a contacts and matters export, and the lawyers' practice-area rules. For building, invent enquiries and a client list, including a near-match spelling and a former opposing party.

Variations

  • Lateral hire: search the new lawyer's prior matter list before they start.
  • New party mid-matter: re-run the search when a new party appears.
  • Intake CRM: use Lawmatics' intake forms and conflict search in place of the inbox.

Where to find more

Further reading, not the source of this design:

Sources

Further reading

More workflow libraries elsewhere

Further reading, not part of our programme: other people's takes on the same jobs.

  • n8n workflow templates ↗

    Community-built automation flows, filterable by sales, marketing, support, document work and AI.

    Read a template for the order of its steps and the apps it touches, then design the approval points yourself.

  • Make templates ↗

    Ready-made scenarios grouped by business area, including invoicing, inventory, HR and email marketing.

    Useful for seeing which systems a small business already connects, before you pick what your agent reads.

  • Zapier templates ↗

    Short trigger-and-action recipes for lead management, support tickets, forms and campaigns.

    Most recipes are one trigger and one action; notice where an agent would add a judgement step and a human check.

  • Claude Cookbooks ↗

    Code notebooks for classification, summarising, extracting data from forms and PDFs, and tool use.

    Open it when a step needs code, such as pulling fields out of a receipt; the ideas carry over to other models.

  • Building effective agents cookbook ↗

    Minimal examples of chaining, routing, parallel calls, orchestrator and workers, and evaluator loops.

    Read it to name the shape of your workflow before you build it; the patterns matter more than the code.

  • Hermes Agent Skills Hub ↗

    Searching skills other people have written for Hermes Agent, from built-in to community sources.

    Read a community skill before you install it, and never give one access to an owner's accounts without review.

  • ClawHub ↗

    The public registry of OpenClaw skills and plugins, including email, calendar, sheets and chat connectors.

    Check who published a skill and what it can touch; treat it as a starting point you read, not a black box.

  • Agent Skills ↗

    The open format for packaging a workflow as a SKILL.md folder that many agents can load.

    Use it when you want to hand a workflow over as a skill file the owner's agent can reuse.