What it is: the name that appears as the sender when an SMS notification is sent to the recipient. Can be defined at multiple sites at once; the system always applies the most specific one.
Setup levels, top to bottom:
- On the request itself (smsFrom field when creating the API request): if indicated here, always has the highest priority, above any other configuration.
- In the template: if the request does not indicate a sender, the one configured in the “Sender” section of the used template is used.
- At the group/client level: If neither the request nor the template indicate this, the sender configured in the group tab is used.
- En el nivel general de instalación: if nothing is configured in the previous levels, the globally defined sender is used for the entire installation.
Restrictions to consider:
- If no alias is set up, or the client does not have its own alias registered with CNMC, the alias “VIAFIRMA” will be used by default.
- The configured sender may not appear as is in all countries. Many local regulators require the sender’s name (Sender ID) to be pre-registered in order to use it, and in its absence the operator can filter the SMS, replace the sender with a generic numeric code or mark it as suspicious. Before setting a sender for a particular country, it is advisable to consult the applicable regulations: SMS regulation summary by countries.
- In Spain, the alias must match exactly (character to character, including upper/lower case) with the one registered at CNMC. If it does not match exactly, the operator can reject or filter the shipment even though the name “resembles” the registered one. For example, if in the CNMC’s alias search the existing record is “VIAFIRMA” (capitalized), setting the sender as “Viafirma” would not be valid: you have to use exactly “VIAFIRMA”. Always check the exact alias in that search engine before setting it up.
Important disclaimer:
Once the client has provided us with the exact registered alias, Viafirma can set it up at the group level. However, when the sender is defined from the API (in the request) or from a template, that configuration is introduced and maintained by the client itself, so the responsibility that the value used matches exactly with the alias registered at CNMC falls on the client in these two cases.