PulseGate — Integration

Overview

Request SMS, WhatsApp, voice, and supported messaging delivery for announcements, event reminders, promotion notices, and campaign stages.

Capabilities

• Map engagement events to approved SMS, WhatsApp, and voice templates

• Use stable campaign, content, snapshot, and recipient correlation identifiers

• Respect channel eligibility, consent, provider restrictions, and template approval

• Ingest delivery, failure, rejection, and retry outcomes

• Keep transport, provider credentials, templates, and delivery queues outside EngagementHub

1. 1

   Step 1

   Connect PulseGate and grant the required internal app and event permissions.

   Back to top
2. 2

   Step 2

   Map each communication trigger to a PulseGate message code or template binding.

   Back to top
3. 3

   Step 3

   Map variables such as customer_name, title, project_name, event date, venue, promotion expiry, and CTA link.

   Back to top
4. 4

   Step 4

   Choose the audience snapshot and channel plan.

   Back to top
5. 5

   Step 5

   Run controlled test messages on each enabled channel.

   Back to top
6. 6

   Step 6

   Launch and reconcile PulseGate outcomes into campaign reporting.

   Back to top

Limitations

• Only provider-approved templates may be available for some channels.

• PulseGate must apply current consent, opt-out, invalid-number, and rate-limit rules at dispatch time.

• Voice delivery may require separate scripts, provider configuration, and do-not-call policy.

FAQs

Pricing