Workflows for what you build.

Acknowledges an intake form the minute it lands, confirms the consultation, and gets the intake paperwork done before the client arrives.

1. Request receivedSent to acknowledge an inbound inquiry, lead, or application before a ticket number is assigned.
2. Consultation confirmedSent when a booking is confirmed.
3. Intake formsSent ahead of an appointment when intake, consent, or check-in forms need completing.

Reminds a client of a scheduled meeting the day before and an hour out, then confirms every move, cancellation, and miss.

1. Meeting tomorrowSent the day before the appointment.
2. Meeting in an hourSent about an hour before the appointment.
3. Meeting movedSent when an appointment is rescheduled.
4. Meeting cancelledSent when an appointment is cancelled.
5. We missed youSent after a missed appointment.

Chases the records and signatures a matter is blocked on, nudges before the upload window closes, and confirms each one when it lands.

1. Documents neededSent when the recipient needs to supply a document to continue.
2. Upload window closingSent when a non-payment action window is approaching its close.
3. Documents receivedSent when the recipient's submitted documents have been received and logged.
4. Ready to signSent when a document is ready for the recipient's e-signature.
5. Still unsignedSent when a document is still unsigned after the initial request.
6. Signature receivedSent when all required signatures are in and the document is executed.

Tells a client an invoice is ready, due, or past due, and confirms the payment when it posts, with every figure left in the portal.

1. Invoice readyThe same moment without the figure - the text names the invoice and links to it.
2. Invoice due soonSent before an invoice is due, naming the invoice rather than the amount.
3. Invoice past dueSent when an invoice is overdue, naming the invoice rather than the amount.
4. Payment postedSent when a payment is applied to an invoice, naming the invoice rather than the amount.

Points a client at a new portal message, flags a sign-in from a new device, and proves the phone is the client's at signup, at a sensitive change, and at signature.

1. New portal messageSent when a new message is waiting in a secure inbox or client portal.
2. New sign-inSent when an account is accessed from a new device.
3. Portal signup codeSent when a user verifies their phone at signup.
4. Step-up codeSent before a sensitive action: making a payment, a withdrawal, a change of payment details, a transfer of ownership.
5. Signing codeSent when a signer must prove the phone is theirs before a signature is applied.