P
PV
Many agencies already have their own SMS gateways, WhatsApp infrastructure, regional SMS providers, or communication platforms. Currently, the only supported telephony/messaging provider is Twilio, which limits flexibility, choice, and control.
It would be valuable to introduce a
pluggable Communications Provider framework
for SMS and telephony, allowing agencies and developers to connect their preferred provider or build custom integrations without replacing the existing native messaging channels.
Proposed Solution
Support could include:
  • REST API
  • Webhooks
  • OAuth or API Key authentication
  • Custom HTTP endpoints
  • Marketplace application integration
  • Optional SDK for building custom communication providers
This would allow agencies to connect providers such as:
  • Twilio
  • Vonage
  • MessageBird
  • TextAnywhere
  • Regional SMS providers
  • Self-hosted SMS gateways
  • Android SMS gateways
  • Proprietary agency messaging platforms
Suggested Provider Capabilities
A custom communication provider could expose a standard set of endpoints and events, including:
Outgoing
  • Send SMS
  • Send MMS (where supported)
  • Send OTP/verification messages
  • Place voice calls (optional)
  • Check message status
  • Upload media (where supported)
Incoming
  • Receive incoming SMS
  • Receive MMS (where supported)
  • Delivery receipts
  • Failed message notifications
  • Incoming call events (optional)
By standardising the interface, Boomerangme could support virtually any SMS or telephony provider without needing to build and maintain individual integrations for each one, giving agencies and enterprise customers significantly more flexibility while preserving the existing native messaging channel integrations.
This would make the messaging system provider-agnostic and far more scalable and it would significantly increase adoption among agencies and end clients who already operate their own communications infrastructure.
Thank you for considering this.