Stay organized with collections
Save and categorize content based on your preferences.
It is highly recommended to support localization in the Actions Center Appointments Redirect
integration. Users are shown a localized experience based on their language
settings. If no localization is set, the default text may be shown to the
user. You are able to provide localized text for many fields in the
integration, such as service names and descriptions. Please refer to our
feed
specification for the full list of fields that can be localized by using the
Text message.
Any field in the feeds that uses a Text message can be localized by providing
a localized_value for each supported language.
It is required to specify both the value and
localized_value.
We will show the localized_value based on the user’s locale
(which is set in the user’s language browser settings).
Value will be used as a default when the user’s locale is not in your
list of supported localizations
Should you not define value and the users locale is not in your list
of supported localizations we will use the first value present in
localized_value. While this fallback is available it is strongly
recommend for you to specify the default value explicitly.
If you do not support localization in your system, please set
localized_value and set locale with the only
language you support. Set value as well which may be used as a
default.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-09-18 UTC."],[[["\u003cp\u003eLocalization is highly recommended for the Actions Center Appointments Redirect integration to provide users with a tailored experience in their preferred language.\u003c/p\u003e\n"],["\u003cp\u003eDevelopers can localize many fields, including service names and descriptions, by using the \u003ccode\u003eText\u003c/code\u003e message and providing localized values for supported languages.\u003c/p\u003e\n"],["\u003cp\u003eIt's crucial to specify both a default \u003ccode\u003evalue\u003c/code\u003e and \u003ccode\u003elocalized_value\u003c/code\u003e within the \u003ccode\u003eText\u003c/code\u003e message for each localizable field.\u003c/p\u003e\n"],["\u003cp\u003eIf localization isn't supported, set \u003ccode\u003elocalized_value\u003c/code\u003e and \u003ccode\u003elocale\u003c/code\u003e with the single supported language and provide a default \u003ccode\u003evalue\u003c/code\u003e.\u003c/p\u003e\n"]]],["Localization is strongly recommended for the Actions Center Appointments Redirect integration, using the `Text` message to localize fields like service names. Provide a default `value` and a `localized_value` array for each supported language. The `localized_value` is displayed based on the user's browser language settings; otherwise, the `value` is shown as a default. If localization isn't supported, provide one `localized_value` and set `locale` with the single language you support, setting a default `value` as well.\n"],null,[]]