# Vonage connection for Viber

Use Vonage to carry Viber messages and delivery updates for a configured INSIDE account.

*Release 3.3 · admin, developer*

**Settings › General Settings › Integrations**

## What it is

**Vonage** is an alternative provider for a Viber connection in INSIDE. It carries customer messages and reports delivery, read and failure events. This release's Vonage messaging connection handles Viber traffic.

## Who uses it and why

Administrators arrange the Vonage account and sender with Powerfront. Developers coordinate the provider's incoming-message and delivery-notification configuration. Operators use the resulting **Viber** conversations.

## Where to find it

Powerfront selects **Vonage** as **Provider** for a **Viber** account under **Settings › General Settings › Integrations**. There is no separate client-managed Vonage settings screen.

## How it works

1. Vonage sends a customer message addressed to the business sender.
2. INSIDE matches that destination to the configured Viber **Sender ID** and imports supported content.
3. Replies use the account's Vonage credentials.
4. Delivery reports identify the business sender and update the corresponding conversation messages.

Supported incoming content includes text, images, video and files. Submitted reports are intermediate updates. Delivery, read, rejection and failure reports determine the later status shown for messages.

The connection can receive messages and status reports together or through separate provider notification connections. Powerfront supplies the correct connection details.

## Configure it

Ask Powerfront to select **Vonage**, set **Integration Type** to **ChatBot** and enter the **Sender ID**, **Vonage API Key** and **Vonage API Secret**. **Vonage API URL** is optional; an empty value uses the standard Vonage service.

Provide **Vonage Signature Secret** to Powerfront when signed notifications are configured. With this field set, INSIDE checks notification signatures and expiry. It also checks age and message integrity when the provider includes those details. With the field unset, signature verification is disabled.

Coordinate any sender or credential changes with Powerfront so incoming messages and delivery reports continue to select the same account.

### Fields

| Field | Where | Required | What it is for |
|---|---|---|---|
| Sender ID | Settings › General Settings › Integrations | Yes | Identifies the Viber sender account used to match incoming messages and delivery reports. |
| Vonage API URL | Settings › General Settings › Integrations | No | Overrides the standard Vonage service address when a different connection address is needed. |
| Vonage API Key | Settings › General Settings › Integrations | Yes | Identifies the Vonage account used to send messages. |
| Vonage API Secret | Settings › General Settings › Integrations | Yes | Authenticates outgoing Vonage requests. |
| Vonage Signature Secret | Settings › General Settings › Integrations | No | Enables verification of signed incoming message and status notifications. Leaving it unset disables signature verification. |

## Limits and good to know

- **Business Messages** cannot be saved as the integration type for Vonage. Ask Powerfront to select **ChatBot**.
- This connection does not provide Vonage SMS, MMS, WhatsApp or Messenger messaging in this release.
- If signature verification is enabled, missing, invalid or expired authentication can prevent a notification from being processed.
- An accepted notification does not itself mean that the customer received or read the message. Review the later provider status.

## Depends on and works with

### This feature uses

- **Requires** [Webhooks and message status](CHN-003.md): Incoming notifications carry customer messages and delivery status.
- **Requires** [Viber messaging channel setup](CHN-016.md): Vonage messaging is selected within a Viber account.
- **Configured in** [Messaging channel connections](CHN-001.md): Powerfront manages connection credentials and provider selection.
- **Works better with** [Message delivery and read receipts](CHAT-003.md): Vonage delivery, read and failure reports update message status.

### Used by

- **Configures** [Viber messaging channel setup](CHN-016.md): Choosing Vonage selects its Viber transport, credentials and notification verification.

## FAQ and troubleshooting

### Can I use this connection for Vonage SMS?

No. The messaging connection described here handles Viber. SMS accounts use the separate **Text/SMS Phone Numbers** setup.

### Why are incoming messages missing after a sender change?

Ask Powerfront to check that the destination business sender matches **Sender ID** and that the selected account is enabled.

### Why did signed notifications stop working?

Ask Powerfront to check **Vonage Signature Secret** against the provider configuration and review the notification authentication and expiry.

### Why does the account reject Business Messages?

The Vonage account editor only permits **ChatBot** for Viber in this release.