Specialists

A Specialist works toward one goal for your Product: its Type, a goal sentence, What counts as reaching it and a Window. It races Experiments toward that goal. Specialists lists them with their Type, Live Experiments, Best Goal rate, Helped this week and Last Report; Type and Archived narrow the table.

Before you start

Creating, editing, publishing and accepting a draft take an admin; members read every page and can chat with a Specialist. Your Plan caps how many Specialists are not archived (Billing); at the cap Create Specialist says so. An Experiment counts only consented browsers (Legal) in the environment in the address, and an event in What counts counts from when it is first reported, so declare and wire it before you publish (Events).

Creating a Specialist

Templates lists the Specialist templates with a Type filter and a search. Pressing a card writes the whole Specialist as Drafts: its goal, what counts, its Window and one to three Experiments with their Flows or Checklists. Every value ARCY found on your site reads From your site; every blank reads Needs you and holds that Experiment back until you fill it. An Experiment waiting on a flow template offers Build the flow; the built Flow becomes its Action (Flows). An empty Specialists page offers four templates, one per Type.

Create Specialist starts from nothing. The Type is Conversion, Activation, Retention or Support. It sets the starting Window, 30 days for Retention and 14 for the others, and never limits which Experiments the Specialist can run. What counts is one or more conditions joined by or: an event from arcy.track(), a route reached, a flow's last step, Identified or Came back. Avoiding this counts turns it around, so a person succeeds when the Window ends without it; only an event or a route can be avoided. The Window is 7, 14, 21 or 30 days, or Custom from 1 to 90, counted from the first time ARCY acts on the person. Instructions is what the Specialist reads on every run, such as "Never offer a discount"; visitors never see it.

Settings holds the same fields. A change to What counts or the Window restarts every Goal rate of the Specialist from today, and asks first; past Reports stay as written. A Retention Specialist adds the At-risk alert: when its people inside the Window who have not come back double in a week and reach the Floor (10 by default), your team hears about it (Alerts).

Archive pauses every Experiment in every environment and frees the Specialist's place on your Plan; its Reports stay readable under Archived. Delete is offered only while none of its Experiments was ever Live.

Experiments

A Specialist page holds one The race card: its live Experiments, and those paused after running, each with its Goal rate, the people behind it and its distance from the Leader. Everyone the Specialist helps gets one of them, drawn once and kept, so their Goal rates compare fairly. The card's badge is the Verdict, Clear winner, Leaning toward, Too close to call or No Verdict yet. An Experiment has no end date, so the card counts the day of the race and how far the next Report is. Pick a winner keeps the Experiment ahead live and pauses the rest: an admin's press, offered at Clear winner or Leaning toward, with Undo for half a minute. New Experiment opens a blank Draft.

The card's second tab is Time to value: the middle of the time people take to reach an event that counts as value (Events). Per person runs from a first visit and Per question from a chat question, both reading With ARCY against Baseline. The two sides of Per question start their clocks in different places, which the tab says above the figures. A group nobody has reached reads Not measured, never a zero, and the gap between the middles waits for 30 on each side. The figures cover the whole Product here, not one race.

Who and when decides who an Experiment acts on and when. Starts when is the Entry: First consented load as Anonymous, The moment identify() resolves, Days since the last Session, Days since the last event, Reached a route (a pattern like /cancel*, acting in that visit), Joined an Insight's people or Not among an Insight's people (Home). Any Type may use any Entry. Only people where keeps people matching every attribute clause, so any clause drops anonymous browsers. Eligible for is how many days after Entry the person may still be acted on, 365 at most; it keeps new people new and is not the Window. Acts when is the one condition that decides the moment: the flow step's condition builder, with standing conditions under checked when the visit starts and at least one live condition, such as the current page.

Action is what ARCY does at that moment, picked from three groups under What it does. Offer a flow holds a Pill above the bar with its X, a Whisper the bar types into its own placeholder, a Peek that raises a short chat panel carrying a start and a dismiss button, and a Run that starts the flow with no tap. Show something holds an Announcement, a card joined to the bar's top edge, and a Show, a Checklist strip above it (Checklists). Ask holds Ask NPS.

How strongly ARCY steps in runs Pill, Whisper, Peek, Run, quietest first. A Whisper or a Peek with no flow puts the cursor in the bar and the chat agent answers. An Announcement takes a title, a text, an optional image address starting with https://, and one button that opens a link or starts a flow, never both. A Run waits for Settle time (2 seconds by default), starts once per person, and the visitor can Stop it. A Show's condition, Where it shows, takes page and element conditions only. Suggest line (optional) replaces the flow's public name.

Ask NPS asks the standard 0 to 10 question in the visitor's language and then the reason. You write nothing for it. One person is asked at most once every 90 days across your Product, and their latest answer becomes an NPS band and NPS score any Experiment can target on under Only people where.

Each type names the oldest arcy.js that can show it, and a page running an older one is never offered it (Updates). An Action naming a flow or Checklist this environment does not serve does nothing here.

The Stage beside the editor plays the Action on the real widget with this Product's Theme, on every edit. Nothing is sent or counted. It switches the resting form, screen width, language and the page behind the widget, and fills Liquid values from Sample values. Preview on your site opens your site in a new tab and plays the Action at once; analytics records nothing.

Publish makes the Experiment Live in the environment in the address; the button waits while changes are unsaved or a blocker stands. Pause stops it acting here and keeps its results; publishing again continues them.

Once an Experiment has been Live anywhere, who it acts on and which type it is are fixed. A change to Who and when or to the Action's type saves through Save as new Experiment: a new Draft under the same Specialist, while the old one keeps its results. Its words, its image and the settle time change in place, with a dated mark on its results, and so do the name and Ignore the limit. Try a different action copies who and when into a new Draft and asks only for the Action. Delete Experiment is offered only while it was never Live.

Ignore the limit, shown to admins only, lets one Experiment act past the Frequency limit's counts; it still adds to them and never acts in the 24 hours after a person says no.

The chat and Suggest experiments

The chat sits right under the Specialist's name, at the top of its page. Chat history, beside Settings, reopens your earlier chats with it; New chat starts over. Before answering it reads its goal, Instructions, Experiments and every Report. A turn may draft one Experiment, a flow, a pause or a Settings change; when you state a lasting fact it offers Save to Instructions.

Suggest experiments shows a plan first, Will build, Will need you and Left out with a reason, and drafts up to three Experiments only on your confirm. Both presses use AI credits; a run that writes nothing costs none. A Specialist holds at most five open drafts; past that, accept or discard some first.

Drafts wait under Waiting for you and in the chat, each with its line of evidence. Accept publishes the draft in the environment in the address; Discard deletes it, and the same draft is not proposed again. Drafts your coding agent wrote over ARCY MCP carry its name. Nothing a visitor sees changes before an admin presses.

Results and Reports

Results opens on Matched, ARCY acted on, Engaged and Reached the goal. Engaged counts the people who took the Action up, each once: a Pill or Peek accepted, a Whisper or an Announcement tapped, a Checklist item ticked, an NPS score given, or a Run's flow finished. It never reads above ARCY acted on. The Goal rate is the share of people ARCY acted on who reached the goal inside their Window, counted once their Window has closed, always beside its count and the one-line definition. Goal rate by week draws a week lighter while some of its people are still counting, and marks the day the Experiment was published or paused or its flow changed. People ARCY acted on lists each person as reached, not yet or missed. Development shows the same numbers from test visits. Best Goal rate on the table waits for 30 final results.

An Ask NPS Experiment opens on an NPS score card instead: promoters minus detractors as a share of everyone who answered, How people scored across the eleven scores, and Their reasons. A reason reads Masked where this Product does not store message content (Legal). A person's own answers sit on their row under Users.

A Report is written in Production each time an Experiment gains 100 final results since the last one; you can also ask for one in the chat once 30 are new. It gives every Experiment's Goal rate and count, a Verdict per race, Clear winner at 95 percent sure, Leaning toward from 80, Too close to call below, what the Specialist learned, and one next step. A next step that pauses the Experiment behind is one press, an admin's. Reports read in the dashboard's language and are never deleted.

The Frequency limit

Frequency limit caps what ARCY starts by itself for one person across every Specialist. Every type counts once, at its first show, a Checklist on its first show only. Per visit is 1 to 3, a visit ending after 30 minutes without activity; Per week is 1 to 14 over the last 7 days. The defaults are 1 and 3. A dismissed Pill or Peek, a dismissed Ask NPS or a stopped Run starts 24 hours in which nothing starts for that person; closing an Announcement is not a no, and it is never armed again for them either way.

Under the cap, three lanes each hold one thing at a time: the Run, the Ask (a Pill, a Peek, a Whisper or Ask NPS) and the one above the bar (a Checklist strip or an Announcement). A Run outranks the Ask lane, so a visitor never meets two offers at once. What a person opens themselves never counts. Admins set it.

See also

• Checklists
• Alerts