Skip to main content
LaunchsiteOS
Get Started →

Automations

Automate coaching workflows. Keep the steps visible.

Build client follow-ups in LaunchSite OS with event triggers, delays, conditions, and actions. Configure a workflow, review what it will do, then activate it and inspect its run history.

Start free trialExplore the platform
Product previewAutomation builder canvas with a check-in trigger, an AI agent step, a two hour delay, a condition, and a send message action

A workflow you can read

Every step on the canvas,in the order it runs.

The branch that fires when energy drops below five is drawn where you can see it. Select any step to edit exactly what it does, without leaving the diagram.

Visual automation with the send message step selected, showing its editable message body in a side panel

The pieces

Triggers, delays, conditions, actions.

Real practice events start the workflow: a check-in lands, a phase advances, a client goes quiet. What happens next is yours to arrange.

  • 01Triggers fire from events that actually happened
  • 02Delays wait in real time, not on your calendar
  • 03Conditions branch on the client’s own data
  • 04Actions message, assign, or flag for your review
Automation list showing saved workflows with their triggers and current state

Approval gate

Hold supported message drafts for review.

When a workflow uses an approval hold, its message draft waits for your decision. Other activated actions and scheduled messages can send automatically according to their configuration, so review the channels and steps before turning a workflow on.

  • 01Held drafts wait in a review queue you control
  • 02Edit before approving, or reject outright
  • 03An approval-held step resumes from your decision
Review banner reading that seven drafted messages are on hold, with an open review action

How automation behaves here

You configure the workflow.The system runs its steps.

An activated workflow can send a message or perform another configured action without you opening the app. Choose its scope deliberately and review its history; a completed send cannot be recalled by pausing the workflow.

  • 01Every workflow is readable as a diagram before it runs
  • 02State-changing steps run from an explicit coach instruction
  • 03Approval holds apply to supported steps when configured
  • 04Runs keep durable history, so you can explain what happened
  • 05Any workflow can be paused or edited without losing its history

Choosing the right follow-up workflow

What is an event workflow?

An event such as a submitted check-in starts a sequence. You arrange supported actions, delays, and conditions to decide what happens next. For example, a check-in can start a follow-up that branches on an answer and sends a configured message.

How are scheduled messages different?

Scheduled, birthday, and holiday messages use their configured time and audience. Review the recipients, message, and channels before activation. Their delivery is separate from event workflows, so an event workflow’s approval hold does not also hold scheduled sends.

Explore the platform

The rest of the practice.

Automations are one system of six. They share the same client record.

Your practice, operating clearly

Automate the follow-up you forget when the week gets busy.

Start with one workflow and watch what it catches.

Start free trialView pricing