No more dead enquiries.

Web forms, phone calls, email, manual entry and referrals land in one stage-tracked pipeline, each carrying where it came from. A returning enquirer is matched to the contact the firm already holds rather than arriving as a stranger. A voice receptionist can take the inbound line when the firm turns it on — it is not how this page leads, and it is not claimed as a live public receptionist.

Build intake forms in a drag-drop editor — fields, conditional logic, per-form email actions. Embed on any partner site with a one-line script; UTMs and ad click IDs are forwarded automatically. The same editor builds the client questionnaires that gather what a family lawyer needs before the first meeting: children, finances, the family home, the other party.

Every live enquiry carries two bars — qualifying and onboarding — the single next action, who owns it, and how long it has waited, flagged red past 48 hours. Each action is marked by who it waits on: the firm, the client, or ready to convert. Every lead gets an AI summary, a relevance score and a quality rating; duplicates are flagged for review rather than silently merged. Where a reply is composed it goes to an approvals queue for a person to read, edit and send, and it refuses to draft to anyone marked do-not-contact.

Consultations are booked from the lead onto a lawyer's own Google Calendar or Outlook, offering only the days that genuinely have room, with the invite emailed and the meeting on the record. A booking that needs moving is moved against the lawyer's other commitments, and the client is told either way. That first meeting is the one Notetaker then writes up.

Terms to sign, the welcome email and the questionnaires are assembled from the team's own templates and arrive as ready drafts on the lead. A person reviews and sends. Ezra does not email a client on its own to start onboarding. Chase of an unsigned document is automatic; the first send is human.

KYC, AML and PEP/sanctions checks run through Thirdfort, with the firm's standard check set per matter type. A referred result is never auto-passed or auto-failed — it waits for a person to read the provider's report and decide. Where sanctions and PEP monitoring is switched on, Ezra tracks the period and tells whoever ran the check when it lapses. The same check can be started from the notetaker review in one tick. Identity follows the person, not the matter: a client who has already cleared KYC skips it on the next instruction. Where identity was genuinely verified off-system, an admin or partner records a manual pass; it is filed as an override with a reason, never as a check result.

Ezra Sign sends terms as an envelope, chases the client on its own, files the signed copy into the right folder and can block conversion until it is back. A will, an LPA, a deed or a statutory declaration is recognised and never routed to e-signing.

Conversion needs four: conflict, identity, signed terms and payment arranged — plus the firm's own acceptance questions. The button stays disabled and lists exactly what is outstanding. An exception is a recorded override: an admin or partner authorises it with a reason, or anyone else requests one and an approver decides — and an approver cannot decide their own request. There is no quiet way past a gate. Ezra never converts anyone by itself.

Identity follows the person. A client who has already cleared KYC and signed terms skips straight to onboarding carrying the compliance they already passed, rather than being put through it again.

Exact and fuzzy matching across Clio and Ezra contacts, weighted by signal: an email or phone match is decisive, a shared surname deliberately is not. Anything scoring 70% or more against a different person, or hitting the firm's block-list, goes to a human. It re-runs whenever the parties change — including when the other parent is added after the first meeting — and a conflict a person flagged can never be cleared by a later automatic run.

Case plans (Lexcel 7.1), matter risk assessments (MLR 2017 reg 28) and supervisors' file reviews (Lexcel 5.11) live on the matter and on a central register. Ezra drafts what the file can evidence and marks it as its own suggestion — but it never proposes a risk rating, and on the case plan it leaves blank the fields a client disputes later: what the retainer excludes, and what would change the costs estimate. A case plan is the firm's own record; it is never sent to a client without a separate, explicit act.

Log a SAR, gather from Ezra and Clio, decide each third party once across every document (the other parent, the children, a new partner), redact or withhold under a named statutory exemption, produce the pack and deliver it behind a password-protected link that expires. An open request puts a preservation hold on the person's documents, because destroying responsive material is a criminal offence under DPA 2018 s173. The one-month clock runs from the date received; it can be paused awaiting ID, clarification or a fee, and extended with a recorded reason up to the statutory maximum.

A client asking for a copy of their own file is logged and worked as Copy of file, not as a subject access request. Ezra treats it differently: the disclosure is the file, not a scan of everywhere the person is mentioned. Starting either request is a deliberate, logged step from the data-requests queue.

Rectification, erasure, restriction and objection run on the same one-month clock as a SAR but need a decision rather than a disclosure pack. You record Granted, Partly granted or Refused with grounds, tick Article 19 recipient notification where others were told, and mark the response sent. Ezra does not itself correct, erase or restrict the underlying records — that remains a person's act, evidenced on the request.

A complaint about how the firm handled personal data sits on the complaints register, not in the SAR queue. Quarantine holds inbound attachments that failed scanning until someone releases them. The approvals queue collects everything waiting on a decision — referred KYC, conflict review, override requests — so compliance is a worklist, not a hunt.

Spend, enquiries, qualified enquiries and the matters they became, campaign by campaign, with return on ad spend on the same row. Lifetime values are computed per enquiry type and department from bills marked paid over the last twelve months — mean and median side by side, so one outsize financial-remedy matter cannot carry the average. Attribution is not a separate product: it is the same pipeline, followed through to a signed client.

As a lead is verified, qualified, engaged and finally pays, Ezra fires the matching conversion back to Google, Meta and LinkedIn — server to server, so it survives ad-blockers and iOS. Every milestone is logged as sent, pending, failed, expired or skipped, with the platform's own error on the row. Failures are retried, then surfaced.

Call tracking — Infinity and MediaHawk — matches every ring to a campaign. The calls report treats a ring under five seconds as a misdial and anything longer as a matter that went elsewhere. Missed calls break down by ring duration, hour of day, team and paid campaign.