Sales FAQ

📦v1.0.0📅2026-04-28🔄Updated 2026-04-28👤Admin Team
use-casesmarket-and-positioningmessage-center

Sales FAQ

Answers to the questions and objections that come up most often during evaluation.

"We don't have DevOps capacity to host this ourselves."

Message Center is a single Next.js container + MongoDB. Deployment takes a competent engineer approximately one day using the provided Docker Compose or Kubernetes manifests. Once running, ongoing maintenance is minimal: certificate rotation (once a year), MongoDB index monitoring, and occasional version upgrades.

If you have an existing VPS or Kubernetes cluster running other services, Message Center is one more container. It does not require specialized SMS or SMPP expertise to deploy — that complexity lives in the SMS Core and Proxy layers.

For organizations with truly zero DevOps capacity, contact us to discuss managed deployment options.

"We already use Twilio / Infobip. Why switch?"

You probably do not need to switch entirely. Message Center is most compelling when one or more of these apply:

  1. You have data residency requirements that prevent routing subscriber data through the provider's cloud
  2. You want to use direct SMPP agreements (which you've negotiated, or plan to negotiate) to reduce per-message cost
  3. You need multi-tenant workspace isolation for multiple clients or departments — cloud CPaaS providers do not offer this natively
  4. You need a compliance audit trail that you own and control, not one dependent on a vendor support ticket

If none of these apply and Twilio or Infobip meets your requirements, you may not need to change.

"What happens if you stop supporting this product?"

Message Center's source code is part of your license — it does not phone home, and it does not stop working if the vendor disappears. A deployed instance will continue running indefinitely on the infrastructure you control.

Unlike SaaS tools, you are not dependent on the vendor's uptime, pricing decisions, or roadmap. Your deployed version remains functional regardless of what happens to the vendor.

"Our compliance team requires SOC 2 / ISO 27001 certification."

Message Center is a software platform, not a SaaS service. Certification requirements apply to the services and infrastructure you run — not to the software you deploy. The same way your compliance team certifies your MongoDB cluster or your Kubernetes environment, they would certify the environment you deploy Message Center into.

This is often easier for regulated buyers than negotiating with a cloud provider, because you control all the variables: where data is stored, who has access to the host, what logging is in place, and what encryption is applied.

The platform itself provides the compliance features your team will ask about: immutable audit log, RBAC, tamper-evident records, configurable retention.

"Can we customize the UI with our branding?"

Yes, under SKU 3 (Custom Adapter / white-label). This includes modifying the application name, logo, color scheme, and domain. The customization is done at the source level — this is a one-time engineering engagement as part of the SKU 3 delivery.

Basic deployments (SKU 2) use the default Message Center branding.

"We need SMS to integrate with our CRM / ERP / internal platform."

Integration approaches:

  1. Trigger mode campaigns via API — your application calls the Message Center BFF API to add numbers to an active trigger campaign. Suitable for OTP, transactional notifications, and event-driven sends.
  2. Upstream Core API — if you need deeper integration (custom scheduling, recipient management at the job level), the SMS Gateway Core exposes a REST API that your application can call directly with the service JWT. This bypasses the Message Center management layer and is suitable for automated, high-frequency programmatic sends.
  3. Webhook / export — delivery reports can be exported from campaigns as downloadable files and imported into your CRM/ERP.

The right integration pattern depends on your use case. For marketing/scheduled campaigns initiated by people, the Message Center UI workflow is typically the right path. For automated transactional sends initiated by applications, direct Core API access is simpler.

"We need support for RCS / WhatsApp / email alongside SMS."

Message Center is SMS-only. The Core + Proxy stack is built around the SMPP protocol.

If omnichannel messaging (SMS + WhatsApp + RCS + email from a single platform) is a requirement, cloud-based CPaaS providers (Infobip, Bird/MessageBird, Sinch) are better suited — they have invested heavily in this area.

Message Center's value is in the governance layer for SMS specifically, in environments where data sovereignty or carrier integration requirements make cloud omnichannel tools unsuitable.

"What does it cost? We need a budget number."

Message Center is sold as a one-time platform license, not a per-message subscription. Pricing depends on the SKU (1: gateway only, 2: full stack, 3: custom adapter) and the scope of any customization or deployment support.

Contact the sales team for a quote. The commercial terms we do not publish here — but the TCO comparison model in ROI & TCO gives you the framework to evaluate the economics against your current spend.

"Can we evaluate before purchasing?"

Yes. The standard evaluation path:

  1. We provide a time-limited trial license and access to pre-built Docker images
  2. You deploy to your own infrastructure (or a test environment)
  3. You run the provided seed scripts to set up a demo workspace with test data
  4. You evaluate the platform against your functional and compliance requirements

Full documentation for deployment and configuration is available publicly. Technical evaluation typically takes 1–2 weeks.

"We're in a regulated market. Do you understand our compliance requirements?"

We cannot make specific legal claims for every jurisdiction — your legal team must review against your local regulations. What we can say:

  • Message Center's audit log, RBAC, and data residency model were designed specifically for regulated environments — telecoms, financial services, government
  • The platform has been deployed in markets with explicit data localization requirements (Central Asia)
  • The architecture is designed to satisfy the most common requirements we encounter: immutable audit trail, four-eyes moderation, sender registration enforcement, no data in vendor infrastructure

Bring your compliance team's specific checklist. We can walk through exactly how each requirement is addressed — and be honest where something requires additional customization or falls outside our scope.

"Can this handle millions of messages per day?"

Throughput capacity is determined primarily by your SMPP connection configuration and carrier agreement — not by Message Center itself. The BFF layer (campaign management, approval, recipient tracking) is lightweight and can be scaled horizontally if needed.

Tested parameters:

  • Recipient files up to 1 GB (approximately 10 million numbers) are supported via streaming upload
  • The Core processes jobs at the throughput of your SMPP session (configurable ESME connection count and TPS)
  • MongoDB handles campaign metadata and audit logs at typical enterprise volumes without specialized infrastructure

For capacity planning specific to your volume and architecture, see the deployment documentation.

Next Steps