You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be better if CX did not have to keep a mapping of messagingServiceSid's.
Instead of getting the messagingServiceSid in the customFields from CX, perhaps we can track the Sid on a per conversation basis, maybe as a room attribute, and then get it from there when it is time to send a templated message?
The text was updated successfully, but these errors were encountered:
Is this possible?
It would be better if CX did not have to keep a mapping of messagingServiceSid's.
Instead of getting the messagingServiceSid in the customFields from CX, perhaps we can track the Sid on a per conversation basis, maybe as a room attribute, and then get it from there when it is time to send a templated message?
The text was updated successfully, but these errors were encountered: