Pulse
Read what the agent did this week, close the questions it could not answer, and find the step where a flow loses people.
Pulse is where you read what happened in the selected environment: the insights ARCY found, every conversation, the questions it could not answer, and how each flow is doing.
Before you start
Pulse fills as traffic arrives. Until the install is confirmed on Installation, every section offers that page instead of numbers.
Conversations and the questions in the content gap table need Store conversations turned on for the Product. With it off, the conversation list stays empty and the content gap table keeps its counts but shows Question not stored. See Consent.
What it changes
Nothing on Pulse changes the widget. Everything is read from the environment picked in the sidebar, so a development test session never lands in production numbers.
Insights are short findings, each with a number and a button that opens the place it
points at. A Best guess: line is a possible cause, not a measured one. Revenue-ranked
findings need plan_value and plan_cycle sent through identify(), and the section says so
until they arrive. See Attributes.
Conversations lists every conversation, searchable by message text, with how many answers the visitor rated good or bad. Open one to read it in full, with What the agent did above each answer: the searches it ran, the pages it read, whether it handed off.
Content gap is the table of questions ARCY could not answer from your material: the question, how often it was asked, when it was last seen, and the agent's note of what it looked for. One row is one question however it was phrased. Click a row to filter Conversations to the conversations behind it. Close a gap on Train.
Flows covers the flows published in this environment plus any flow that ran inside the chosen date range: the last 7, 30 or 90 days, or any two dates. The range drives the three tiles (Runs started, Completion rate, Live flows), both charts and the table. Drafts stay out of the numbers. Every run ends in exactly one outcome:
| Outcome | Meaning |
|---|---|
| Completed | The person reached the last step, even if a step failed on the way. The error still counts in Errors. |
| Failed | A step errored and the run never finished. |
| Dismissed | The person closed the flow. |
| Left unfinished | No ending and no activity for 30 minutes. |
| In progress | The run is still open. |
How every run ended stacks those outcomes per day. Runs by flow draws one bar per flow for the ten busiest and rolls the rest into Other flows. Click a bar or a flow name to open that flow's own page: the last 30 days of runs, the step funnel with its Drop-off step marked, Errors, How runs started, Agent suggestions and Self-heal history.
Flows that are not counted are listed under the table as Not tracked in this environment, with the reason. Start tracking publishes the flow here; a flow with no steps offers Open in builder instead. Only an organization admin sees either button.
When it goes wrong
The Flows section says the range went past the scan limit. The numbers cover only the most recent events. Pick a shorter date range.
A flow shows Few users so far. Its weakest step is not highlighted until enough people have run it.
The content gap table says the Product has no training content. ARCY has nothing to answer from, so every question lands here. Add a source on Train.