Skip to main content

Introducing Mobile Inbox



Today, we’re excited to announce Mobile Inbox, a new customer-friendly home for in-app messages. In-app messaging proved its value as an effective channel for prompting action during app sessions—tapping into promotions, completing outstanding actions, or learning more about users—but its instantaneous nature can interrupt an otherwise fluid app experience. Unfortunately, your users can’t reread or re-engage with your messages once dismissed.

With Mobile Inbox, we’ve mitigated that disruption and offer marketers a new venue for sharing that same, highly-personalized in-app content in a place that is available for revisiting at any time. Messages are natively stored inside each user’s Mobile Inbox for sorting and recall—just like an email inbox! Message delivery is unobtrusive and conveniently saved.

To learn more about mobile inbox, check out the documentation below, and if you have any questions, please don't hesitate to let me know in the comments!

_Blog Post: https://iterable.com/blog/introducing-mobile-inbox/_
_Release Notes: https://support.iterable.com/hc/en-us/articles/360038860371_
Hi Sarah!

Justin from Fundsfy here 😀
I attended the Product Roadmap webinar on Tuesday on 3/3, and I have a few questions that I would like to have addressed.

Quick overview:
1. Our App is hybrid and built on Ionic so we are unable to use the Iterable SDK, therefore we have to make InApp API calls to use the Mobile Inbox, but this limits our abilities for having notifications marked as read. The consume call we are using to delete messages.
2. I have had many support tickets for this, and finally it was put in as a feature request by our CSM. I understand that this is put through to the product team.

My questions:
1. When can we expect a mark as read API call? For example: `POST /api/events/trackInAppOpen: "true” or `POST /api/events/trackInAppOpen: "false" depending if the user opened the message in the Inbox or not. Needs to be a boolean.
2. We keep receiving error messages when requesting more then one notification at a time. I believe this could be fixed if Iterable makes it possible to ask for notifications doing pagination, i.e: I ask for 20 messages, and later I ask for the next 20 messages (first call: returns the messages 0-20, second call: returns the messages 20-40 (or less if there are no more than 40), etc.) What is the timeline and scope for this?
Hi @Justin Rivera , thanks for reaching out to us. Please review our documentation here for details on supported features. Our product team applies lean product principles in building new features and we are just getting started with mobile inbox. This feedback will allow the team to effectively prioritize and define the next iterations.

Reply


Terms & ConditionsCookie settings