A lead starts a chat, then the next follow-up is left waiting in a queue. Giantpanda can signal when a chat is created or when a CRM activity is created. A Zap can use those events to send an SMS through Mobile Message, giving a sales or service team a prompt while the conversation is still recent.

This is particularly useful for operators who rely on Giantpanda to turn incoming leads into booked meetings. A Chat Created event can send a short acknowledgement to the lead, while Activity Created can alert a staff member that a meaningful action has been logged. Mobile Message's Inbound SMS Received trigger can also start Giantpanda's Start Chat action, creating a lead and beginning the chat automation after someone texts your Mobile Message number. These workflows are separate and one-directional, so they do not promise that every Giantpanda conversation is mirrored in Mobile Message. Choose the event and outcome carefully in Zapier, map the contact details, and test the customer-facing wording before enabling the Zap. Both services need to be connected for the workflow to run.