Velaxe
Chat Core — Orchestration Engine for Sessions, Routing, Handoff & Governed AI | Velaxe

Chat Core

PulseGate (Messaging Gateway) — Integration

Transport abstraction for SMS/OTT. Chat Core uses PulseGate to send/receive messages, normalize receipts, and guarantee delivery semantics across Twilio, Meta WhatsApp, Messenger/IG, Telegram, and more.

Overview

Transport abstraction for SMS/OTT. Chat Core uses PulseGate to send/receive messages, normalize receipts, and guarantee delivery semantics across Twilio, Meta WhatsApp, Messenger/IG, Telegram, and more.

Capabilities

  • Unified send API for sms/whatsapp/messenger/telegram

  • Inbound webhook normalization to MessageEnvelope

  • Delivery receipts → chat.message.* state updates

  • Rate-limit aware retries, DLQ + replay

  • Attachment handling via signed links (no PII blobs)

Setup Steps (5)

  1. 1

    Step 1

    In Settings → Connections, connect your messaging providers inside PulseGate (e.g., Twilio, WhatsApp Cloud).

  2. 2

    Step 2

    Enable the workspace link between Chat Core and PulseGate in Settings → Integrations → PulseGate.

  3. 3

    Step 3

    Map brands/senders to queues (e.g., WhatsApp number → Sales queue).

  4. 4

    Step 4

    Optionally configure canary routing and quiet hours.

  5. 5

    Step 5

    Send a test message from Chat Core; confirm receipts flow back to the session.

Limitations

  • Channel features vary by provider/geo (e.g., templates on WhatsApp).

  • Throughput subject to upstream vendor rate limits; retries are queued.

FAQs

Do I need separate webhooks?

No. Vendors post to PulseGate; PulseGate forwards normalized events to Chat Core.

How are media files handled?

Files are stored via SecureStore and referenced by signed URL in the session.

Can I fail over providers?

Yes, enable smart routing in PulseGate; Chat Core is provider-agnostic.

Pricing

Free

Free

Great for trying the integration.

Team

USD 99.00 / monthly

Business

USD 499.00 / monthly

Enterprise

USD 2,500.00 / monthly