Native CRM plugins
Operator teams do not want another console. The plugins put sending inside the CRM they already work in, and push state, consent and cost back into it.
- Connectors
- 8 native
- Sync
- Bi-directional
- Latency
- Under 2 s
Build order
- 1
Install the connector
Add the plugin from the marketplace of the platform you run and paste a scoped key.
- 2
Map the fields
Point player id, phone, locale and consent at their equivalents. Anything unmapped is simply not synced.
- 3
Choose the direction
Decide which system wins on conflict for each field. The default is newest write.
- 4
Send from where you work
Trigger a campaign, a journey step or a single message without leaving the CRM.
What it gives you
Two-way sync with the systems your team already runs
- Segment push from the CRM into a send, with the audience resolved at send time rather than at export time
- Delivery state, cost and reply text written back onto the player record
- Consent flags treated as the shared source of truth, with conflict resolution on the newest timestamp
- Field mapping held in the plugin, so schema changes on either side do not need a code deploy
- Per-agent send limits and approval steps for manual outbound
- A generic outbound connector for in-house systems that speaks the same payload shape
Wire native crm plugins into your stack
Sandbox keys are free and behave exactly like production, including the failure codes. Nothing to schedule and nobody to talk to first.