Question 1

Why would I use my own SMS gateway?

Accepted Answer

Using your own SMS gateway gives you control over your sender ID, existing volume discounts, and dedicated sender relationships. SMS sent through your gateway does not count against the EnaBed platform SMS quota.

Question 2

What bed events trigger SMS?

Accepted Answer

When SMS alerting launches, you will be able to configure operational notifications for bed status changes and capacity thresholds. Security codes will always use transactional routing.

Question 3

How are my SMS provider credentials secured?

Accepted Answer

Credentials (API keys, passwords, webhook secrets) are encrypted using AES-GCM before storage. They are never logged, displayed after initial entry, or accessible to EnaBed support.

Question 4

What if my provider sends an error?

Accepted Answer

Automatic failover activates: if your BYO provider returns a technical error, the SMS is re-attempted via the platform default providers — NetGSM for Turkish numbers, Bird for international.

Question 5

Can I use different providers for different routing?

Accepted Answer

Currently, one platform-level BYO provider is configured per tenant. The platform automatically routes Turkish numbers through the Turkey default and international numbers through the global default when BYO is not configured.

Your SMS gateway. Your contracts. Your numbers.

Supported SMS providers.

NetGSM

Bird (formerly MessageBird)

Twilio

Infobip

Custom Webhook

BYO SMS FAQ

See EnaBed in your facility.