Reading your numbers

A request is one message from one of your users, handled: a question answered or a task done. A conversation is a thread of them, and you can read each one on the Conversations tab, but one conversation can be a single request or thirty, so nothing is counted in them. What you see on a chart, on a card and on your allowance is always requests.

• Open Sites and pick a site. The Overview tab opens first.
• Pick a period from the menu at the top right: 7, 30, 60 or 90 days, all time, or Custom for any dates. Everything below follows it.
• Read the line above the cards. It says what Verb did in that period: requests handled, things done, and for how many people.
• Read the four cards. Requests; People reached; Rated helpful, from your users' thumbs up and down; and Verified actions, the share confirmed to have actually happened. A site with no actions shows Different requests instead.
• Below them are the summary (next section), requests per day, and Do people come back?, which follows signed-in users from one visit to the next.
• Press Refresh to fetch the latest numbers without reloading the page.

A summary groups what your users asked for and what the assistant could not do for them. The AI only groups and names. Every count is counted from your own data, and every quote is a request exactly as it was typed.

• Every Monday, a summary of the week before is emailed to everyone in your workspace and shown on the Overview.
• Ask for one for the period on screen with Summarize this period. On Dev and Starter you can ask for one every 7 days per site, and the button shows the date it comes back.
• Long periods are sampled. Up to 250 requests are read, spread evenly across the period, so a summary of a year covers the whole year. The summary says when it read a sample.
• Read the full summary opens it on its own page: the numbers against the period before, what to do next, everything people wanted, what stood out, how each action did, who came back, and their own words.
• Every summary is kept under Analytics, Summaries, until the conversations it was made from reach the end of their retention.

Open Analytics in the side panel and pick a site at the top. It covers the last 30 days, one tab at a time.

• Activity. Requests per day, how many people asked, and when they use it, by day and hour in your timezone.
• Actions. Anything failing right now at the top, then how many actions ran, how many were confirmed, and a row per action with its most common error. A red count on the tab means something is failing now.
• Could not do. What people asked for that nothing handled, split into actions worth adding and answers worth adding to what it knows. It has the same plan limit as summaries.
• Summaries. Every summary kept for the site, newest first. Open one to read it here, or open it in full.
• Alerts. Every alert for the site, newest first, with the ones you have not seen marked New.

Everyone in your workspace gets an email when:

• An action keeps failing: 3 or more failures in 24 hours, making up 30% or more of its uses.
• The assistant fails to load on one of your pages.

Each problem is emailed at most once a day. A gold count on Analytics in the side panel shows alerts you have not opened yet. Clicking it opens that site's Alerts tab, which clears it. The count is yours alone: somebody else in your workspace still sees theirs until they look.

On a site's Conversations tab, Find one person takes the id your app gives a signed-in user and shows what they asked and what Verb did for them. Use it to help that person. Every lookup is recorded, the id you type is not stored, and only signed-in users can be found.