Skip to content
AskVault Docs
Try Free →

Channel health monitoring

Written by , Founder, AskVault · Reviewed by Aashiq
Last updated: · 3 min read

What's tracked

For each of the 13 connected channels:

  • Status. Operational, degraded, down.
  • Uptime % over the last 24 hours, 7 days, 30 days.
  • Error rate of message delivery.
  • Throughput (messages per minute).
  • Provider status (Twilio, Slack API, etc.).
  • Last successful message timestamp.

Where to find it

Three views:

  1. Deploy Hub overview. Health indicators on each channel card.
  2. Per-channel detail. Click a channel for drilldown.
  3. Analytics dashboard. Health trends over time.

Drilldown view

Click any channel to see:

  • Error breakdown. Categorized by error type (auth, rate limit, provider outage, etc.).
  • Affected conversations. List of conversations impacted.
  • Recent errors. Last 100 with full error context.
  • Provider correlation. Cross-reference with provider status pages.

About 80% of channel errors trace to provider issues (Twilio, Slack); 20% to AskVault-side issues.

Common error categories

Per channel:

WhatsApp / SMS / Voice.

  • Twilio account issue.
  • Rate limit hit.
  • Number not registered (A2P 10DLC).
  • Customer opted out.

Slack / Discord.

  • OAuth token expired.
  • Bot not in channel.
  • Permission missing.
  • Rate limit (Slack 429).

Email.

  • IMAP/SMTP credentials invalid.
  • Token refresh needed.
  • Inbox folder missing.
  • Provider rate limit.

Widget / Hosted page.

  • CORS rejection (domain not allowlisted).
  • CDN cache stale.
  • Rate limit per visitor.

Alerting

Configure under Deploy Hub > Notifications:

  • Email alerts on channel degradation.
  • Slack alerts to a chosen channel.
  • Webhook alerts to your own monitoring.
  • Per-channel sensitivity. Alert on 5%, 10%, or 25% error rate.

About 5 to 10 minutes from degradation onset to first alert.

Self-healing

AskVault auto-recovers from many transient issues:

  • OAuth tokens auto-refresh ahead of expiry.
  • Failed deliveries retry with exponential backoff (5 to 24 hours).
  • Rate-limit-throttled traffic spreads across the cap.

For persistent issues, manual action required (re-authorize OAuth, contact provider, etc.).

Cross-channel patterns

When multiple channels degrade simultaneously, often:

  • AskVault platform issue. Check status page.
  • Provider-shared issue. Twilio outage affects WhatsApp, SMS, and Voice together.
  • DNS issue on your end. Custom domain plus webhook endpoints affected.

The dashboard correlates and suggests likely cause.

API access

For programmatic health checks:

Terminal window
curl https://api.askvault.co/v1/channels/whatsapp/health \
  -H "Authorization: Bearer ak_xxx"

Returns current status, error rate, last-success timestamp. Useful for embedding in your own dashboards.

Limits

  • Health metrics retention. 90 days standard.
  • Alert frequency. Up to 1 alert per channel per 15 minutes (anti-spam).
  • Drilldown depth. Last 1,000 errors per channel per day.

Common pitfalls

Channel shows healthy but feels broken. Check provider's own status page. AskVault sees its side; the provider may be silently dropping.

Persistent OAuth errors. Token refresh disabled or revoked. Re-authorize.

Sporadic 429s. Rate limit at provider. Lower send rate or contact provider for cap increase.

FAQ

Does this monitor uptime my customers see?

Closely. The dashboard sees AskVault-to-provider; customer-to-provider may differ for last-mile issues.

Can I export health data?

Yes via API or Conversation Export.

Do I get notified during after-hours?

Yes if email/Slack/webhook alerts configured. Respects business-hours toggle if set.

Was this page helpful?