When you migrate from live chat to messaging for Web Widget and mobile SDKs, new triggers are created and a number of updates are made to existing triggers to accommodate the functionality changes. If you do not update an existing trigger, these changes do not impact its functionality for live chat.
This article includes the following topics:
For more information, see the following articles:
Trigger changes when migrating from Chat to messaging
The basic way you work with Chat triggers remains unchanged when you move from Chat to messaging. You can view, edit, and add triggers from the main Chat triggers page, accessed from the Chat dashboard at Settings > Triggers.
You’ll see the changes in the Customize trigger section of the Add trigger and Edit trigger pages, when you are viewing an existing trigger, or creating a new trigger.
These changes include:
- A new Channel dropdown menu
- Updated Run trigger options
- Updated condition options
- Updated action options
The Channel menu
The new Channel menu appears at the top of the Customize trigger section. It allows you to run a trigger based on which channel a chat request is received through:

Options include:
- Chat, which runs the trigger only if the visitor is using Live Chat.
- Messaging, which runs the trigger only if the visitor is using the messaging channel.
- Chat and messaging, which runs the trigger if the visitor is using either Live Chat or messaging.
Updated Run trigger options
If you select Messaging or Chat and messaging from the Channel dropdown menu, you can no longer choose to run the trigger when a visitor has loaded the Chat widget, as the Chat widget is not used in messaging.
You can select the following options:
- A visitor requests a chat
- A visitor sends a chat message
Updated condition options
If you select Messaging or Chat and messaging from the Channel dropdown menu, the number of conditions available to you is limited to the following:
- Hour of day
- Day of week
- Visitor previous chats
- Visitor name
- Visitor email
- Visitor triggered
- Account status
- Department status
- Visitor is chatting
- Visitor requesting chat
- Visitor served
- Department (Only available when Run trigger = A visitor requests a chat)
- Sender (Only available when Run trigger = A visitor requests a chat)
- Sender type (Only available when Run trigger = A visitor requests a chat)
- Message (Only available when Run trigger = A visitor requests a chat)
- Queue size (account)
For a complete list of trigger conditions and descriptions, including those that are not available for messaging, see Zendesk Chat triggers conditions and actions reference: Trigger conditions.
Updated action options
If you select Messaging or Chat and messaging from the Channel dropdown menu, the number of actions available to you is limited to the following:
- Send message to visitor
- Set triggered (shown on dashboard)
- Wait
- Set name of visitor
- Block visitor
About the messaging triggers
When messaging is activated for Web Widget and mobile SDKs, you have three default triggers in your Chat triggers list:
By default, these triggers have the Chat channel selected, and are not active. If you would like them to work with your messaging channel, you will need to update the following:
- Trigger status: Click the checkbox to activate the trigger
- Channel: Use the drop-down to select Messaging or Chat and messaging
You can edit the content as needed to work with your messaging channel.
The processes for creating, editing, and deleting messaging triggers are identical to standard triggers, with one exception. If you select a condition or action field that is only available in the Chat channel, then select Messaging or Chat and messaging from the Channel menu, you will not be able to save the trigger settings until you have updated the fields.
First Reply
This trigger sends an automated reply to customers that request a chat, so they know their request is being attended to.
The trigger is set up as follows:
- Run trigger: When a visitor requests a chat
- Check conditions: Check all of the following conditions
- Visitor requesting chat | Is true
- Perform the following actions
- Wait | 5 (in seconds)
- Send message to visitor | Customer Service | Thanks for your message, please wait a moment while our agents attend to you.
Request Contact Details
When your account is set to away, this trigger asks customers requesting a chat to leave their email address.
The trigger is set up as follows:
- Run trigger: When a visitor requests a chat
- Check conditions: Check all of the following conditions
- Account status | Equals | Away
- Perform the following actions
- Send message to visitor | Customer Service | Hi, sorry we are away at the moment. Please leave your email address and we will get back to you as soon as possible.
All Agents Offline
When all agents are offline, this trigger send an automated reply to warn the end user to expect a delayed response..
The trigger is set up as follows:
- Run trigger: When a chat message is sent
- Check conditions: Check all of the following conditions
- Account status | Equals | Offline
- Perform the following actions
- Send message to visitor | Automated Response | Hi there! Thanks for reaching out to us. We're offline right now, but we'll respond to your message when we're back online in a few hours.
17 Comments
Hi Jon,
Could you explain in detail what the configurations are for the problematic triggers? Some screenshots of your trigger settings will help greatly too.
Please submit a ticket with the above information to support@zendesk.com and our team will have a check for you, thanks!
Hi There, is it possible for a breakdown of what a messaging trigger would look like if we were wanting to route an end user to a specific group based on the "needs selector/options selector"?
Hi Clik,
You may refer to this article: https://support.zendesk.com/hc/en-us/articles/360057909933#topic_wrf_5km_jnb, particularly the 'Assigning Groups to messaging conversations' part. It shows how you can collect an information from an end-user and to use it to setup routing rules in a trigger.
Best,
There are so many more triggers available for chat over messaging. Is there a plan to offer the same triggers for messaging? Any work arounds in the meantime?
Hi Jordan,
Thank you for reaching out to Zendesk Community! Could you tell us more about your use case and what specific trigger conditions are you looking for/wanting to add to Zendesk Messaging?
Hey Destiny,
The main reason we liked the conditions for chat was that it allowed us to personalize messages based on the IP, page URL etc. A big feature that’s missing at the moment because of the conditions is the proactive greeting as well.
These are the top 3 conditions we would love to have access to on the messaging channel that are currently available on chat:
Many clients have moved over to Intercom chat in the meantime until some of these conditions are available. If these changes are in the roadmap, or you know of any work arounds, please let me know.
Happy to discuss in further detail if needed. Thanks!
Hi Jordan,
The proactive greeting is still not present on our supported features for the Agent workspace therefore I don't have any workaround to share at this time. But, I have forwarded your comment to the PM team as an FYI. For trackable feature requests, I would suggest posting them on our Community site.
Thank you for your understanding.
Hello on our current plan with Zendesk we are allowed to have two concurrent triggers enabled. When attempting to enable more it advises that our plan might need to be adjusted. However, I can't find any documentation on which plans afford what number of triggers. Does anyone have insight on this?
Hi,
Is there a way that we could change the avatar that is used for the chat/messaging trigger messages and replace it with another image (for example, our logo instead)?
Attached are images of what it looks like on the user and agent side which is just a blank standard image.

Hi Issa,
Thank you for your inquiry. Please know that in changing the avatar in Messaging, you can see the available customization in this documentation.
I hope this answers your question. Enjoy the rest of your weekend!
Cheers,
Blanca
I can't seem to find a way for my chat trigger, after updating to messages, to recognise that an agent hasn't sent a first response OR no agent has opened the chat yet - to then wait 60 seconds from when the customer first requested the chat and trigger an apology message for the waiting time. Is this possible?
I noticed one of the settings that was in the chat trigger was not available when I changed it to use for messages. This was the 'still on site' option. I've tried changing other features of the trigger but none work the same way as that did.
Thanks
Unfortunately, this condition is not available in Messaging. For a complete list of trigger conditions and descriptions, including those that are not available for messaging, see Zendesk Chat triggers conditions and actions reference: Trigger conditions.
You may create a new post in the Feedback - Chat, and Messaging (Chat) in our community to engage with other users who have similar needs and discuss possible workarounds. Conversations with a high level of engagement ultimately get flagged for product managers to review when they go through roadmap planning.
Let me know for further questions!
Hello,
I enabled classic chat but don't have the ability to create a live chat trigger. The only option available is "messaging". Please help, when I originally switched from messaging to chat I had the ability to make a live chat trigger but after I reverted back to messaging and later decided to switch to live chat again the functionality seems to work differently.
Anthony Brantley,
I have created a ticket for you to investigate further. Please wait for my update via email and let's continue our conversation there.
What is the logic behind including "customer details" in the chat widget if all our users are supposed to be authenticated? What is the case scenario for this?
We're also getting chat requests simply when someone logs in - they have not started a chat with us - often we send a response but the users is not intending to chat with us - is there a way to stop Zendesk from triggering a chat message to support?
Hi Frank,
Once an end-user has been authenticated and their identity has been verified with Zendesk, the end user will not be prompted to provide their name or email address by the messaging bot as part of the default messaging response as mentioned here.
However, please take note of the current limitation we have for end-user authentication in messaging.
Regarding chat requests, I have created a ticket for you via email to investigate further. Let us continue our conversation from there.
Please sign in to leave a comment.