The International Settings are useful if you're using your Agillic instance for multiple countries or different languages. You can find them under the 'System Settings' section of the Settings module.
In the 'International Settings' section, you'll find the following settings:
Country Code
Default Callback Country Calling Code
If you set a default country code, Agillic will identify all the recipients where the MSISDN field is missing a country code. Agillic will then temporarily prefix the default country code and check if the phone number is valid. The validation takes the default country's formatting standards into account. The fixed person data field MSISDN_TYPE will be updated to reflect the results of the assessment. The assessment result could be any of the following - Invalid, Mobile, Fixed Line, Mobile or Fixed Line, Toll-Free, Premium Rate, Shared Cost, VOIP, Personal Number, Pager, UAN, Voicemail, or Unknown.
The MSISDN will be reassessed on every SMS send out, on any changes made to a recipient's MSISDN, or on any changes to the default fallback country code. Using the default fallback country calling code feature will not introduce any changes to the value in the MSISDN Person Data Field.
Languages
Language versions allow you to create different versions of content such as emails, pages, and SMS to add an additional layer of personalisation.
A recipient's language is defined as a Person Data field. You can adjust the language field in System Settings in the 'Person Data' section.
A language version has a display name and language key. If a recipient doesn't have a set language or their value doesn't match any provided language key, we use the default language. When you create a new content item, the default language version is set automatically.
With our date format language feature, you can also define the display language and format for each language version that you’re working with. This feature gives you even more flexibility for working with a multilingual setup.
Language versions define both display formats for all date, timestamp, and number data field types. We borrow our date and timestamp display formats from Java to support as many format patterns and languages as possible. For example, if the date pattern 'EEE, MMMM d, yyyy' is selected with English language, the output would be 'Sat, July 4, 2020'. Using the same pattern with Danish selected would show as 'lør., juli 4, 2020'. The number display format affects which decimal separators are applied on numbers, whether they be full stops or commas. The differing display formats are only applied once content has been rendered for a recipient.
Language date versions
Time Zone
Enable Time Zone Aware Scheduling
When this setting has been enabled, you can use time zone aware scheduling. This means you can deliver outbound content to recipients in their respective time zones.
When the feature is enabled, you will be able to activate time zone aware scheduling for any Flow, except for Flows that are scheduled by the minute or by the hour.
Default Time Zone
For recipients without time zone information, they will be assigned the default time zone.
You can change the time zone settings, as well as other International settings, in the Settings module under 'System Settings', then 'International'. All data in the connected TIME_ZONE Person Data field should use the TZ-database format, such as 'Europe/Copenhagen'.
Time Zone configuration in International Settings