Voicemail Events β HyperConnect Integration Notification
When a guest leaves a voicemail through the voice channel, SmartBot notifies the HyperConnect integration so the missed-call event appears in the HyperConnect timeline. This article explains what triggers the notification, what information is included, and how failures are handled so you can set expectations for your team.
Note: For conceptual background on SmartBot's voice channel, see IVR and voice channel.
Before you begin
- The voice channel must be enabled for the center where you want voicemail events to appear.
- The center must have a valid center ID configured in your SmartBot voice channel settings. Without a center ID, the system does not dispatch the voicemail event notification to HyperConnect.
- The guest's phone number must be captured during the voice recording for the notification to include guest contact details.
- For HyperConnect voice and messaging features, see HyperConnect overview.
Steps
Understand when a voicemail event is triggered
A voicemail event notification is dispatched to the HyperConnect integration automatically after a voice recording completes, provided the center ID for the call is present. You do not need to take any action to trigger this β it occurs as part of the normal missed-call handling flow.
The notification is sent using an asynchronous (fire-and-forget) process. This means:
- The voicemail record is saved regardless of whether the notification succeeds.
- Transcription of the voicemail proceeds regardless of whether the notification succeeds.
- If the notification cannot be delivered, the failure is logged for your administrator to review, but no manual retry is required from your end.
Review what information the notification includes
When a voicemail event is dispatched, the following guest information is included in the notification sent to HyperConnect:
| Field | Description |
|---|---|
| Guest name | The name associated with the guest's profile, as resolved from the incoming call. |
| Phone number | The guest's phone number captured during the voice recording. |
| Phone code | The country dialing code associated with the guest's phone number. |
| Country | The guest's country, resolved from the phone's country code to the Zenoti internal country record. |
Note: If the guest's country code cannot be resolved to a recognized country in Zenoti, the country field is omitted from the notification. The notification is still sent with all other available fields β the missing country does not prevent the event from being dispatched.
Verify that voicemail events are appearing in HyperConnect
After a guest leaves a voicemail on an enabled voice channel, confirm the event appears correctly:
- Open the HyperConnect timeline for the relevant center.
- Locate the missed-call entry for the guest.
- Confirm that the guest's name and phone number are displayed on the timeline entry.
If the missed-call entry does not appear, verify the following:
- The center ID is correctly configured in the voice channel settings. See Configure the voice channel.
- The voice channel is enabled for the center. See Configure SmartBot general settings.
Important: A voicemail event that fails to reach HyperConnect does not affect voicemail storage or transcription. The voicemail will still be accessible in the call logs. See Call logs and voicemail for how to access recorded voicemails.
Tips
- If your team relies on HyperConnect to track missed calls, confirm that the center ID is populated in the voice channel configuration before enabling voicemail for a center. A missing center ID is the most common reason a voicemail event does not appear in the HyperConnect timeline.
- Guest country information on the timeline entry depends on the phone number's country code being recognized by Zenoti. If you serve guests in regions with less common dialing codes, verify that those countries are configured in your organization's country settings.
- Because the notification is delivered asynchronously, there may be a brief delay between a voicemail being recorded and the event appearing in the HyperConnect timeline. This is expected behavior and does not indicate a failure.
- Voicemail transcription and storage are not affected by the HyperConnect notification status. Even if a notification fails, the voicemail recording and its transcript remain available in the call logs.
Troubleshooting
| Problem | Resolution |
|---|---|
| Missed-call entry does not appear in the HyperConnect timeline after a voicemail is recorded. | Confirm that the center ID is configured correctly in the voice channel settings. A missing center ID prevents the voicemail event from being dispatched. See Configure the voice channel. |
| Guest country is missing from the HyperConnect timeline entry. | The guest's phone country code could not be matched to a country in Zenoti. This is expected and does not prevent the event from appearing β only the country field is omitted. No action is required. |
| Voicemail is saved and transcribed, but no notification reached HyperConnect. | The asynchronous notification may have failed. Your administrator can review the failure log to confirm. The voicemail record itself is unaffected and remains accessible in the call logs. |