--- title: "Messages" slug: "messages" updated: 2026-09-01T16:16:11Z published: 2026-09-01T16:16:11Z canonical: "learn.servitly.com/messages" stale: true --- > ## Documentation Index > Fetch the complete documentation index at: https://learn.servitly.com/llms.txt > Use this file to discover all available pages before exploring further. # Messages In the Appearance / Messages page, you can configure all the messages the application sends to the users when a certain event occurs. This page is divided into several sections, each covering a specific set of messages. - **Account and Security**: The set of messages that are sent when registering or updating an account. - **Account Suspension**: The set of messages that are sent when an account is about to expire, has expired, or is being reactivated. - **Alerts**: The default messages that are sent when an alarm is activated or cleared. - **Partners**: The messages involved in managing client assignments to partners. - **Payments**: The messages involved in payment processing. - **Work Sessions**: The default messages that are sent when a work session is started or stopped. ![](https://cdn.document360.io/6759e9c9-3ce3-49df-965a-7231d2d9a10a/Images/Documentation/image(21).png) ## Editing messages Within the list of messages, you can click on each message to expand it and edit the associated texts. ![](https://cdn.document360.io/6759e9c9-3ce3-49df-965a-7231d2d9a10a/Images/Documentation/image(22).png) The subject and body are available for messages sent only via email. Messages that can be sent through different channels (e.g., email, SMS, push) can have multiple texts to define, for example, short and long messages. ## Placeholders Within the email subject and payload, you can use the placeholders to generate dynamic content. ```plaintext

NEW ACCOUNT CREATED

Hi ${fullName},

Welcome to ${applicationName}, a new account has been prepared for you.

Click on the link below in order to complete the registration:
${accountActivationUrl}

Thanks,
${companyName}

``` Here is the list of common available placeholders: | **Placeholder** | **Description** | | --- | --- | | *applicationName* | The name of the application. You can manage this label within the Labels page. | | *companyName* | The name of the company that owns the application. You can manage this label within the Labels page. | | *fullName* | The concatenation of the user's first and last name. | | *user.firstName* | The user's first name. | | *user.lastName* | The user's last name. | | *unsubscribeUrl* | The URL that users can click to turn off alert and work-session notifications. | According to the message type, you can use the following placeholders to include a specific operation URL. ### Account creation | **Placeholder** | **Description** | | --- | --- | | *accountActivationUrl* | The URL the user must click to activate the account. | ### Self-account creation | **Placeholder** | **Description** | | --- | --- | | *createPreliminaryUserUrl* | The URL the user must click to activate the account in case of self-registration. | ### Self-account registration already existing | **Placeholder** | **Description** | | --- | --- | | *createPreliminaryUserExistUrl* | The URL the user must click to activate the account in case of self-registration and already registered user. | ### Information updated | **Placeholder** | **Description** | | --- | --- | | *updater* | The user who performs the update of sensible information. | | *updatedObject* | The update object (e.g. customer, location, thing). | | *updatedProperties* | The list of updated properties. | | *updateTimestampFormattedTZ* | The formatted timestamp of the occurred update. | ### Account inactivity | **Placeholder** | **Description** | | --- | --- | | *suspensionDate* | The date the user account will be suspended for inactivity. | ### Alert activated and cleared Within messages notifying alerts activation and clearing, you can use any general placeholder and any [event placeholder](/v1/docs/placeholders). To comply with the GDPR, DPS users must be able to opt out of any notification that is not strictly necessary for the delivery of the service. To support this, you can insert the `unsubscribeUrl` placeholder in the body of your notification emails. The placeholder resolves to a URL that, when opened by the user, disables alert notifications. For more details about the DPS user experience, refer to the [User Profile](/v1/docs/dps-user-profile#unsubscribe-from-notifications) article. ### Partner authorization update | **Placeholder** | **Description** | | --- | --- | | *customerName* | The name of the customer that is authorized on a partner. | | *partnerName* | The name of the partner that is authorized on a client. | | *customerDetailsUrl* | The authorized customer details page URL. | | *locationDetailsUrl* | The authorized location details page URL. |