Loading

Marketing Cloud - Troubleshooting inbound WhatsApp messages in Journey Builder

Veröffentlichungsdatum: May 12, 2025
Beschreibung

Within Journey Builder, both the Wait Until Chat Response Activity & Inbound Chat Entry Source, are both available to manage WhatsApp conversations with Contacts.

When an inbound WhatsApp message is sent from a Contact, the contents of the message are evaluated based on if/where the Contact is presently in any active Journey(s) along with any matching or configured Keyword values in the following order.

  1. Wait Until Chat Response configured Keyword paths
  2. Inbound Chat Entry Source
  3. Wait Until Chat Response invalid path

Please note Keywords can be used across Journeys, as well as Wait Until Chat Response Activities and/or Inbound Chat Entry Sources.

Based on this, if a Contact is waiting in a Wait Until Chat Response Activity configured with a Keyword path that matches a second Journey with an Inbound Chat Entry Source, if that Contact sends in the Keyword, they will proceed in the original Journey and not be injected into the second Journey.

Also, if a subscriber is a part of multiple journeys(For example,Journey with Inbound Chat Entry Source) with the same channel, the latest published journey will be considered always for the keyword matching in any scenario.

Lösung
  • Use Journey History or the Chat Messaging Extract to review the history of any particular ContactKey and see if they're currently flowing through any active Journeys.
  • To avoid this conflict, the customer should use different keywords for the WaitUntil activity and the Inbound Chat, or only keep one of them active at a time.
Nummer des Knowledge-Artikels

004464103

 
Laden
Salesforce Help | Article