DocsIntegration Guides
Integrating with Your CRM / ERP
Architectural trade-offs between direct phone recipient sending vs. full contact database synchronization.
6 min read•Guide
Architectural Approaches
When integrating PingStack with your existing CRM, school ERP, or billing software, you have two primary patterns:
Option A: Direct Recipient Sending (Recommended for Existing CRMs)
If your database is already the single source of truth for customer data, pass phone numbers and variables directly via `/api/v1/messages` or `/api/v1/campaigns/{id}/launch` (Pattern C).
* **Pros**: Zero data synchronization lag, no duplicate database maintenance, immediate dispatches.
* **Cons**: Contacts are registered on the fly in PingStack for Inbox visibility.
Option B: Full Contact & Group Synchronization
Sync customer records via `/api/v1/contacts/bulk` and group memberships via `/api/v1/groups/{id}/contacts`.
* **Pros**: Non-technical team members can view rich contact metadata and launch broadcast campaigns directly inside the PingStack Workspace UI.
* **Cons**: Requires managing two-way synchronization.