Velaxe
PulseGate — Unified Messaging Gateway for SMS, WhatsApp, Messenger & Telegram | Velaxe

PulseGate

Configure quiet hours & opt-out enforcement

Set sending windows, enforce STOP/HELP keywords, and manage consent registry.

12 min Beginner Compliance, Messaging Ops Updated Oct 3, 2025
View App All Guides

Overview

Set sending windows, enforce STOP/HELP keywords, and manage consent registry.

Prerequisites

None.

Permissions required

compliance:write

Steps (3)

Estimated: 12 min
  1. 1

    Set global quiet hours

    Compliance 4 min Back to top

    Compliance → Policies → Quiet Hours. Choose local-time windows per region; enable override for urgent incident class if required.

    Tips

    —

    Validation

    —

    Success criteria

    —

  2. 2

    Enable STOP/HELP handling

    Messaging Ops 4 min Back to top

    Turn on automatic keyword detection. PulseGate updates consent registry and suppresses further sends until opt-in.

    Tips

    —

    Validation

    —

    Success criteria

    —

  3. 3

    Review consent records

    Compliance 4 min Back to top

    Open Consent Registry; export CSV for audit with timestamps, IP, and source path.

    Tips

    —

    Validation

    —

    Success criteria

    • No sends occur outside allowed windows or without active consent.

About this guide

PulseGate centralizes business messaging for SMS and popular OTT channels including WhatsApp, Facebook Messenger, Instagram DM, and Telegram. Connect providers like Twilio or Meta Cloud API once, then send and receive through a single, normalized interface. PulseGate tracks delivery receipts, applies rate-limit aware retries, and surfaces errors with one-click safe requeue.

Admins manage connectors, numbers/senders, WhatsApp templates, and compliance (opt-in/opt-out, quiet hours). Apps such as LiveConnect and Agent Desk consume clean events and message states without worrying about vendor quirks.

Built for reliability and scale with queues, backoff, DLQs, and health dashboards.