Journeys: install multi-step customer lifecycle messaging

GuidesUpdated 2026-08-18

A journey in Arino One is a ready-made or AI-drafted bundle of message templates, flows and automations that together implement a multi-step customer lifecycle — onboarding, re-engagement, post-purchase follow-up — installed in one click and always landing as editable drafts, never as live sends.

Why journeys exist

Building a lifecycle sequence from scratch means creating several message templates, wiring up a flow with the right branching and delays, then building an automation to trigger it at the right moment — three separate builders, each requiring its own setup before anything works end to end. Journeys package that whole chain as one installable unit, so a team can go from "we want a re-engagement sequence" to a full draft in a couple of clicks, then spend their time on the wording and timing rather than on assembling the plumbing.

Ready-made bundles vs AI-built journeys

Marketing → Journeys shows two paths side by side.

Ready-made bundlesAI-built journeys
SourceBuilt-in library shipped with the productA plain-English prompt you write
Install actionOne clickGenerate, review, then install
Customisation before installNone — edit after installingThe draft reflects your prompt directly
Feature switch requiredjourneysjourneys plus journeys_ai
Typical useCommon lifecycle patterns (welcome series, cart recovery, feedback loop)A sequence specific to your business that isn't in the standard library

Both paths finish at the same place: a set of draft templates, flows and automations you review and activate individually.

Installing a ready-made bundle

Each card on the Journeys page names what it installs — for example "3 templates, 2 flows, 1 automation" — and lists the steps of the lifecycle in short bullet form, so you know what you're getting before installing. Clicking Install creates every piece as a draft and marks the card Installed. If you install the same bundle again later, the platform reuses the records it already created rather than duplicating them, which matters if a teammate tries to install something that's already there.

Drafting a custom journey with AI

Where the standard library doesn't cover what you need, describe the journey in a sentence: for example, "Send customers an article, ask two days later whether they read it, and if they say yes send a short satisfaction survey flow. Tag everyone who answers." The AI builder returns a structured draft — the message templates it wants to create, the flow logic connecting them, and the automation that will trigger the whole thing — which you review on screen before committing. If the first draft misses the mark, refine the prompt and regenerate rather than installing and fixing it piece by piece afterwards.

What "draft" actually means here

Every template, flow and automation a journey creates is inert until you switch it on. This is deliberate: a journey installed on a live workspace should never surprise a customer with an unreviewed message. After installing, work through the created items in their own sections — message templates may need submitting for channel approval, flows may need timing adjusted for your audience's time zone, and automations need their trigger conditions checked against your actual event names — before flipping each one to active.

Managing an installed journey

The Journeys page keeps a running list of what's installed, with two distinct removal actions:

  • Uninstall deletes the drafts that journey created. Anything you already made live from those drafts is paused or left in place rather than deleted, so activating a piece protects it from being swept away later.
  • Remove entry clears the journey from this list only. Everything it installed — live or still draft — stays exactly as it is; this is for tidying the list, not undoing the install.

Custom and edited journeys

Journeys that don't match a built-in bundle's name — because they were AI-built or because you've since edited the underlying templates and automations — appear in their own section on the page, separate from the standard library cards, so heavily customised journeys don't get confused with an unmodified installed bundle.

Costs

Journeys themselves carry no separate fee — the builder, the AI drafting and the install mechanism are part of the standard product. Once activated, each piece bills the same way it would if you'd built it manually: message templates and automations send on their channel's normal metered rate, and AI generation is metered per the AI provider configured for the workspace, with no Arino markup. See billing and plans and AI and API keys for current figures.

Steps at a glance

  1. Open JourneysGo to Marketing → Journeys. The page is gated by the journeys feature switch, turned on in Settings → Workspace → Marketing.
  2. Browse ready-made bundlesReview the built-in journeys on offer — each card lists what it installs: a number of templates, flows and automations, plus a short step-by-step description of the lifecycle it covers.
  3. Install a bundle, or describe your ownClick Install on a ready-made bundle, or describe a custom journey in plain English for the AI builder to draft — for example, send an article, check two days later whether it was read, then branch into a satisfaction survey.
  4. Review the AI draftRead through the generated blueprint — the templates, the flow logic and the automations it proposes — and refine the prompt if it isn't right before installing.
  5. Install and land in draftInstalling creates every template, flow and automation the journey needs, all as drafts. Nothing sends or triggers until you open and activate each piece.
  6. Edit and activate the piecesOpen the created templates, flows and automations from their own sections, adjust wording and timing to match your brand, then switch each one live individually.
  7. Manage installed journeysFrom the Journeys page, uninstall a journey to remove the drafts it created (live items are paused or left alone), or remove the entry to drop it from the list while keeping everything it built.

Frequently asked

What exactly does a journey install?

A bundle of message templates, one or more flows describing the branching logic and timing, and the automations that trigger those flows off events or schedules. The Journeys page shows the count of each before you install.

Does installing a journey make it live immediately?

No. Everything a journey creates — templates, flows and automations — lands as a draft. Nothing sends or triggers a single message until you open the created items and switch them on individually.

What happens if I install the same journey twice?

Installing again reuses the existing records rather than duplicating them, so you won't end up with two copies of the same templates and automations cluttering your library.

What's the difference between Uninstall and Remove entry?

Uninstall deletes only the drafts that journey created; anything you've already made live is paused or left alone rather than deleted outright. Remove entry simply clears the journey from the list on this page and keeps everything it installed exactly as it is.

How does the AI journey builder work?

Describe the lifecycle you want in a sentence or two — for example, an onboarding sequence with a welcome message, a check-in after three days, and a discount offer if there's been no purchase after a week. The AI builder returns a full draft blueprint you review before installing, and you can refine the prompt and regenerate if the first draft isn't right.

Do I need the AI feature switch to use journeys at all?

No. Ready-made journey bundles install without AI. The AI builder for custom, described journeys is a separate feature switch (journeys_ai) layered on top, so a workspace can offer the built-in bundles without exposing free-text AI generation.

Next step

Apply this to your own deployment

This guide describes decisions we make on live instances. Tell us your channels, systems and region and we will map it to an architecture outline, a provisioning plan and an indicative commercial model — usually within one business day.