Skip to main content
RingCentral is how Vortex IQ reaches enterprise on-call rotations: voice calls, SMS, and team messages routed through a unified communications platform that the merchant’s IT department already trusts.

​
What is RingCentral?

RingCentral is an enterprise unified communications provider. The flagship product, RingEX, bundles cloud phone, video meetings, team messaging, SMS, fax, and a contact-centre suite into one platform. Buyers skew larger than Aircall or Dialpad: Fortune 500, large mid-market, and regulated industries (finance, healthcare, public sector). The platform is known for global PSTN coverage, compliance certifications (HIPAA, PCI, SOC 2), and deep telephony feature parity with on-prem PBX systems. For Vortex IQ, RingCentral is the alert channel for merchants whose comms stack is already standardised on RingCentral and whose on-call practices need enterprise reliability.

​
Why Vortex IQ uses RingCentral as an alert channel

RingCentral is not a data source. It is an outbound delivery surface, with two distinct roles inside Vortex IQ:
  1. Voice escalation, equivalent to the role Aircall and Dialpad play, but routed through the merchant’s existing RingCentral phone numbers and on-call queues.
  2. RingEX SMS, used as a secondary fast-touch channel for high-severity incidents on numbers that the merchant has provisioned through RingCentral rather than Twilio or Vonage.
Typical incidents that escalate via RingCentral:
  • Severity-one outages on Shopify, BigCommerce, or Adobe Commerce stores.
  • Payment-gateway disconnections during peak hours.
  • Catalogue or pricing drift during an active campaign window.
  • SLA-breach forecasting on monitored services that feed into critical commerce paths.
When a merchant has both PagerDuty and RingCentral configured, PagerDuty routes the on-call rota and RingCentral places the actual phone call or SMS.

​
What gets delivered

For voice calls, the spoken script mirrors the format used on Aircall and Dialpad:
  • Severity, one-line summary, store name, and platform.
  • Triggering metric with current value and threshold.
  • Live revenue-at-risk in local currency.
  • Spoken reference identifier and short URL into the incident page.
  • Keypad acknowledgement: 1 to acknowledge, 2 to snooze, 3 to escalate.
For RingEX SMS, the message is a short structured alert (under 160 characters where possible), with the severity, alert name, store, current value, and a short URL. SMS is used for medium and high severity, never as the only channel for severity-one. Long-form context lives in the linked Vortex IQ incident page, not in the SMS body.

​
How it integrates

  • Authentication: OAuth 2.0 against RingCentral’s developer platform, with a JWT or password-flow service account for outbound origination.
  • Calls API: Vortex IQ uses RingCentral’s RingOut and Call Control APIs for outbound voice with a TTS-rendered script.
  • SMS API: messages are sent via RingCentral’s SMS endpoints from a merchant-provisioned number.
  • Number selection: voice and SMS originate from numbers the merchant has provisioned in RingCentral, so caller-ID is consistent.
  • Rate limiting and dedupe: one voice call per recipient per minute, one SMS per recipient per 30 seconds, deduplicated on incident ID.
  • Compliance: RingCentral’s enterprise compliance posture (HIPAA, SOC 2) is preserved end-to-end; Vortex IQ does not store call audio, only metadata.

​
Operational diagnostics

The Nerve Centre exposes RingCentral channel health:
  • Last successful test call and test SMS per number.
  • Call acknowledgement rate over the last 7 days.
  • SMS delivery rate, with carrier-level status where RingCentral provides it.
  • Failed-delivery log with RingCentral API error codes.
  • Token rotation reminder, with auto-warning 14 days before OAuth refresh tokens are due to rotate under the merchant’s policy.
If RingCentral returns sustained errors, Vortex IQ falls through to the next link in the escalation chain, typically PagerDuty, then a backup voice or SMS channel.

​
Connect RingCentral to Vortex IQ

Add RingCentral as a notification channel from the Vortex IQ settings page. Provide the RingCentral API credentials, choose the numbers, users, and call queues that should receive incident escalation, and Ask Viq will route severity-one incidents through RingCentral voice and RingEX SMS from the next deployment forward.