Help Center

Explore our knowledge base
article

FAQ: In-app Messaging

 

The in-app Messaging feature of iAdvize Messenger allows you to chat with your mobile app users (iOS &Android) thanks to the mobile SDK. Your visitors can reach you even when your teams are unavailable and are immediately notified on their phone as soon as they get an answer. 

1/ Is it possible to enable GDPR consent? 
GDPR consent can be enabled during the mobile SDK integration phase. The first message sent to visitors asking them for their consent can be set up by the integrator. Moreover, this message should include a link redirecting visitors to a Web page specifying the brand legal conditions
 
2/ Is it possible to integrate external chatbots?  
No. 
 
3/ Would it be possible to modify the location of the chat button? 
We position the chat button at the bottom left corner. The integrator can change this default position. However, visitors cannot drag it on their mobile screen. 
 
4/ Will it be possible for visitors to retrieve the history of their mobile conversations on their desktop devices?  
No. However, visitors authenticated on a mobile app from a smartphone and another mobile device (i.e. a tablet) will be able to retrieve the history of the conversations they have had from these different devices. 
 
5/ Will it be possible to configure the mobile SDK from the administration (colour/font customisation, enabling/disabling the chat button, etc.)? 
No. All the mobile SDK settings should be changed by the integrator during the mobile SDK integration.
 
6/ What are the different steps required to integrate the mobile SDK?  
  1. Creating a new (iOS and / or Android) mobile app on the administration. Once the information about the mobile app(s) is entered, a secret key and application ID will be provided for the second step. This first step only requires a dozen minutes as it is simple and quick to complete.
  2. Integrating the mobile SDK to the mobile apps. This operation only requires a few hours of development from integrators. Using the secret key and the application ID provided by iAdvize in step 1, the integrator will be able to integrate the mobile SDK, customise the conversation interface, the chat button, the GDPR link, etc. The integrator will be able use a demo app and a technical documentation made available on GitHub. Moreover, the Cheat Sheet are already available to explain this second step. 
 
7/ Will respondents (professional agents and ibbü experts) be able to use canned answers?  
Yes, professional agents and experts have access to the same features as when they handle social/messaging conversations (excluding end of conversation tags).
 
8/ Will it be possible to block a malicious visitor interacting from a mobile app? 
No. However, an expert or a professional agent still have this option for classical chat conversations so with visitors chatting from a website. 
 
9/ Will respondents (professional agents and ibbü experts) be able to see the mobile screen of visitors they are chatting with? 
No.
 
10/ Will it be possible to add tags to conversations? 
  • For conversations handled by professional agents: yes 
  • For conversations handled by ibbü experts: yes, at the end of Q2
 
11/ How are slots dedicated to mobile conversations managed? 
Professional agents and experts will receive conversations in push mode. These mobile conversations will be managed in slots dedicate to third-party messaging channels (mobile app, Facebook, Twitter, Messenger, SMS...).
In other words, if professional agents or experts can receive a maximum of 3 chat conversations and are indeed handling 3 chat conversations, they can receive up to X additional conversations from third-parties in their conversation panel. 
You can define this number of slots in the iAdvize platform directly.
 
12/ Can agents snooze a conversation to free a “mobile slot”? 
Yes, you will find more information on conversation management here.
13/ Will ibbü experts be able to snooze a conversation to free “mobile slot”? 
Yes.
 
14/ What happens if visitors do not answer the agent/expert's last message(s)?
The agent/expert has to end the conversation. If the visitor eventually replied, then a new conversation will be created and routed to an available agent/expert.
 
15/ To which agent/expert a transaction is assigned to?
Transactions are always assigned to the last agent or expert who handled the conversation. That is to say the agent/expert who sent the last message before ending the conversation.
 
16/ Will it be possible to create targeting rules and associate them with a routing rule? i.e. I want to display the chat button on a “Gardening” page only and route the generated conversations to the appropriate experts.
It will not be possible to use targeting rules to choose where to display your chat button. However, it is possible to route conversations to the right routing group thanks to routing rules. 
 
Here are the steps you should follow to do so:  
  1. Create a “mobile app” targeting rule in the administration (once again: this rule won’t be used to target mobile users but only to route conversations. These settings will be simplified in a future version of the mobile SDK). 
  2. Associate this targeting rule with a routing rule (just like for chat conversations on desktop devices)
  3. Retrieve the targeting rule ID created in step 1.  
  4. Integrate this ID within your mobile app page where you want to display the chat button, in the code provided by the mobile SDK. 
 
Notes: it is not possible to create targeting rules like on desktop devices. The targeting criteria offered on desktop will not work for mobile devices. When creating the targeting rule, choose the “Mobile App” channel, there will not be any criteria to choose and you simply have to save your rule. 
It is then up to the integrator to choose to display the chat button on specific pages thanks to some customised display rules the integrator will have to set up on the mobile app. Thus, the targeting rules need to be handled and set-up when the mobile SDK is integrated.
 
17/ Is the SDK able to recognise the visitor language, i. e. routes the conversation to the operator who speaks the same language?
Yes! Technically, integrators have to use the device language (= language set up on the mobile OS) or the language chosen by the visitor in the app. Once this setting is defined, the conversation is sent to our routing engine and pushed to an appropriate operator.
 
 
18/ How heavy will the mobile SDK be?
  • For Android: ~300ko
  • For iOS: ~7Mo
19/ What are the package managers?
  • For Android: Github
  • For iOS:  Cocoapods/Carthage

20/ What are the technical limits regarding the sending of files/images by the visitor?

  • Authorized file formats: all types of images (JPEG, PNG, GIF,...) & PDF
  • Maximum size: 10MB