I have a test real-time journey (one contact). The contact has a valid Cell Phone number. If I "test send" the Text Message using the cell phone number, the user gets the message just fine. Whenever scheduled through the journey, it gives a "Invalud Recipient Number" error. See pic below (so frustruting, this tool).
Any ideas?
Hi,
Thanks for your sharing.
However, on the issues of functional design, it is recommended to post your proposal in Ideas forum in order to drive it to be improved.
Or you could raise a support ticket for further help.
So very frustrating....
1) Mobile Numbers need the "+", plus the country, then the mobile number. This means that you either need to formalize all of your mobile numbers (because most companies in america just use xxx-xxx-xxxx for the mobile number field), OR:
2) You can make a new Computed field, which adds the +1 to the mobile number field, BUT, don't forget, any user who then uses 1-xxx-xxx-xxxx will error out as well. Frustrating that the Mobile Phone field is free-form text, but requires something very formal and counter to how these numbers are stored within CRM in america.
3) ALSO, you then need to make sure the "Consent Center" in Real-Time has a Marketing Communications consent record setup for the number.
This is alot of trial and error to get this tool to work. Sad. Also, other things to note:
4) Email Templates are separate between Outbount marketing and Real-time. Why?
5) Company Assets are separate between Outbound marketing and Real-time. Why?
6) Real-time cannot use cards like Tasks, Call, Run A Workflow, etc. You can only make a journey that sends an email or a text message - thats it. Why?
7) Real-Time survey responses are not tracked (even when a Consent record is there). So, if you make a journey in Outbound, send an email with a Survey link, everything is tracked fine. Do the same in Real-Time, and the "tracker" always says "Marketing Recipient", it is never tracked against a contact. Why?
André Arnaud de Cal...
291,979
Super User 2025 Season 1
Martin Dráb
230,848
Most Valuable Professional
nmaenpaa
101,156