Skip to content

Documentation

How do I send lifecycle emails without building it myself?

Describe what should happen in a sentence, and Kicklace writes the automation, the list and the email template it needs, as one plan you approve once. “Welcome everyone who signs up” or “check in with anyone who never activates” is enough. Nothing sends until an automation is switched on, and nobody lands on a list without the exact words they agreed to.

How Kicklace builds it

An automation is one sentence in up to five parts — when something happens, wait, only if it is still true, then do this, otherwise do that — and the "when" and the "who" are usually a population: one of the seven lifecycle rungs, or one of Kicklace's own groups like Quiet or Slowing. Say "when somebody enters Paying, welcome them" and there is nothing to define: the population already exists and is kept current on its own.

Ask for more than one automation at once — "set up a welcome sequence for the waitlist" — and Kicklace writes a plan: the list with the consent sentence people will actually agree to (10 to 500 characters, stored word for word — an import never puts anyone on a list on its own), the email template in your workspace's own style, and the automation that ties them together, in the order they need to be built. You approve the plan once, and Kicklace builds every piece itself and switches the automation on — nothing here is a canvas you drag boxes around.

Change your mind later and the same conversation makes a precise edit rather than a rebuild: say what should be different about one automation, and only the part you named moves.

Set it up

  1. Press ⌘K anywhere, or Ask on the page it concerns, and describe what should happen in a sentence.
  2. Read what comes back — the list, the template, the automation's own When → Wait → Only if → Then — as one proposal.
  3. Press Approve. Kicklace builds the list empty, writes the template, and switches the automation on.
  4. If something needs to change later, open the automation and press Modify — the same conversation, editing one part rather than starting again.
  5. On Free, Kicklace still writes the plan and shows it to you. Approving it, like anything that sends or runs by itself, is part of Pro, and a fourteen-day trial is offered at that moment.

What it does not do

It never emails somebody who has not agreed to that exact list — consent is stored, never assumed, and importing rows never subscribes anyone. Sending, and an automation that runs, are part of Pro rather than Free. And nothing fires the moment it is approved: a Then step only runs when its own trigger — a population entered, an event, a schedule — actually happens.