Notification channels
Manage email, SMS, in-app, push and webhook channels, choose between the ENA Gateway and your own provider accounts, and set SMS quiet hours.
Notification channels decide how EnaFeedback sends alerts, personnel codes and visitor status updates, and through which provider. Out of the box, email and SMS work through the ENA Gateway with no extra setup. You can connect your own provider account if you prefer.
Required role
Provider settings live under System settings → Integrations and can only be changed by users with the Owner role. SMS quiet hours are set by each user for themselves.
Channels and supported providers
EnaFeedback has 5 channels: Email, SMS, In-app, Push and Webhook.
| Channel | Providers |
|---|---|
| ENA Gateway, Resend, SendGrid, SMTP (none / STARTTLS / TLS) | |
| SMS | ENA Gateway, NetGSM, Twilio, Bird |
| Push | ENA Gateway, Firebase FCM (HTTP v1 service account) |
| Webhook | ENA Gateway, custom webhook URL |
| In-app | No external provider; shown under the bell icon in the sidebar |
What the ENA Gateway actually does
- Email is sent through Resend.
- SMS is sent through NetGSM.
- Push and webhook are not enabled on the ENA Gateway. To use webhooks, set your own webhook URL. Push notifications are not offered in the alert channel pickers yet, and they are off in the mobile app.
One provider, no failover
Each channel runs one active provider at a time. If a send fails, EnaFeedback does not switch to another provider automatically. If you delete your own provider, the channel falls back to the ENA Gateway.
Connect your own provider
Teams usually bring their own account to send from their organization's email domain, to use their approved SMS sender name, or to use an existing contract.
Open Integrations
Go to System → System settings → Integrations.
Choose the channel and provider
For SMS, for example, pick NetGSM, Twilio or Bird. For email, pick Resend, SendGrid or SMTP.
Enter the credentials
Enter the API key, user name or SMTP details from your provider. These secrets are stored encrypted with AES-256-GCM on the server.
Activate and test
Make the provider active. Then confirm delivery by triggering an alert to yourself or by resending a personnel code.
SMS quiet hours
SMS quiet hours are set per user. During quiet hours, SMS from alert rules and follows are queued. When the window ends, they go out as one digest SMS.
- Quiet hours apply only to rule and follow SMS.
- Email and in-app alerts are not affected.
Monitor deliveries
Every delivery is logged. Under System → Records → Notification deliveries, each row shows a status:
| Status | Meaning |
|---|---|
| Pending | Waiting to be sent |
| Sent | The provider accepted the message |
| Failed | The provider returned an error |
| Skipped | The delivery was not sent on this channel |
Recipients are masked on this screen. The table can be exported to Excel.
Tips
- "Your request status was updated" messages go to visitors by email and/or SMS when they left contact details. They are written in Turkish, English, German or Arabic.
- Personnel codes can be sent by email, SMS or both. After switching SMS providers, send a code to a test staff member to confirm the channel works.
Related articles
Can't find what you need?
Our support team can help with anything from setup to reporting.
Alert rules
Turn on the 15 alert rules that email, text or notify your team in-app when a low hygiene rating, a complaint or a forgotten check-out comes in.
Follows and personal notifications
Follow a location, survey, feedback item or staff member to get email, SMS or in-app notifications only for the events that matter to you.