Skip to main content

Timeline for What does QueueMO API actually do?

Current License: CC BY-SA 4.0

7 events
when toggle format what by license comment
Oct 6, 2023 at 8:59 vote accept ZeRoberto
Oct 5, 2023 at 11:23 comment added Duc Le Like instead of the real person texts a keyword to your Short/Long code to opt it/opt out, you do it for them through the API
Oct 5, 2023 at 11:16 comment added Duc Le messageText property is to use for Opt In/Opt Out in Mobile Connect channel. E.g. you put your keyword in messageText , then if it will be captured in a Mobile Opt-In msg you created for that keyword, and then you are opted in. You can try it yourself to experience
Oct 5, 2023 at 11:05 comment added ZeRoberto Thanks, this is exactly opposite to what SF Support told me btw, they said you can send an SMS directly from the API, but I get your point and that's how I thought it works after checking what MO stands for. That being said, in the payload of the QueueMO why is there a messageText prop? where is that stored? "Mobile opt-in" template type in MobileConnect picks those QueueMO records up?
Oct 5, 2023 at 10:55 comment added Duc Le Like I mentioned in my answer. It is the inbound mobile message, not outbound msg. So basically, it doesn't send anything to the subscriber but the MC system. You can create a separate mobile msg to capture the queue MO send so it can send a confirmation msg after that. help.salesforce.com/s/…
Oct 5, 2023 at 10:26 comment added ZeRoberto Thanks. But at the end of the day, is an SMS message triggered TO the person who provided consent through a web form? So let's imagine I collect people phone numbers in a web form, can I trigger the QueueMO to both subscribe them AND send them the first message from the keyword of my choosing?
Oct 5, 2023 at 7:52 history answered Duc Le CC BY-SA 4.0