VeloConnect — Guide

Notification preferences

VeloConnect can tell you when something needs your attention two ways: a bell in the top bar (in-app) and an email to your account address. You decide which event types fire which channel.

Notification preferences
Fig. 1 — Per-event preferences. The bell + envelope columns let you mix channels.

The two channels

  • In-app — the bell icon next to your avatar. Clicking it opens a dropdown with the recent unread notifications, each linked to the conversation, campaign, or settings page it refers to. The bell shows a red dot when there’s unread.
  • Email — sent to the address on your profile. Useful for the events you want to know about when you’re not in the app.

Open Settings → Notifications to see one row per event type, with a bell column and an envelope column. Tick the boxes you want.

Event types

For everyone:

  • New conversation assigned to me — fires when an admin or a teammate reassigns a thread to you, or when round-robin routing lands a new conversation on you.
  • New message in a conversation I’m assigned to — fires on every inbound message in your queue. High-volume; most agents leave this on in-app and off for email.
  • Missed call on a number assigned to me — fires when a call to one of your assigned DIDs rings out without an answer.
  • Voicemail left on my extension — fires when a caller leaves a voicemail. Email version includes the audio attachment and the auto-transcript if it’s available.
  • Campaign finished — fires when a campaign you created moves to Completed state. Stats are ready to look at.

For admins only:

  • Wallet balance crossed warning / critical threshold — see Topping up your wallet for what those thresholds mean.
  • Sender ID approval status changed — Meta or a carrier approved or rejected a sender ID submission.
  • DID assignment requests pending KYC — a user-facing number purchase needs documents reviewed.

Do not disturb hours

If you’d rather not get emails at 2 AM, switch on Do not disturb and pick a window in your timezone — for example 19:00 to 08:00. During that window VeloConnect skips email sends entirely; in-app notifications still arrive and queue under the bell, so nothing is lost when you sign in again.

DND respects timezone correctly across daylight-saving changes. No action needed twice a year.

Mobile push

Mobile push notifications aren’t in V1. We’re shipping them in a future release; until then, email plus the in-app bell cover the same ground.

Next