As a complement to the use of mail templates within AFLS, the use of macros to include information related to the case is enabled.
Tokens are quick texts that are populated with the information from the work order or additional fields.
⚐ Example tokens: A greeting to the client by name could be written as: Hello, Sir(a) Template:ClientName.
In some cases, tokens will reference securities that may not yet exist.
⚐ Example tokens with Exception: the date of care if it has not already been assigned.
⚐ Note: For the use of the tokens, it is proposed to use double brackets, e.g. {{Id}}. These tokens will not handle multilanguage, they will always be the same strings for all languages supported in AFLS. Tokens will not account for case usage.
| Token | Definition | Exceptions |
|---|---|---|
| {{WorkOrder}} | Order number | |
| {{AgentName}} | Name of the agent who answers the order | If it has not been assigned will appear: Not yet defined. (in multilanguage) |
| {{AttentionDate}} | Date of Operation | If it has not been assigned, it will appear: Not yet defined. |
| {{AgentPhone}} | Phone number of the agent responding to the order | If you have not assigned, it will appear. Unavailable. |
| {{Subject}} | Order Subject | Full subject |
| {{ClientName}} | Client Name | None, it must always exist. |
| {{ClientPhone}} | Customer Phone | None, it must always exist. |
| {{Address}} | Order Address | None, it must always have an address |