Status Events
The gray status pills that appear in the middle of a conversation — a reference for what each one means and what triggers it.
Overview
Alongside messages, the chat tab shows status events — small pills on the surface color, centered in the thread, that record something happening to the conversation rather than something being said in it.
They're the visitor's audit trail. When an agent joins, when the conversation is handed to someone else, when a transcript goes out, the visitor sees it. Nothing important happens to their conversation behind their back.
How They Look
Consecutive events on the same day merge into a single pill, one line each, with a time next to every line. So a handoff doesn't produce a stack of four separate blocks — it produces one tidy pill listing what happened, in order.
Event Reference
Agent handoff
| Event | When it appears |
|---|---|
| Agent requested | The visitor asked for a human, from any of the three routes |
| Agent request canceled | The visitor went back to Yaplet before an agent picked up, or after the agent who had the chat left the visitor's last message unanswered for 5 minutes |
| <name> joined | An agent joined the conversation |
| Chat transferred to <name> | The conversation was handed to a different agent |
| The team is away right now | The visitor asked for a human while nobody was online |
| The team hasn't been able to reply yet | Nobody from your team replied within 5 minutes of the request |
The last two start out as the "Leave a message" card in the thread, where the visitor can leave an email or go back to the AI — see Email, Ratings & Agent Handoff. Once the visitor saves or closes the card it shrinks to one line, and an older card shows as the plain gray line above.
Lines only your team sees
More lines appear in your team's view of the thread and never reach the visitor:
| Event | When it appears |
|---|---|
| <name> left | An agent left the conversation |
| <name> marked as seen | An agent resolved the chat |
| Rating request | A teammate used Ask for rating |
| Form "<name>" launched | A form was started in the chat |
| Visitor banned, Visitor banned — <reason>, Visitor unbanned | A ban was placed or lifted |
| AI paused — daily AI limit reached (<n> answers in 24 hours) | One visitor used up the daily number of AI answers set in the brand's settings. The line says when the AI resumes (UTC) |
| Workflow started, Conversation stopped by workflow | A chat workflow started, or stopped the conversation (with its note, if it has one) |
| The workflow's email could not be sent…, Could not start the workflow "<name>": … | A workflow ran into a problem, with the reason |
| Bug report collected by the AI: …, Feature request collected by the AI: … | Yaplet collected a report or request from the visitor |
Ratings
| Event | When it appears |
|---|---|
| Rating submitted: … | The visitor picked a score |
| Feedback: … | The visitor left written feedback with their rating |
Visitor details
| Event | When it appears |
|---|---|
| Email updated to <email> | An email address was added or changed |
| Transcript was sent to <email> | The conversation was emailed to the visitor |
| The visitor edited an earlier message | On Messenger or Instagram, the visitor changed a message they had already sent |
Events Versus Recent Events
Don't confuse these with the Recent activity section in the Inbox sidebar. They're different things:
| Status events | Recent activity | |
|---|---|---|
| Where | In the conversation thread | In the Inbox sidebar |
| Who sees them | The visitor and your team | Your team only |
| What they track | Things happening to the conversation | What the visitor did on your site |
See Recent Events for the Inbox sidebar section.
Reading a Thread Through Its Events
The events tell the story of a conversation at a glance. A pill reading:
Agent requested · 14:02 Sarah joined · 14:04 Rating submitted: 5 · 14:32
...describes a two-minute pickup, a half-hour conversation, and a happy customer — without reading a single message. When you're scanning your Inbox for what went well or badly, the events are often the fastest read.