Checklists
Write an ordered list of outcomes with your own words on it, let an agent's Show trigger put it on the chat bar for the right people, and read which item they are stuck on.
A Checklist is an ordered list of outcomes a person works through in any order. You write and publish it under Checklists on Configure > Flows; an agent's trigger decides who sees it, when and where.
Before you start
Creating, editing and publishing takes an admin. An item ARCY does for the person needs a flow published to this environment (Flows). An item done by hand needs a Custom event, a route or a flow's last step to mark it; wire arcy.track() first where nothing else does (Reference).
Setting it up
Create Checklist asks for a Name your team alone sees.
What visitors read holds the Title and an Intro (optional). Both take attributes as flow copy does and are translated on Localization under the Checklist's name.
Items, at most 12, in the order visitors read them, each with an Item title and a Line (optional). Flow names a flow this environment serves: tapping the item runs it, and a completed run ticks it. Done rule ticks it when the person did the thing by hand: A Custom event, A route reached or A flow's last step reached. An item with no flow needs a Done rule, or the list cannot publish.
Publish freezes the list for this environment; a later edit reads Pending changes until you publish again. The row's menu holds Duplicate and Delete, refused while an environment serves the list or a trigger names it.
Showing it. On a Target under Agents, add a trigger and set Then to Show. Checklist picks a published list. The condition, labelled Where it shows, takes page and element conditions only: it says on which pages the strip sits, not when a show begins. A second list can wait for the first through the standing condition Checklist state: Not shown, Shown, not done or Done.
What it changes
The strip, the list's title and "2 of 5", shows on every visit while the trigger holds. A tap opens the card: the items in your order, done ones ticked, an item with a flow tappable, one with no flow read only. The list leaves for good when every item is done, the Target completes or its Window ends; the X hides it for the session only. While a flow runs the strip steps aside and returns after; a Suggest offer waits for the next session. A visitor outside the chat bar audience gets the bar with the strip and loses it on the X.
Done is counted from what the person did since entering the Target, so something done before the list appeared is ticked on first sight. Republishing changes no tick.
Needs review marks an item whose flow is unpublished, deleted or out of the showing agent's audience, or that has neither flow nor Done rule; the list still publishes and the item is read only.
Item funnel, on the Checklist page: people Shown, people Done, the median days to the last item, then per item Shown, Tapped and Done, split by the agent that showed it. Anonymous browsers count. A person's page on Users lists each list they were shown, which agent showed it and each item's done day, by hand or with ARCY. People on the Target page gains a Checklist column. A person who ran an item's flow counts as Flow-assisted in the Target's Lift; one who only saw the strip does not.