Law firm workflow automation, from intake to invoice

Say "workflow automation" in a law firm and it tends to land as software making a decision: sizing up a case, deciding who is worth signing. That is not what it does. Law firm workflow automation, done properly, is unglamorous. It removes the second and third handling of the same fact. A prospect types a phone number into the form on your website, and that number then gets read back on the callback, typed into a calendar invite, typed into the engagement letter, and typed once more onto the first invoice. Nobody bills for any of that.

Trace one inquiry through a four-person firm and the pattern is easy to see. A form comes in at nine at night. In the morning somebody reads it, decides who owns it, writes a welcome email from scratch, opens a task to call the person back, picks a due date out of the air, sends a link so the prospect can book a consultation, and then, four days later, remembers that nobody ever heard back. None of it needs a law degree. It needs somebody to remember, and remembering is the part that fails when three new inquiries land in the same afternoon.

What a workflow is made of

In Esqase a workflow is a named, ordered list of steps you build once and attach to a lead or a matter. You assemble it on a canvas in the workflow builder, name it, and give it one of two triggers. "Manual" means you attach it yourself, from a lead, a matter, or the new-matter wizard. "When a lead or matter is created" means Esqase attaches it to every new record from the sources you pick, such as your booking page or a public form. A workflow can also hang off a public entry point, so a lead-intake form submission or a booking on one of your event types creates the lead and brings the steps with it. There is no house intake sequence you are expected to conform to. You build the steps yourself, out of ten step types. Each one is something a person at your firm already does by hand:

• Email sends the client one email, written in the step or started from a saved template, with placeholders filled in from the record.
• Task creates an internal to-do with a title, assignees, a task type, and a priority from Lowest to Highest.
• Task list creates a batch of tasks at once from a saved list.
• Form emails the client a link to one of your forms and, if you switch reminders on, chases them until they submit or the reminder limits run out.
• Event invites the client to book a meeting, with its own email for the invite, the confirmation, and the decline.
• Document creates a document on the record, blank or from a document template, and fills in placeholders from the record and the client's form answers.
• Invoice drafts an invoice, one line per activity category you pick, and can then approve it, create a payment link, email it, and remind the client until it is paid.
• Status change moves the record to its next stage, moves a lead to a stage you pick, or marks the lead hired or not hired.
• Convert to matter turns the lead into a matter, using a matter template if you name one, or opening the new-matter wizard seeded from the lead if you do not.
• Conflict check screens the client against your firm's records and can stop the workflow at a high-priority match.

Every step also says how it runs. "Manual" waits for a member. "Automatic" means Esqase runs it when its turn comes. "Automatic, needs approval" means Esqase prepares it, writing the email or drafting the invoice, and holds it for a member to approve. A step can start a set time after the one above it, wait for a client outcome such as the form coming back, and carry a condition, so it only runs when, say, the lead source is your website. None of it runs on its own until you turn on the workflow's Automation switch, which starts off on every new workflow.

Put those together and the intake you run from memory turns into a list anyone at the firm can read, and, with automation on, a list Esqase works through for you. Say a prospect submits your inquiry form at nine at night. The form has a workflow assigned, so the lead it creates arrives with the steps already on it. A conflict check screens the new contact first. A task called Call the new lead goes to the member who runs intake, its start date anchored to the moment the lead was created and its due date set relative to that start, so the window slides with the record instead of pointing at a date you typed months ago. An email step sends your welcome message. An event step titled Initial consultation points at the consultation event type you already offer, with its invite, confirmation, and decline emails written up front and a reminder every two days, up to the limit you set. A form step sends the longer questionnaire once the meeting is confirmed, and a task list step drops your standard qualification checklist on in one move. Then a status change moves the lead to its next stage, and Convert to matter waits for whoever took the consultation, with your practice area's template attached.

The invoice step for the consultation fee can sit on either side of the conversion. Above it, the step drafts the bill on a small invoicing matter linked to the lead, which suits a fee you charge before deciding whether to take the case. Below it, the draft lands on the new matter with the client as bill contact, your firm's numbering, and the currency already in place, so nobody signs into a second system to bill the client whose form you read this morning.

What legal workflow automation should never decide

Esqase runs the steps and leaves the calls to you. Attaching a workflow copies its steps onto the record, and with automation on, Esqase works down the list one step at a time, in order. A "Manual" step holds everything below it until a member runs it. Blocking is on by default for a conflict check, so a high-priority match holds the workflow until a member reviews the matches and decides whether to carry on, and a clean automatic screen is only a first pass, because it searches less than the full check a member runs. Convert to matter never runs unattended: it asks a member every time. Invoices start out needing approval too, so an automatic invoice step drafts the bill and waits for a person until your firm changes that.

The case to think about is the stranger at nine at night. Once a workflow's automation is on, leads from your booking page or a public form run its automatic steps as soon as they arrive. An owner or administrator can turn off "Run automatic steps on these leads" in your automation settings, and those steps then wait until a member clicks "Start automation" on the lead. We would turn it off while you are still testing a workflow, so a stranger filling in your form never triggers an email nobody has read. After that, set a sending window: emails, form requests, meeting invites, and reminders that come due outside the hours you set wait for the window to open, while tasks are created straight away. You can pause any single record, and marking a lead not hired pauses its workflows for you.

Some things should stay out of a workflow's automatic steps entirely. Anything a client will read as personal belongs in the composer, written by whoever took the call. An email you want read before it goes can be set to "Automatic, needs approval", so a member sees what Esqase wrote and can choose "Edit and send". Judgment stays put too: whether a conflict-check match is a real conflict under the rules of your jurisdiction, whether the lead is one you want to sign, whether the fee arrangement fits this client. Conditions do not change that. A condition applies a rule you wrote in advance: it checks a field on the record, such as the lead source, and skips the step or stops the workflow when the field does not match. One bit of housekeeping catches firms out: if two active workflows use the "When a lead or matter is created" trigger and share a source, every new record from that source gets both sets of steps, which is how a tidy process turns into a lead with two callback tasks and two welcome emails. Keep a single playbook on the automatic trigger and attach the others by hand.

Where automating client intake pays off

The phone number the client typed into your form lands on the contact Esqase builds from the submission. The consultation invite goes to that contact, and on conversion it becomes the matter's primary client and bill recipient, so nobody retyped anything between the form and the first invoice. The remembering moves into the workflow as well. A form or event step can remind the client on the interval you set, and when Esqase stops chasing, everyone watching the record gets one "Waiting on the client" notification. The record's run history shows what happened and who did it: a member, the client, or Esqase automation. And because each attachment is a copy, editing a workflow never disturbs the leads and matters that already carry its steps, so you can improve the process on a Tuesday without touching anyone's open file.

Write down the intake you already run from memory, build it once from the ten workflow step types, and attach it to the next inquiry that comes in. When you turn automation on, the builder checks the workflow first and lists anything that would stop it. Workflow automation comes with every plan, and you are not charged during the 14-day free trial. Start your free trial, or talk to sales if you would rather see it run against your own intake first.