Skip to main content
Pushover is how Vortex IQ buzzes a single operator’s phone with a precise, structured alert in under a second, without the noise of a team chat channel.

​
What is Pushover?

Pushover is a small, focused push-notification delivery service. It runs apps on iOS, Android, and desktop (macOS, Windows, Linux browser) that receive notifications from a simple HTTP API. The product is one of the most beloved tools among individual ops engineers, indie developers, and small DTC operators: the API is one endpoint, the apps are a one-time five-dollar purchase per platform, and the latency is low. There is no presence, no chat, no threading. It is just a push to a device, with a title, a message, a priority, and an optional sound. For Vortex IQ, Pushover is the lightweight channel for individual recipients who want a personal pulse on their store without forcing the whole team into Slack.

​
Why Vortex IQ uses Pushover as an alert channel

Pushover is the right channel when:
  • A solo merchant or a small founding team is running the store and Slack is overkill.
  • A specialist (the head of paid media, the warehouse lead, the customer-experience manager) wants their own narrow stream of alerts about their domain.
  • Something needs to reach a specific person fast on their phone, without waking the whole on-call rota.
Vortex IQ uses Pushover for medium and high-severity individual alerts: ad spend anomalies, refund-rate spikes on a specific product category, inventory thresholds on a hero SKU, customer-feedback spikes on a launch product. It is not a replacement for voice (Aircall, Dialpad, RingCentral) on severity-one outages, and it is not a substitute for team channels (Slack, Teams) on collaborative incidents.

​
What gets delivered

A Pushover alert from Vortex IQ contains:
  • Title: severity icon plus short alert name (for example, “Refund-rate spike, Sneakers category”).
  • Body: one or two short paragraphs with the trigger metric, current value, threshold, and time window.
  • Priority: standard, high, or emergency, mapping to Pushover’s 0, 1, and 2 priority levels.
  • Sound: a configurable sound per priority, so high-priority alerts can be distinguished by ear.
  • Deeplink: a short URL into the relevant Vortex IQ Nerve Centre panel.
Emergency-priority alerts use Pushover’s repeat-and-confirm behaviour: the device keeps notifying until the recipient acknowledges, which is useful for warehouse inventory triggers during fulfilment hours.

​
How it integrates

  • Authentication: a per-user Pushover application token plus the recipient’s user key. Both are stored encrypted in Vortex IQ.
  • Outbound trigger: Vortex IQ posts to the Pushover messages endpoint with the rendered title, message, priority, sound, and URL.
  • Per-recipient subscription rules: each merchant user can subscribe to specific alert categories, severities, and stores. Pushover delivery only fires for matched subscriptions, which keeps personal channels focused.
  • Quiet hours: Vortex IQ honours each recipient’s quiet-hour window, suppressing non-emergency-priority alerts overnight.
  • Rate limiting: standard alerts are deduplicated on incident ID to prevent flap-driven floods.

​
Operational diagnostics

The Nerve Centre exposes per-recipient Pushover diagnostics:
  • Last successful test push per user key.
  • 7-day delivery rate (Pushover API success responses).
  • Suppressed-during-quiet-hours count for the last 7 days.
  • Failed-delivery log, with Pushover error codes (invalid user key, application token revoked, message too long).
  • Live preview of how the next alert will render on iOS and Android.
If the Pushover service is unavailable or returns sustained errors, the alert is queued briefly and then routed to the recipient’s secondary channel (typically email or SMS via Twilio or Vonage) so the signal is not lost.

​
Connect Pushover to Vortex IQ

Add Pushover as a notification channel from the Vortex IQ settings page. Each user provides their own Pushover user key, the merchant supplies an application token, and Ask Viq will start routing matched alerts to those devices from the next deployment forward.