From ae6bb3dd8047a0ffb8b8a6b32652be5747beda52 Mon Sep 17 00:00:00 2001 From: Fawas Date: Tue, 4 Nov 2025 14:38:35 +0530 Subject: [PATCH] Update Message Events.md --- .../4. Product Features/03. Flows/4. Others/Message Events.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/4. Product Features/03. Flows/4. Others/Message Events.md b/docs/4. Product Features/03. Flows/4. Others/Message Events.md index 1a499d499..2af8b2b01 100644 --- a/docs/4. Product Features/03. Flows/4. Others/Message Events.md +++ b/docs/4. Product Features/03. Flows/4. Others/Message Events.md @@ -11,8 +11,8 @@ For sending messages, the message is routed through Gupshup, to WhatsApp Busines All messages being sent from Glific to Gupshup to WhatsApp are tracked and for each message sent, there are events returned to show the status of the message. -For the tracking to be enabled, please make sure that you have activated tracking of these events in your gupshup app. Refer [this documentation to configure the read receipts -](https://glific.github.io/docs/docs/FAQ/Read%20Receipts/) +For the tracking to be enabled, please make sure that you have activated tracking of these events in your gupshup app. Refer 26th step of [this documentation to configure the read receipts +](https://glific.github.io/docs/docs/Pre%20Onboarding/Gupshup%20Setup) The status of each message can be found in the `messages` table, under the `bsp_status`in the organization’s BigQuery account.