Digital channels drive a cloud contact center. In Infobip, this encompasses some of the most popular chat apps such as Messenger by Facebook, Telegram, Google's Business Messages, WhatsApp, Viber, KakaoTalk, Email, and Social Media channels such as Facebook Posts, Instagram Posts and Messages, and Twitter Tweets & Direct Messages.
This means that you are enriching your customer experience and providing support to your customers via their preferred channels of choice that are most familiar to them.
You can use a broad portfolio of the world's most popular chat apps in Conversations. Below you can find more details about each chat app available in Conversations and how to use them.
Being one of the most popular messaging apps and used worldwide, Telegram is a new channel available in Conversations and agents can use it to communicate with customers.
Currently, agents can send and receive the following:
If a user contacts the support over Telegram, their data can be stored in the People module and used later on in your communication.
According to the Telegram business model, agents cannot start a conversation over Telegram. Customers (end users) need to initiate the conversation.
To enable Telegram as a channel in Conversations, refer to Telegram on our Documentation Hub.
Google's Business Messages
Google's Business Messages is another channel available in Conversations that agents can use to resolve customers’ issues over their channel of choice.
For the time being, agents can send and receive Texts and Images.
If a user contacts support via Google’s Business Messages channel, their data will be stored in the People module so the agents can manage their profiles.
According to the Google business model, agents cannot start a conversation over Google's Business Messages. Customers (end users) need to initiate the conversation.
To enable this channel in Conversations, refer to Google's Business Messages on our Documentation Hub.
Use Messenger by Facebook in Conversations to communicate with your customers. You can use Messenger via templates, same as WhatsApp so the process is fairly similar for both channels.
Note that you need to submit your Facebook page and Messenger channel to Facebook for review. Please check the Messenger App Submission section and Getting Started in case you need help.
Messenger has introduced message tags that are used in mobile-terminated (MT) initiated scenarios. This means that it's possible to send a message to a customer even 24 hours after receiving the last message.
To send a message, you need to select one of the three message tags predefined by Messenger. The message content is free-form, meaning it is not predefined by any template.
Once a message has been sent, the tag that was used will be visible under the actual message inside the agent's desktop window.
When you select WhatsApp as your channel of communication, the system automatically detects if this is the first contact or more than 24 hours have elapsed from the last customer interaction. In this case, you are shown an alert within the message reply box:
You can use WhatsApp templates within ongoing conversations or when starting a new one.
When you select Use a WhatsApp Template, a pop-up opens where the user can select a template from already registered and approved WhatsApp templates. A template can also contain placeholders (variables) for personalization purposes. In this case, the user will need to map all placeholders by entering a value for each.
The experience is same the as for user-defined templates but agents cannot edit the content other than the variables part.
Use WhatsApp product messages type to send an interactive message about a product or service that is present in your catalog. Customers can ask questions about the product, add the product to the cart, and submit the cart without leaving the chat.
To send a Product message, you must have a Meta catalog that is connected to your WhatsApp Business Account. Refer to the WhatsApp channel for more information on Product Messages, as well as the Manage Catalog section.
You can set this up via Conversations API but the agent can only preview this in the agent panel (no modifications available at that time).
Agents can now use stickers to send (over API) or receive messages to/from customers over the WhatsApp channel.
You could send only pictures as attachments (.png, .jpg) using Viber in Conversations up until this point.
Now you are able to send all supported formats by the Viber channel such as documents, PDFs, and spreadsheets.
You can send and receive files as long as they are supported based on the table below:
||Max File Size
||.doc, .docx, .rtf, .dot, .dotx, .odt, .odf, .fodt, .txt, .info
||.pdf, .xps, .pdax, .eps
.xls, .xlsx, .ods, .fods, .csv, .xlsm, .xltx
Use Viber Bots in Conversations and allow your agents to utilize this channel for better customer engagement, and faster support.
With Viber Bots you can:
- Widen reach and extend conversations to new and existing customers
- Customize the end user's keyboard capabilities and use rich media to offer a dynamic and immersive messaging experience
With the API portion, you can provide your customers the possibility to:
- Reply in real time to subscriber requests with the information they need: purchase receipts, account setup change confirmation, bank balance status, and more
- Identify new and existing audience types to engage and send them customized offers
You can only start a conversation with the customer if they have subscribed on their mobile device through Viber. If they have not subscribed, you will not be able to communicate with them using Viber Bots.
You can use the following types of messages in Viber Bots:
|Text message with keyboard
Additionally, you can use the available attachments:
||Adobe Portable Document Format (.pdf)
||MPEG-4 audio file (mp4)
||Portable Network Graphics (PNG)
||Microsoft Word (.doc)
||Adaptive Multi-Rate (amr)
||Microsoft Office-OOXML-Word Document (.docx)
||MP3 audio file (mp3)
||Microsoft PowerPoint (.ppt)
||Ogg Audio (ogg)
||Microsoft Office-OOXML-Presentation (.pptx)
||Microsoft Excel (.xls)
||Microsoft Office-OOXML-Spreadsheet (.xlsx)
Read more about Viber Bots.
With over 52 million global monthly active users (MAU) today, KakaoTalk is the most popular and the most used messenger application in South Korea.
Set up real-time conversations with your customers, offer live agent support, and help your agents provide the best customer service by using our Conversations solution.
To enable KakaoTalk in Conversations, contact your dedicated Account Manager to enable the service for you. Also, refer to our KakaoTalk docs for more information.
Here you can see in a bit more detail how to use Live Chat in Conversations. More importantly, it will give you a better insight into leads and authenticated customers are shown in Live Chat.
Customers visiting your website or using the mobile app can be classified into two types:
- Leads – An unidentified customer. It can be an existing customer or a potential customer who opens the chat widget and starts a conversation.
- Authenticated customer – A customer who has logged in at your website or mobile application and can be identified as your customer within your information system.
Leads are website users who haven’t been identified because they didn’t log in. Although, Live Chat can remember visitors within the chat session and associate it with a visitor ID.
This goes even for cases where a conversation was closed, and the same visitor started another conversation. The customer card will still contain the entire conversation history and their previous requests for this visitor. That way the agent can see the backstory and have an overview of the visitor’s previous questions.
Learn more about leads.
Authenticated customers are the known customers who have logged in to your website.
Learn more about authenticated customers.
Authenticated customers can be grouped in two ways:
- A person that exists in the People module
- Authenticated Customer not found in People
Authenticated Customer Found in People
This is an authenticated customer who has their profile in People. When such a customer starts a conversation on your website, you can rely on People to provide you with additional information about this customer. For example, then you will know their first and last name.
Here’s what the conversation with such a customer looks like:
However, sometimes, you might not have a first or last name entered in People. If this is the case, then Conversations will use the provided key identification.
Authenticated Customer Not Found in People
This is an authenticated customer who has not been entered as a profile in People. This means, that this customer and their email address (which is used as a key identity) do not match anyone in People.
Here’s what the conversation with such a customer looks like:
Supported File Types
The following are all the file types that both agents and customers can share over Live Chat. You will not see a lot of other file types because we want to control which ones can be shared due to security purposes, as we want to make Live Chat as secure as possible.
||jpeg, bmp, gi, svg+xml, png, tiff
||x-msvideo, mpeg, quicktime, mp4
||aac, mp4, amr, AMR, mpeg, ogg, x-wav
||xml, x-directory, javacript, x-wav, vnd.ms-excel, text/plain, vnd.oasis.opendocument.spreadsheet, vnd.oasis.opendocument.graphics, x-gzip, octet-stream, pdf, msword, json, rtg, text/html, vnd.oasis.opendocument.text, vnd.oasis.opendocument.presentation, zip, vnd.openxmlformats-officedocument.wordprocessingml.document, vnd.openxmlformats-officedocument.presentationml.presentation, vnd.openxmlformats-officedocument.spreadsheetml.sheet
Use Instagram in Conversations to reply to your end-user's requests, both on posts and direct messages.
Make sure to activate Instagram Messaging first before you start using it. Then you can benefit from one of the most popular social media platforms by responding to your followers' posts and direct messages.
Instagram conversations are located in the All Work panel. Agents (or a Supervisor/Manager) can simply assign these conversations to themselves and continue with their work as usual inside the My Work panel.
Create interactive content for your customers, and engage them in simple communication.
You can create and reuse templates that contain generic information or standard responses to customers.
Your agents can share a list of possibilities in a single message to the customer (maximum of 10 cards per message).
You can create these in the Conversations API solution but can only preview them in the Conversations full solution.
Check out our Instagram docs for more information on the channel itself.
Apple Messages for Business
Apple Messages for Business is a new channel in the Infobip portfolio that helps businesses connect with customers directly from Maps, Siri & Safari on any Apple device. This channel gives you the opportunity to reach over 1.65 billion iOS devices worldwide.
Read more about Apple Messages for Business in our in-depth section on the Documentation Hub.
Use Apple Messages for Business in Conversations to provide customers with quick support through one-on-one conversations with a live agent. This way you're offering them the option to switch a conversation from a chatbot to a live agent for requests that chatbots cannot handle further.
Other supported solutions:
- You first need to create a new Apple Messages for Business account, and, during this process, select Infobip as the Messaging Service Provider. If you already have an account, all you need to do is select Infobip as the Messaging Service Provider. You can find more info in the Apple docs.
- Connect Apple account to Infobip account. You can connect your Apple account to your Infobip account automatically (without any help from the Infobip side) – as you'll be redirected to the Infobip web interface from Apple's Register. It is critical to note that you must be logged into the appropriate Infobip account during this step.
- Make sure you're logged in to the Infobip web interface and find your way to the Numbers and Channels section on the left-menu navigation.
Here you can configure specific Apple Messages for Business' features: Apple Pay support, iMessage app sharing support, and Authentication request support.
Supported Message Types
The table below outlines supported message types depending on whether the client (mobile-terminated) sent them or the end user (mobile-originated).
||Conversations API and preview in message history
|Apple Pay Request
|iMessage App Sharing
||Preview of response
||Conversations API and preview in message history
||Preview of response
||Conversations API and preview in message history
|3D Files (usdz)
||✔ (as file)
Specific Message Types
Check out which specific message types you can send to end users in Apple Messages for Business : Apple Pay support, iMessage app sharing support, and Authentication request support.
Apple Pay Request
To send Apple Pay requests inside the agent panel, you need to set this up in the Numbers and Channels section. Navigate to Numbers and Channels > Apple Messages for Business. Locate your connected accounts and click the three-dot menu on the far right. Select the Create Apple Pay Configuration action.
After configuring this:
- You can utilize this feature inside the agent panel and send the Apple Pay request to your customer by clicking on the Apple Messages for Business icon
- Select Apple Pay within the Apple Messages for Business card in the agent panel
- Fill in the required data to send the Apple Pay request to the customer. After the payment has been successfully processed, you will see the confirmation in the agent panel.
To successfully authenticate a customer, use the Apple Messages for Business action inside the agent panel.
To send the Authentication request to the customer from the agent panel, you need to set this up in the Numbers and Channels section. Navigate to Numbers and Channels > Apple Messages for Business. Locate your connected accounts and click the three-dot menu on the far right. Select the Authentication action.
After configuring this:
- You can utilize this feature inside the agent panel and send the Authentication request to your customer by clicking on the Apple Messages for Business icon
- Select Authentication within the Apple Messages for Business card in the agent panel
- Fill in the required data to send the Authentication request to the customer. After the customer has been successfully authenticated, you will see the confirmation in the agent panel.
iMessage App Request
To send an iMessage, you need to set this up in the channel itself. Click on the Apple Messages for Business, then the three-dot menu, and click Edit Custom App Configuration. Fill in the required info and hit Save.
- To chat with a customer and send an iMessage, click the Apple Messages for Business icon in the agent panel
- Choose the iMessage App from the drop-down
- Fill in the data needed to send an iMessage app to the customer
Rich Link Messages
Rich links in Conversations are now supported. If you're sending a message that only contains a link, it will automatically be converted into a rich link for the end user. This way your end users can have an overview of what your agents are sharing to them and thus strengthen your overall customer experience.
This is the view from the agent panel when sending rich link messages:
This is an example of what the customer sees on their iOS device:
For more info, read the specific Apple Messages for Business channel page.
Use LINE in Conversations to offer your customers quick support and resolve issues in one-on-one conversations over their favorite communication channel. Offer different lists and showcase your offerings, and at the same time, decrease your call center operational costs.
You can now use two new content types in LINE in Conversations: Carousel Message, and Button Message. This should definitely help simply content sharing with your customers, allowing for a more user-friendly customer experience.
For more information about supported message types, refer to the main LINE documentation, covering end-to-end scenarios.
Use Email in Conversations and let your contact center agents reply to customer emails directly from the agent panel.
To start using Email as a 2-way communication channel in Conversations, you need to set it up first.
In the web interface, navigate to the Numbers and Channels section > locate and click on the Email card.
In this window, you have two options: Marketing and transactional, and Conversations. Choose Conversations.
Here you can configure your email setup to enable your contact center agents to email customers directly from the agent panel.
You can choose between:
- Custom sender
- Infobip sender
To use the Custom sender option, you need to own the domain that will be used to register senders to.
If you don’t have your own domain, you will need to purchase and register it from a domain provider before adding senders or go back and choose to use Infobip senders instead.
Alternatively, you can use Infobip domain to register a new subdomain, and then you can add senders (unlimited) to that domain.
Note that the main domain is always ibconversations.com and your register a new subdomain which could be something like acmesupport.ibconversations.com.
- Custom sender
As mentioned earlier, to add a custom sender, you need to own the domain that will be used to register senders to.
If you already own such a domain, click on the ADD SENDER button on the far right.
What follows is an intuitive sender creation process and you will see a checkmark next to each completed item as you go through the list.
- Enter your sender name that will be displayed in replies.
- Define Conversations email address - This email address will be used for receiving emails on Conversations from your domain. This email won't be used in communications. Your default domain is @fwd.ibconversations.com
- Set up forwarding - Go to your email provider settings panel and enter your Conversations email address you created in the previous step as a forwarding address. This means that every email sent to your domain will be forwarded to the Conversations agent panel. e.g., if you are using the Gmail suite, go to settings, select Add forwarding address, and paste the address into the input field.
Verify forwarding of incoming verification - Enter the email address you used to set up forwarding from. Click on the Verify button to receive a test email. The test email is sent to the Agent Panel in Conversations.
Outbound verification - to be able to send outbound emails, you need to confirm the domain ownership by creating a TXT record and then entering it into your domain’s DNS settings. Enter your domain and click the Create Record button.
Once the DNS records have been generated, click the Export Records button to export these. Then, proceed by adding them to your domain settings. When done, come back to the Infobip web interface and click the Verify button to verify the DNS records. Note that it can take up to 48 hours for these to be verified.
Read more on how to manage DNS records.
Also, the Custom Sender list will show the status of your senders:
- Verified (green) - Inbound and outbound verification done.
- Unverified (red) - Inbound and outbound verification still pending.
If your sender status is still pending, click on the sender name, and in the verification window, you can try resending the test email and check the All Work panel for that email to verify your sender.
These statuses are applicable to custom senders only.
Two-way email communication is now available in Conversations. Both customers and agents can initiate an email conversation.
Emails within any conversation contain the following information:
- Sender's name
- Sender's email address
- Email subject
- Email body
- Email attachments
- Day of the week, date, and time the email is received/sent
Additionally, agents can use these actions when handling emails:
- Reply to email – use it to send a reply
- Forward email – use this to forward the existing email to another recipient
- Show original email – hidden behind the ellipsis, providing an overview of the email in HTML, TEXT, and SOURCE
Moreover, an option to expand and contract an email card in conversations history is available and visible with an arrow icon.
Agents can send emails in two ways:
When an agent wants to initiate a new conversation and send an email to the customer, they should use the Start a Conversation button.
When sending an email from an existing conversation, they need to click either reply or forward or use the New Email button at the bottom of the page.
Common editing options are available while writing an email, along with the ability to send attachments up to 20MB.
To make reading and writing emails easier, the right-hand pane containing context cards can be contracted to a narrower size, thus providing extra space for managing emails. Agents can also take over emails by clicking the take-over icon.
When sending an email, agents can choose the sender's email address and the recipient. Also, common options like CC and BCC are available.
If an agent gets distracted from writing an email because they are working on different tasks, a draft will be stored in the Email drafts tab. They can access it from the top of the conversations history section.
When a BCC recipient replies to an email in a conversation, a new conversation will be started. The reason behind this is that, until now, agents could send an email to multiple clients using BCC (clients are not aware of one another), and if they replied, handling all those replies in one conversation could impose security and privacy risk.
Similar is valid for the Forward option. Each time an agent forwards an email, a new conversation will be created to separate the existing communication from the new one.
Emails are always ordered from newest to oldest: the latest email is shown at the top of the agent panel but you can view the older threads by clicking the arrow next to the three-dot menu on the right.
Also, you can make use of the draft option while forwarding an email. This option was previously available for replies only. During forwarding, simply click on the Edit draft button to edit your email.
When an inbound email is received, the system checks if that email belongs to an existing thread. Different behaviors of different email servers and email clients used by customers impact the parameters that are sent along with each inbound email.
To bypass those limitations, you can incorporate email threading by using these four parameters:
- Reference ID stored in the header of the email
- Reference ID stored in the email body
- Recipient list
- Email subject with prefixes such as “Re:”, “Fw:” and their localized version stripped
The system checks these parameters and if at least two are a match, the inbound email is considered as a continuation of an already existing thread.
You can enrich outbound emails with various values such as placeholders and simple templating language. You can create a template for every outbound email. Before the email is sent to the end user, the template will be applied.
To access this feature, navigate to Numbers and Channels > Conversations > Outbound Emails.
Outbound Emails consist of two main parts:
- Templates. The place where you can define multiple templates. You need to enter the name and the description (optional field) when creating a template. Templates consist of a Subject and Content. Those fields are by default prepopulated with the subject and the body already defined by an agent sending the email. Agents can play around those fields and add placeholders available in the standard placeholder picker used in multiple places in Conversations. These templates are usually used to define a signature to be automatically applied when sending emails. Once the agent saves the template, it will appear on the list of templates and they can edit it, delete or search a specific template.
- Conditions. This is where you can define which template will be applied to which outbound email. When creating a condition, you can enter the title and description (optional), select the template that you wish to apply the conditions to, and then set these conditions using the AND action, as well as the OR action. You can also enable/disable the conditions by moving the toggle at the top right corner.
After you have created your conditions, they will appear on the conditions list where you can edit or delete them.
You can use Infobip Social Media channels to resolve customer inquiries over some of the most popular social media sites, such as Facebook Posts, Instagram Posts, and Twitter. Social Media is primarily used with Conversations but certain features such as Facebook Posts can be coupled with our chatbot solution, Answers, as well.