SMS and short links
EnaFeedback builds every SMS from ready-made templates in four languages, keeps it to two segments and adds an ena.run short link. Language and quiet hours.
- Admin panel
This article was verified with an older release. Screen names or steps may differ in the current version.
Every SMS that EnaFeedback sends is built from the product's ready-made template list. Each SMS is short: it says what happened in one or two sentences, and the details sit behind an https://ena.run/… short link. This article is for Owner and Administrator users who set up SMS in the admin panel: which SMS go to whom, in which language, where the short links lead, and how quiet hours work.
Required role, permission and version
- The SMS provider is changed under System → System settings → Integrations, by the Owner role only. See Message channels.
- A staff member's Message language is set with the Personnel permission.
- Templates, short links and the per-staff message language arrived in EnaFeedback 2.1.114; the quiet-hours digest for admins in EnaFeedback 2.2.0. Short links need ENA Cloud 0.1.24 or later.
Which SMS are sent?
| Recipient | SMS | Link |
|---|---|---|
| Panel users | Ticket routed to your team, ticket status changed | The ticket in the panel |
| Panel users | Alert rule and follow alerts | The record in the panel |
| Panel users | Quiet-hours digest | The admin panel home page |
| Panel users and staff | A message written in the message center (sender and subject) | The message center, when all recipients are panel users or all are staff |
| Staff | Welcome and welcome reminder, personnel code | The mobile app page on www.enafeedback.com, with the organization code |
| Staff | Account activated, deactivated, record deleted | None |
| Staff | Attendance reminders, session closed automatically | None |
| Visitor | Your request status was updated | None |
| Test | Test SMS from Send test | None |
SMS to panel users and staff start with [Organization short name]. Visitor SMS carry no organization name and no link. SMS texts cannot be edited in the panel.
Languages
Every template exists in Turkish, English, German and Arabic. The language depends on the recipient:
| Recipient | Language |
|---|---|
| Panel users | The organization language |
| Staff | The Message language on the staff record; the organization language if none is set |
| Visitor | The language the visitor used on the form |
Set a staff member's message language
Open the staff record
On Personnel → Personnel, edit the staff member.
Pick the message language
In Message language, choose Türkçe, English, Deutsch, العربية or Organization language.
Save
Welcome, personnel code, account status and attendance messages are sent in this language from now on.
Length and characters
- Each SMS is at most two segments. Fields such as name, organization short name and subject have length limits; longer values are shortened. The organization short name is used up to 16 characters (12 in Arabic).
- If the text still exceeds two segments, the longest field is shortened first, then the link is dropped.
- The ENA Gateway and NetGSM send Turkish letters (ç, ğ, ı, ş, İ) with the Turkish character encoding. With Twilio and Bird, Turkish letters are replaced by their Latin equivalents so the SMS does not turn into a more expensive Unicode message.
- German ä, ö, ü and ß go out in the standard SMS encoding. Arabic SMS are Unicode, so Arabic fields are kept shorter.
- Typographic marks such as curly quotes and long dashes are replaced by plain ones so they do not turn the SMS into Unicode.
Keep the short name short
Enter the organization's short name in Organization identity with no more than 16 characters, so it shows in SMS without being cut.
Short links
Links in SMS are short links that start with https://ena.run/. Your organization's panel address is never written into an SMS; the link forwards to the right page when tapped.
- Ticket, alert and follow SMS open the record in the panel. You need to be signed in to the panel to see it.
- Staff welcome and code SMS open the mobile app page on www.enafeedback.com with your organization code.
- Short links are created through ENA Cloud, whichever SMS provider you use.
- If a link cannot be created, the SMS goes out without it; every text reads well without the link.
Quiet hours
| Setting | For whom | Where | What happens |
|---|---|---|---|
| SMS quiet hours | Each panel user, for themselves | Preferences → Alert preferences → Quiet hours | Alert rule and follow SMS are held; one digest SMS goes out when the window ends |
| Staff SMS quiet hours | All staff | Check-in / Check-out → Module management → Reminders & timesheet | Attendance reminder and auto-close SMS are not sent; they are skipped |
The digest SMS contains the number of alerts held during quiet hours and a link to the admin panel. Quiet hours do not affect e-mail or in-app messages. For details, see My preferences and Attendance.
When no organization name is set
Requires: EnaFeedback 2.3.0If no organization name has been entered yet, SMS use [EnaFeedback] in place of the organization name; "ENA" alone is never used. Templates that already name the product in the sentence (welcome, welcome reminder and the test SMS) are then written without an organization name.
Monitor deliveries
Every SMS shows with the SMS channel on the Message deliveries view of System → Records. An SMS waiting for quiet hours to end is Held; an SMS folded into a digest is Skipped. See Permissions and delivery.
Known limits
- SMS texts come from ready-made templates and cannot be edited per organization.
- An SMS never exceeds two segments; fields are shortened or the link is dropped when needed.
- Each channel runs one active SMS provider; a failed SMS is not passed to another provider.
Related articles
Can't find what you need?
Our support team can help with anything from setup to reporting.
Message channels
Manage the in-app, e-mail, SMS and webhook channels; choose the ENA Gateway or your own provider, test a channel and follow delivery statuses.
Webhooks
Set up a webhook that sends ticket routing and status-change events to your own system as HMAC-SHA256 signed JSON, follow retries and verify the signature.