Use eligible business access
Before development is activated, the business needs a supported Viber account and any required commercial agreement.
Integrations Viber
ViberPlanned
ViberPlannedViber support, planned around business access.
Review the proposed Viber connector for Message Inbox, including account eligibility, customer identity and reliable reply handling.
Planned connector. Native setup is not available yet. The workflows below describe the intended scope; release depends on provider access and testing.
Messaging
What we’re planning to connect.
- 01Viber
- 02Planned connection
- 03Message support
Route support messages
The intended flow would put permitted inbound messages into the same queue as other customer requests.
Handle reply failures clearly
A failed or blocked delivery should remain visible to the agent rather than appearing successfully sent.
The right context
Be precise about what connects.
Define the data, permissions and destination before putting the workflow in front of customers.
Eligible business account
Permitted inbound messages
Delivery outcomes
Prepare for the connection
Define your first workflow.
- 01
Choose the first workflow
Confirm provider eligibility and commercial access before planning a customer rollout.
- 02
Agree on data and permissions
Decide which fields may be read, which people may use them and whether any separate write action is needed. Native setup is not available yet.
- 03
Define the acceptance test
Test a blocked recipient, a duplicate event and a failed reply before calling the connection ready.
Before you connect
Viber integration questions
Can I connect Viber to Message today?
The native connector is planned. The workflows on this page describe the proposed design; there is no native installation to activate yet.
What should we test before using it with customers?
Test a blocked recipient, a duplicate event and a failed reply before calling the connection ready.