capabilities.work

Triage Unread Voicemail

A 4-step recipe with RingCentral. We can help you get access.

Recipe · 4 steps

Triage Unread Voicemail

Pull unread voicemail, capture its transcript and audio, and mark it read.

  1. List unread inbound voicemail for the extension. Filtering on messageType, direction, and readStatus at the API keeps the client from paging through the entire message store.
  2. Read the individual voicemail record to pick up the caller information, the RingCentral voicemail transcription (when available), and the id of the audio attachment.
  3. Download the voicemail audio attachment so it can be archived or handed to the RingCentral AI speech-to-text operations for transcription.
  4. Flip the message to "Read" so the next poll does not return it again. This is what keeps a scheduled voicemail integration from reprocessing the same message on every run.
What you'll need to have ready
  • accountId: Internal identifier of the RingCentral account. Use "~" for the account associated with the current authorization session.
  • extensionId: Internal identifier of the extension whose voicemail is being triaged. Use "~" for the extension associated with the current authorization session.
  • dateFrom: Only consider voicemail received on or after this time (ISO 8601). Use the previous poll's watermark here.
  • perPage: Number of voicemail records to pull per page.
For your developer

Arazzo workflow ringcentral:triage-unread-voicemail, 4 operations: listMessages → readMessage → readMessageContent → updateMessage. Specs on APIs.io.