Skip to content
ChatterfyHelp Center
HomeGeneralCRMAI ManagerTrackerPlatformsFAQUpdate log
Main
Bot Settings
Automation & AI
CRM defaults
Flow Settings
AI Settings
Steps
Communication
Changes
Terms
Tracking
Additional
Messenger
Client card
Chat data
Chat data — main card tab
Manual — Manually Changing Lead Parameters
Custom Data — manually filling in custom fields
User Information — basic lead data
Tracker Data — traffic source data
Show Chat Events — displaying service events
Actions — exporting and clearing a conversation
Events
Users
Mailings
Analytics
  1. CRM
  2. Chat data
  3. Show Chat Events — displaying service events

Show Chat Events — displaying service events

The Show Chat Events block in → the Chat data tab — a toggle for displaying system events inside the conversation. When enabled, technical entries appear in the chat feed alongside regular messages: s

Updated June 21, 20263 min
The Show Chat Events block in Customer Card→ the Chat data tab — a toggle for displaying system events inside the conversation.
When enabled, technical entries appear in the chat feed alongside regular messages:
  1. status changes
  1. transitions between steps
  1. tag changes
  1. AI calls
  1. execution errors
Without this toggle, the operator sees only user messages and replies.
With Show Chat Events enabled, you can see what happens between messages at the level of bot logic and automation operation.
Show Chat Events does not change how the bot works — it only displays internal events in the CRM interface. This is a viewing and debugging mode, not separate automation logic.


When to use it

  1. A lead is “stuck” in a flow — you need to understand at which step
  1. AI Reply was not sent — you need to find where the error occurred
  1. Checking Condition and Change Tag logic
  1. Auditing AI Routing — understanding when AI made a decision
  1. Checking transitions between flow and step
  1. Analyzing automatic status changes



Which events are displayed

When Show Chat Events is enabled, system entries appear in the chat feed.

Lead parameter changes

Event
What it shows
Change Status
Changing the conversation status
Change Step
Transition between flow steps
Change Flow
Switching flow
Change Tags
Adding or removing tags
Change Sale Status
Changing the sales stage
Change Operator
Assigning or changing the manager
Examples:
Change Status: Waiting → Auto
Change Step: Welcome → Qualification
Change Tags: +vip


AI events

Event
What it means
Request AI Summary / Router
AI analyzes the context and makes a routing decision
Request AI Reply
AI generates the reply text
AI Error
AI request error
AI Timeout
AI provider timeout
This is especially useful when debugging:
  1. AI Reply
  1. AI Routing
  1. AI Summary
  1. AI transitions within a flow


Execution errors

When errors occur in automation, entries such as Error or AI Error are displayed.
This usually means:
  1. an AI provider error
  1. a webhook issue
  1. an invalid step
  1. a Conditions error
  1. timeout
  1. missing variable
  1. a routing error
Show Chat Events shows that an error occurred, but it does not always show the full cause. For in-depth diagnostics, you may need AI logs, webhook logs, or to check the flow logic.


How to enable / disable

The toggle is located in: Customer Card→ Chat data → Show Chat Events.
After you enable it, technical events start appearing directly in the chat feed.
After you disable it, only regular user and operator messages remain.
If you enable Show Chat Events, service events will be displayed in all chats until you turn the toggle off again.


Use cases

Buyer debugs a flow

The operator reports: “The lead is stuck at Welcome and doesn’t move forward.”
Buyer opens the chat and enables Show Chat Events. They see: Request AI Summary / Router → Error.
They understand that the problem occurred during AI Routing.
After that, they go to check: AI Routings — Deep Dive, AI Settings — Bot Personality, the routing model prompt.

Sales checks qualification

The Sales manager does not understand why the user does not have the qualified tag. They enable Show Chat Events and see: Condition → False. Because of this, Change tag did not run at all. The problem turns out not to be in Tags, but in the flow branching logic.

Support checks the automatic transition

The lead should have automatically transitioned: Waiting → Auto. But the automation did not run. Through Show Chat Events, the operator sees: Change Status did not happen at all. This means the problem is either in the trigger, the Condition, or the step execution.


What to keep in mind

Show Chat Events is a debugging tool, not an everyday operating mode.
When this mode is enabled, the chat feed quickly gets cluttered with technical events:
  1. AI Requests
  1. Change Step
  1. Conditions
  1. Status changes
  1. Errors
This makes it harder to read the regular conversation with the lead.
Recommended workflow:
Enable Show Chat Events.
Find the problem.
Turn it back off.
Show Chat Events does not change the chat history and does not rerun automation. It only visualizes events that have already occurred.


Frequently asked questions

No.
Show Chat Events is displayed only inside the CRM for operators.
The Telegram user does not see:
AI Requests
Change Step
Errors
internal automation events

No.
The setting is applied globally for the current operator and affects how events are displayed in all chats.

Yes.
After Show Chat Events is enabled, past events that have already been recorded in the chat history are also displayed.

Possible reasons:
AI Reply was not used in this flow
AI Routing is disabled
Show Chat Events is disabled
the event was not recorded due to an execution error


Related

Customer Card
The client card is the right-hand panel in , which opens when you click a chat. It contains 3 tabs : Chat data (current lead parameters + actions), Events (event feed), Media (all files from the conve
Manual — Manually Changing Lead Parameters
Manual is a block in → the Chat data tab, where the operator manually manages key lead parameters. Here you will find 6 main fields used in daily work: Sale stage, Status, Flow, Step, Manager, and Tag
Chat Status — conversation statuses
Status is the main technical parameter of a conversation. It shows the current state of the chat and determines: who responds to the user — AI or an operator whether Push Messages (Global/Step push) a
Tags — tags for segmentation
The Bot Settings → Tags section is for tags used to label leads. They are similar in concept to , but much more flexible: a single lead can have multiple tags at the same time. Use tags for everything
AI Reply — smart replies via AI
The AI Reply step is the main step for communicating via AI. In this step, the bot generates a response using a neural network, taking into account the lead’s message, the conversation context, flow-l
AI Routings — Deep Dive
• AI Routings is the most misunderstood layer of AI in Chatterfy. It seems similar to a regular , но устроен иначе и решает другую задачу. Reference на сами Routings — , but it is built differently an
Flow Settings
The Flow Settings section is the heart of Chatterfy . This is where the bot’s communication logic with the lead comes together: which messages are sent, in what order, which conditions are checked, wh
Condition — conditional branching
The Condition step branches the flow based on exact values in the lead’s data. Tag exists — left. deposit greater than $100 — right. time from 12 to 18 — third branch. This is the opposite of “AI Rout

Was this article helpful?

BackTracker Data — traffic source dataNextActions — exporting and clearing a conversation

On this page

  • When to use it
  • Which events are displayed
  • Lead parameter changes
  • AI events
  • Execution errors
  • How to enable / disable
  • Use cases
  • Buyer debugs a flow
  • Sales checks qualification
  • Support checks the automatic transition
  • What to keep in mind
  • Frequently asked questions
  • Related