Question 1

Why would I use my own SMS gateway?

Accepted Answer

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

Question 2

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 Enafeedback support. Only the encrypted blob is stored.

Question 3

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. This ensures critical notifications (like ticket updates and tracking codes) are delivered.

Question 4

Does BYO SMS work for visitor notifications too?

Accepted Answer

Yes. Visitor-facing SMS (e.g. tracking code delivery, status update notifications) can also route through your BYO provider. Security SMS (e.g. cleaning personnel code recovery) always uses transactional routing and does not count against quota.

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 for a number range.

Your SMS gateway. Your contracts. Your numbers.

Supported SMS providers.

NetGSM

Bird (formerly MessageBird)

Twilio

Infobip

Custom Webhook

BYO SMS FAQ

See Enafeedback in your environment.