Loading…
Velaxe
PulseGate — Messaging Operations, Conversations, Campaigns, Routing & Compliance | Velaxe

PulseGate

Configure consent, preferences, suppression and quiet hours

Govern recipient eligibility with communication preferences, consent records, suppression, opt-out keywords, country rules, and quiet-hour policy.

12 min Beginner Compliance Administrator, Communications Administrator Updated Aug 23, 2026
View App All Guides

Overview

Govern recipient eligibility with communication preferences, consent records, suppression, opt-out keywords, country rules, and quiet-hour policy.

Prerequisites

  • Recipient policy requirements for the workspace are defined

Permissions required

compliance.write compliance.read

Steps (4)

Estimated: 12 min
  1. 1

    Define communication policy

    Administrator 3 min Back to top

    Configure communication preferences, consent expectations, and category behavior.

    Tips

    —

    Validation

    —

    Success criteria

    —

  2. 2

    Configure suppression and opt-out controls

    Administrator 3 min Back to top

    Maintain suppression entries and opt-out keywords used by messaging policy.

    Tips

    —

    Validation

    —

    Success criteria

    —

  3. 3

    Configure country and quiet-hour policy

    Administrator 3 min Back to top

    Set country messaging rules and quiet-hour windows for the relevant channels/categories.

    Tips

    —

    Validation

    —

    Success criteria

    —

  4. 4

    Verify policy evaluation

    Administrator 3 min Back to top

    Use representative recipients and categories to confirm delivery eligibility before dispatch.

    Tips

    —

    Validation

    —

    Success criteria

    —

About this guide

PulseGate is the communications control plane for Velaxe workspaces. Applications send business communication through trusted contracts while PulseGate resolves recipients and templates, applies authorization and policy, routes delivery, records message state, and publishes clean events.

Operations teams get a dedicated Messenger workspace for conversations, contacts, campaigns, approvals, failed messages, and media, plus administration for provider connections, sender identities, routing, templates, consent, suppression, quiet hours, cost rules, audit, and reports.

Durable workers handle dispatch, schedules, reminders, campaigns, provider webhooks, retries, reconciliation, metrics, retention, exports, media processing, and operational recovery. Handler, RCP, Bridge v2, EventBus, and ContextResolver contracts keep workspace integrations governed and source-aware.