Written guide

Automate follow-ups and new client onboarding

How rules work under Clients, Automations: triggers, conditions, actions and who sees each, merge fields, chains and run history, then new client onboarding step by step and common recipes.

What a rule is

Open Clients, then Automations. Each rule reads: when something happens to a client, do these actions. A rule has one trigger, at most one condition, and up to 10 actions, which run in order.

  • Click Add rule. Give it a Name, pick the event under When, add a condition under If if you need one, and add actions under Then with Add action.
  • Leave Active ticked and click Save. The rule runs the next time its event happens. It doesn't go back over clients the event already happened to.
  • Suggested rules lists starter rules. Add saves one at once. Set up opens it in the editor first, so you can pick a template or a step.
  • On a rule, Edit opens it, Pause stops it without deleting it, Resume turns it back on, and Delete removes it.

For a short video of one suggested rule, see Automate a client follow-up.

Describe the automation

Instead of picking each part yourself, write what you want in plain words, such as when a client signs the engagement letter, send the organizer and make a task to review it in 3 days. FinishTax sends your description, and the names of your templates, pipelines and steps, to Anthropic, our AI provider, to draft the rules. Nothing saves until you click Save.

  • On Clients, Automations, the Rules tab, the Describe the automation box sits above your rules. Say when it should happen and what to do, up to 1,000 characters, and click Draft.
  • Each drafted rule opens in the rule editor, one at a time, marked Drafted from your description. Check it before saving. One description can make up to 5 rules. Save or Cancel opens the next one.
  • A template or a step it couldn't match is left blank for you to pick. Save stays off until you do.
  • Anything it left out is listed in each draft under About your description, and under the box until you draft again or click Dismiss.
  • A rule on A client is added that sends something to the client leaves imported clients out, as the built-in rules do. Remove that condition in the editor if you want imports included.
  • Your firm can draft 20 times a day. After that, add the rule yourself or try again tomorrow.
  • The Owner, admins and members with Manage pipelines can use it, on Small Firm and up. It needs your consent to use AI. If you haven't given it, FinishTax asks first.

Triggers: what starts a rule

Pick one under When. They're grouped by area.

  • Intake: A client sends the intake form, and A client is added. A client is added by hand, when you convert an intake into a new client, or by an import, once for each client it adds. Clients made by your booking page or a QuickBooks sync don't start it.
  • Organizer: An organizer is sent, A client finishes an organizer, and You finish reviewing an organizer, which is when you click Mark reviewed.
  • Documents: A document is uploaded, and Every requested document is in, the first time everything on a document request is in, whether the client uploaded it or you marked it received.
  • Tasks: A task is done, and All of a client's tasks are done.
  • Signatures: A signature request is signed.
  • Invoices: A client accepts a proposal, An invoice is sent, An invoice is paid, A client chooses to pay from their refund, A client's payment is returned, and A return is delivered, the first time a client downloads a file you held until their invoice was paid.
  • Recurring: Recurring work is marked done, and Recurring work is paid.
  • Pipeline: A client's status changes, A return moves to a new step, and A return leaves a step. A step is a stage, a column on your Pipeline board. For the two step triggers you pick the Pipeline board and the Step instead of a condition. Leave the Step blank and the rule runs whenever a client enters (or leaves) any step on any board.

Conditions: run only sometimes

Without a condition a rule runs every time its event happens. Click Add a condition to narrow it. Pick a Field, an Operator and a Value. Remove condition takes it off.

  • The fields are what that event knows, then the client's own, such as Client type, Tax year, Filing status, Client status and How they heard about you.
  • Some events add their own, such as Source on A client is added, Signature purpose and Signature template on A signature request is signed, Organizer template on A client finishes an organizer, and Service name on recurring work.
  • The operators are is, is not, contains, is greater than, is less than, is empty and is not empty.
  • To leave imported clients out of a rule on A client is added, use Source is not Imported.

Actions, and who sees each one

Above the fields of each action you write text for, a line says who reads them: Your client sees this (email and portal), Your client gets this by email, or Only your firm sees this. Under the fields, Preview shows the text with a sample client, Jordan Alvarez.

  • Move to a step: moves the client on your Pipeline board, in either direction. Tick Add the client to this board if they aren't on it to add them. Tick Never move a client back to leave a client already at or past that step where they are. It's off for rules you add. Nothing goes to the client.
  • Update client status: sets On track, Needs attention, Overdue or Complete. Your firm sees it.
  • Create a task: Task name, Task notes, Priority and Due in days. Only your firm sees it.
  • Complete a task: closes every open task of the client whose title contains the words in Task title contains (for the event's year, when it has one).
  • Notify the firm: an alert, with Alert title and Alert text. Only your firm sees it.
  • Email the client: Email subject and Email message. The email opens with Hi and the client's first name, or Hi there when there's no first name. Your client gets it by email.
  • Request documents: Request title (shown to the client), Note to the client and the documents you name. The subject is fixed: your firm's name, then is requesting documents from you, plus the year when the client has several. Your client sees it by email and in their portal.
  • Ask the client to book: emails a link to your booking page with your Note to the client. Your firm needs a booking page first.
  • Send a portal invite: the same invite as Invite to portal on their profile.
  • Send a signature request: sends one of your signature templates with the client as its signer. A template with more than one person to fill can't be used.
  • Send an organizer: sends one of your organizer templates for the client's latest tax year, or your firm's default year.
  • Ask for their documents: one request for every document still needed on the client's checklist for the year. More on this under new client onboarding below.

When a signature request, an organizer or Ask for their documents can't go to a client, such as when they have no email address, the template was deleted or your plan doesn't include it, the rule skips them, its history says why, and you get a notification.

A past (archived) client gets nothing from a rule. Actions that would reach them are skipped and the history says so. Tasks, alerts and moves still run.

Fill in the client's details

Under each text field, click a chip to put a merge field where your cursor is. FinishTax fills it in when the rule runs.

  • Client name, written {{client_name}}: the client's name, or the business name.
  • First name, written {{first_name}}: their first name, or the client name when there's no first name on file.
  • Firm name, written {{firm_name}}: your firm's name as your clients see it.
  • Tax year, written {{tax_year}}: the year the event was about, else the client's latest year.
  • Portal link, written {{portal_link}}: your firm's own portal sign-in page. It never signs the client in. A client without an account can start your intake from there. It's offered only on actions your client reads, and is left blank in tasks and alerts.

When one rule sets off another

Rules can chain. A rule that moves a client to a step sets off any rule on A return moves to a new step, and a signed letter that a rule sent sets off rules on A signature request is signed. FinishTax keeps chains from repeating.

  • A template goes to a client once for each event, even when two rules would send it.
  • Ask for their documents makes one request for each event.
  • A rule never sends the same template that set it off, so "when this is signed, send it again" can't loop.
  • A rule that would set itself off again in the same chain stops, and its history says rules were setting each other off. A chain of rules setting each other off at once also stops after three rounds.

See what a rule did

Under each rule is its last run: Never ran, Last ran with when and what it did, Last skipped with why, or Last error.

  • A run says what each action did, such as who was emailed or which step the client moved to.
  • A skip says why, such as the condition wasn't met, or the client has no email address.
  • The steps of new client onboarding show the same line.

Set up new client onboarding

At the top of the Rules tab, the card Set up new client onboarding builds the usual chain for you: the engagement letter when you add a client, the organizer once it's signed, and a request for their documents when the organizer comes back. Click Set up.

  • Step 1, Engagement letter: pick one of your signature templates. It's sent for them to sign when you add a client.
  • Step 2, Organizer: pick one of your organizer templates. It's sent once they sign the letter this flow sent. If you skip step 1, it's sent when you add a client.
  • Step 3, tick Ask for their documents. When the organizer this flow sent comes back, they get one request for every document still needed on their checklist. Pick an organizer first: this step waits for it.
  • Step 4 is optional. Tick When all their documents are in, move them to, then pick a Pipeline board and a Step. It never moves a client back.
  • Steps 1 and 2 can be set to Skip this step, and steps 3 and 4 stay off unless you tick them. A skipped step makes no rule. With no templates yet, None yet: create one takes you to make one.
  • Click Save. Each step is an ordinary rule you can change later.

A step your plan doesn't include can't be picked, and it names the plan that has it.

What onboarding does and doesn't start

  • Imported clients are left out. One import never emails your whole client list. A client you add by hand or convert from an intake into a new client starts it.
  • Steps 2 and 3 only continue a chain onboarding started (with step 1 skipped, step 2 starts it when you add a client). A letter you send by hand, even from the same template, doesn't start the organizer, and an organizer you send by hand doesn't start the document request.
  • Step 4 runs each time one of a client's document requests is complete for the first time, for any client, not only new ones. That includes the requests you send for the season. It moves the client forward to the step you picked. A client already at or past that step stays where they are. A client who isn't on that board is added to it, unless they already finished in that pipeline.
  • If you already have rules that send a letter when you add a client, or send an organizer, setup lists them. Leave Replace these so a client never gets two letters (or two organizers) ticked to take that action out of them. A rule's other actions stay.

Let organizer answers build the document list

Step 3 asks for exactly what the client's checklist still needs. To have their organizer answers add to that list, set it on the organizer template. Open Organizers, then Organizer templates, and open a template.

  • On a question, type a document name in A “yes” adds a checklist item, such as 1098 for a question about mortgage interest.
  • A “yes” creates a task does the same for a task for your firm.
  • A yes is a ticked checkbox, a dropdown choice other than No or None, or a typed answer other than blank, No, N/A, None or 0. A question hidden by the client's other answers adds nothing. A file upload question has neither setting.
  • The items are added as soon as the client submits, before step 3 runs. So the request lists them along with anything else the checklist still needs for that year.
  • Documents already received, or already on an open request, aren't asked for again. If nothing is still needed, nothing is sent, and the step's history says so.

Change, pause or remove onboarding

Once set up, the card reads New client onboarding and lists its steps in order, such as 1 Engagement letter, 2 Organizer, 3 Documents. Each shows what it sends, whether it's Active or Paused, and its last run.

  • Edit step opens that step's rule in the editor, to change its text or add actions.
  • Change setup opens the setup again. Changes you made to a step stay, and a paused flow stays paused.
  • Pause flow turns every step off. Resume flow turns them back on.
  • Remove flow deletes its steps. Anything already sent to a client stays sent.
  • If you change a step's template through Edit step, the next step can still be waiting for the old one. The card then names that step and the template it still waits for, with Update setup to line them up again.

Common recipes

  • Keep clients moving after step 4: add a rule on A return moves to a new step, pick the board and step, and add Create a task for whoever prepares it. Or add the suggested rules Ready to e-file, which moves the client when a Form 8879 is signed, and Return delivered.
  • A reminder for your firm: add the suggested rule Review the organizer, which adds a task when a client finishes an organizer. Click Edit on it to set Due in days, such as 2.
  • Begin preparation: when every requested document is in, move the client to In Preparation and add a task to begin work. If onboarding step 4 already moves them, keep only the task, so the two don't both move the client.
  • Next steps by email: a rule on A client is added, with the condition Source is not Imported, and Email the client. Its message starts out filled in with a thank-you that names {{firm_name}} and ends with {{portal_link}}, so they can sign in to their portal.

Plans and who can change rules

  • Automations are on Small Firm and up. Sending a signature request or an organizer also needs a plan that includes them.
  • If your plan ends, rules stop running and start again when it's back. You can still pause or delete a rule, and pause or remove onboarding. Adding, editing and resuming wait for the plan.
  • Team members need View pipelines to see the rules, and Manage pipelines to change them.

Plan: Small Firm and up. Compare plans

Still stuck?

Email us what you were trying to do and where it stopped.

Email us