Email templates are used for the automatic notification of users such as notifying linguists or vendors about new jobs or notifying project managers when a job is marked as Completed. Templates are applied when defining an automated project.
Template macros can be used for the emails and CC or BCC email addresses can be added to send copies to other users. Basic HTML formatting tags can be used to modify the templates.
The first email template available for automated notifications is selected.
To modify an email template, follow these steps:
-
From the Settings
page, scroll down to the section and click on Email templates.
The
page opens. -
Click on the name of a template.
The
page opens. -
Modify the template as required and click Save.
The changes are applied to the selected template.
These can be used in email templates and submitter portal templates.
Some macros are specific and can be used only in specific templates and in specific places. Test templates before using.
Macro |
Email Templates |
Submitter Portal Email Template |
Used |
Note |
---|---|---|---|---|
apcName |
Yes |
No |
body |
Only useable in APC email templates (e.g. New automated project, Automated project source update, Project status changed). |
automationWidget.quote |
No |
Yes |
subject, body |
|
automationWidget.submissionDate |
No |
Yes |
subject, body |
|
automationWidgetEditPage.url |
Yes |
No |
subject, body |
|
automationWidgetPage.id |
No |
Yes |
subject, body |
|
automationWidgetPage.url |
No |
Yes |
subject, body |
|
automationWidgetUser.email |
No |
Yes |
subject, body |
|
buyer.name |
Yes |
No |
subject, body |
|
comment |
Yes |
No |
subject, body |
|
connectorName |
Yes |
No |
body |
Only useable in APC email templates (e.g. New automated project, Automated project source update, Project status changed). |
connectorType |
Yes |
No |
body |
Only useable in APC email templates (e.g. New automated project, Automated project source update, Project status changed). |
edition.name |
Yes |
No |
subject, body |
|
edition.title |
Yes |
No |
subject, body |
|
instantQuote.price |
No |
Yes |
subject, body |
|
instantQuote.submissionDate |
No |
Yes |
subject, body |
|
instantQuotePage.id |
No |
Yes |
subject, body |
|
instantQuotePage.url |
No |
Yes |
subject, body |
|
instantQuoteUser.email |
No |
Yes |
subject, body |
|
job.Count |
Yes |
No |
subject |
|
job.dateDue |
Yes |
No |
subject, body |
|
job.name |
Yes |
No |
subject, body |
|
job.number |
Yes |
No |
subject, body |
|
job.previousWorkflow.dateDue |
Yes |
No |
subject, body |
|
job.sourceLang |
Yes |
No |
subject, body |
|
job.status |
Yes |
No |
subject, body |
|
job.targetLang |
Yes |
No |
subject, body |
|
job.wordCount |
Yes |
No |
subject, body |
|
jobInfo |
Yes |
No |
subject, body |
Special block macro that enables providing info for many jobs. For example:
will provide information for all jobs one by one. |
jobs.newStatus |
Yes |
No |
subject |
|
linguist.email |
Yes |
No |
subject, body, cc, bcc |
|
linguist.firstName |
Yes |
No |
subject, body, cc, bcc |
|
linguist.jobTitle |
Yes |
No |
subject, body, cc, bcc |
|
linguist.lastName |
Yes |
No |
subject, body, cc, bcc |
|
linguist.organization.id |
Yes |
No |
subject, body, cc, bcc |
|
linguist.organization.name |
Yes |
No |
subject, body, cc, bcc |
|
linguist.timezone |
Yes |
No |
subject, body, cc, bcc |
|
linguist.userName |
Yes |
No |
subject, body, cc, bcc |
|
organization.country |
Yes |
No |
subject, body |
|
organization.name |
Yes |
No |
subject, body |
|
organization.phone |
Yes |
No |
subject, body |
|
organization.timezone |
Yes |
No |
subject, body |
|
previousWorkflow.name |
Yes |
No |
subject, body |
|
previsouWorkflow.abbr |
Yes |
No |
subject, body |
|
project.client |
Yes |
Yes |
subject, body |
|
project.dateDue |
Yes |
Yes |
subject, body |
|
project.domain |
Yes |
Yes |
subject, body |
|
project.id |
Yes |
Yes |
subject, body |
|
project.internalId |
Yes |
Yes |
subject, body |
|
project.name |
Yes |
Yes |
subject, body |
|
project.owner |
Yes |
Yes |
subject, body |
|
project.owner.email |
Yes |
Yes |
cc, bcc |
|
project.owner.firstName |
Yes |
Yes |
cc, bcc |
|
Yes |
Yes |
cc, bcc |
||
project.owner.lastName |
Yes |
Yes |
cc, bcc |
|
project.owner.organization.id |
Yes |
Yes |
cc, bcc |
|
Yes |
Yes |
cc, bcc |
||
project.owner.timezone |
Yes |
Yes |
cc, bcc |
|
project.owner.userName |
Yes |
Yes |
cc, bcc |
|
project.sourceLang |
Yes |
Yes |
subject, body |
|
project.status |
Yes |
Yes |
subject, body |
|
project.subDomain |
Yes |
Yes |
subject, body |
|
project.targetLang |
Yes |
Yes |
subject, body |
|
project.url |
Yes |
Yes |
subject, body |
|
quote.confirmUrl |
Yes |
No |
subject, body |
|
quote.id |
Yes |
No |
subject, body |
|
quote.name |
Yes |
No |
subject, body |
|
quote.price |
Yes |
No |
subject, body |
|
quote.status |
Yes |
No |
subject, body |
|
quote.targetLang |
Yes |
No |
subject, body |
|
quote.url |
Yes |
No |
subject, body |
|
quoteInfo |
Yes |
No |
subject, body |
Special block macro. See |
recipient.email |
Yes |
Yes |
subject, body |
|
recipient.firstName |
Yes |
Yes |
subject, body |
|
recipient.jobTitle |
Yes |
Yes |
subject, body |
|
recipient.lastName |
Yes |
Yes |
subject, body |
|
recipient.organization.id |
Yes |
Yes |
subject, body |
|
recipient.organization.name |
Yes |
Yes |
subject, body |
|
recipient.timezone |
Yes |
Yes |
subject, body |
|
recipient.userName |
Yes |
Yes |
subject, body |
|
sender.email |
Yes |
No |
subject, body, cc, bcc |
|
sender.firstName |
Yes |
No |
subject, body, cc, bcc |
|
sender.jobTitle |
Yes |
No |
subject, body, cc, bcc |
|
sender.lastName |
Yes |
No |
subject, body, cc, bcc |
|
sender.organization.id |
Yes |
No |
subject, body, cc, bcc |
|
sender.organization.name |
Yes |
No |
subject, body, cc, bcc |
|
sender.timezone |
Yes |
No |
subject, body, cc, bcc |
|
sender.userName |
Yes |
No |
subject, body, cc, bcc |
|
sourcePost.url |
Yes |
No |
subject, body |
|
vendor.name |
Yes |
No |
subject, body |
|
webhookError |
Yes |
No |
body |
|
webhookUrl |
Yes |
No |
body |
|
workflow.abbr |
Yes |
No |
subject, body |
|
workflow.name |
Yes |
No |
subject, body |
Type:
Instant quote failed
Suggested name:
Instant Quote Failed (en)
Suggested subject:
Instant Quote Failed
Suggested body:
Dear customer, We are sorry but your quote could not be generated. Please email your files for translation directly to me by responding to this email. Thank you. Best regards, {sender.firstName} {sender.lastName} {sender.email}
Type:
Instant quote ready
Suggested name:
Instant Quote Ready (en)
Suggested subject:
Instant Quote {instantQuotePage.id} Ready
Suggested body:
Dear customer, Your quote {instantQuotePage.id} is ready: {instantQuotePage.url} Let me know if you have any questions. Best regards, {sender.firstName} {sender.lastName} {sender.email}
-
Launched manually by a Project Manager by clicking on Tools and selecting in a project, or sent automatically upon the creation of a new job that has the option enabled.
-
This email is sent to the Linguist(s) or Vendor(s), giving notification regarding the availability of new translation job(s).
Type:
Job assigned
Suggested name:
New Work (en)
Suggested subject:
New Work
Suggested body:
Dear {linguist.firstName}, We have new work for you: {jobInfo} File: {job.name} Language: {job.sourceLang} -> {job.targetLang} Due: {job.dateDue} {/jobInfo} Sign in to Phrase to get started: {project.url} Let me know, if you have any questions. Best regards, {sender.firstName} {sender.lastName} {sender.email} ---------------------------------------------------------- Sign in at: {system.url} Username: {linguist.userName} If you do not have a password already, create it by clicking on this link: {system.url.passwordReset}
-
Launched automatically.
-
When a Linguist sets a job status to Rejected in a project with multiple workflow steps, the Linguist in the previous workflow step is notified.
-
Disabled by default - can be enabled on a user-level by editing a Linguist profile and enabling the Reject jobs option.
-
Workflow hierarchical structure are applied in relation to the propagation of segments.
Type:
Job Rejected
Suggested name:
Job rejected (en)
Suggested subject:
Project {project.name}: Job(s) Rejected
Suggested body:
Dear {recipient.firstName}, Job(s) that you completed have just been rejected by a linguist in the ({nextWorkflow.name}) and need to be corrected by you. These jobs need to be corrected: Project: {project.url} {jobInfo} File: {job.name} Language: {job.sourceLang} -> {job.targetLang} Due: {job.dateDue} {/jobInfo} Let me know, if you have any questions. Best regards, {sender.firstName} {sender.lastName} {sender.email} P.S. This email was generated automatically.
-
Launched automatically.
-
When a Linguist or Vendor changes a job's status, this email notification is sent to the Project Owner.
Type:
Job status changed
Suggested name:
Job Status Changed (en)
Suggested subject:
Project {project.name}: {jobs.count} Job(s) {jobs.newStatus}
Suggested body:
Dear {recipient.firstName}, Your linguist user {linguist.firstName} {linguist.lastName} ({linguist.email}) has changed status for the following jobs: Project: {project.url} {jobInfo} File: {job.name} Changed to status: {job.status} Language: {job.sourceLang} -> {job.targetLang} Due: {job.dateDue} {/jobInfo}
-
When a new user is added to an organization, an email will be sent to them automatically which contains their username and a link for creating a password. The automatic email sent upon a user creation follows a specific template, due to GDPR, and cannot be customized. In case of organizations with SSO enabled, the email does not contain the link for creating a password.
However, a Project Manager can also send login credentials manually by selecting a user in the Users page and clicking on the Email login button. The email template for this action can be customized in organization settings.
-
An email with the user's username and the login link is sent. The user then generates a new password with the link provided.
Type:
Login Info
Suggested name:
Login info (en)
Suggested subject:
Your Phrase Login Info
Suggested body:
Dear {recipient.firstName}, I have created a user profile for you in Phrase and this is your login info: Username: {recipient.userName} Sign in at: {system.url.passwordReset} (This will start the process of password creation.) Let me know, if you have any questions. Best regards, {sender.firstName} {sender.lastName} {sender.email}
-
Templates can be selected in the
modal.
Type:
LQA scorecard
Suggested name:
LQA Scorecard
Suggested subject:
{sender.firstName} {sender.lastName} shared LQA Scorecard with you{userName} shared LQA scorecard with you
Suggested body:
Dear {recipient.firstName}, {sender.firstName} {sender.lastName} shared LQA scorecard with you. Project name: {project.name} {jobInfo} File: {job.name} Language: {job.sourceLang} -> {job.targetLang} {/jobInfo} You can download the scorecard here: {report.file.url} The link expires on {report.file.expires}.
Type:
New Project via Automated Project Creation
Suggested name:
New Project via Automated Project Creation (en)
Suggested subject:
New Project via Automated Project Creation
Suggested body:
Dear {recipient.firstName}, A new project "{project.name}" has been created via your Automated Project Creation. Project: {project.url} Automated Project Creation: {apc.name} Best regards
Type:
New project via submitter portal
Suggested name:
New project via submitter portal (en)
Suggested subject:
New submitter portal project from {automationWidgetUser.email}
Suggested body:
Dear {recipient.firstName}, A new project has been created via your instant quote form: {project.url} The jobs were submitted by: {automationWidgetUser.email}
Type:
New project via instant quote form (unsupported files)
Suggested name:
New IQ Project (UNSUPPORTED FILES) (en)
Suggested subject:
New IQ Project from {instantQuoteUser.email} (UNSUPPORTED FILES)
Suggested body:
Dear {recipient.firstName}, A new project has been created via your instant quote form: {project.url} The files were submitted by: {instantQuoteUser.email} IMPORTANT: Please note that some of the files are not supported by Phrase. You will find them in the project's Reference File section.
-
Launched automatically.
-
When unsupported files are submitted via the submitter portal, the Project Manager is notified.
Type:
New project via submitter portalautomation widget (unsupported files)
Suggested name:
New project via submitter portalautomation widget (en)
Suggested subject:
New submitter portal project from {automationWidgetUser.email} (UNSUPPORTED FILES)
Suggested body:
Dear {recipient.firstName}, A new project has been created via your instant quote form: {project.url} The files were submitted by: {automationWidgetUser.email} IMPORTANT: Please note that some of the files are not supported by Phrase. You will find them in the project's Reference File section.
-
Launched automatically.
-
The Vendor will receive an email when a Project Manager shares a project with them by clicking on Share and selecting in a Project.
Type:
Shared project assigned
Suggested name:
New Shared Project (en)
Suggested subject:
New Shared Project
Suggested body:
Dear {vendor.name}, A new shared project has been assigned to you: {project.url} Let me know, if you have any questions. Best regards, {sender.firstName} {sender.lastName} {sender.email}
-
Launched automatically.
-
When a Linguist sets a job status to Completed in a project with multiple workflow steps, the Linguist in the next workflow step is notified.
Type:
Next step ready
Suggested name:
Next step ready (en)
Suggested subject:
Project {project.name}: Job(s) Ready, You Can Start
Suggested body:
Dear {recipient.firstName}, You have been assigned work in the {workflow.name} workflow step. We would like to let you know that you can start now. The linguist who was in charge of the preceding workflow step ({previousWorkflow.name}) has just changed status to Completed for the following job(s): Project: {project.url} {jobInfo} File: {job.name} Changed to: {previousWorkflow.name} - {job.status} Language: {job.sourceLang} -> {job.targetLang} Due: {job.dateDue} {/jobInfo} Job in the preceding workflow step still not completed? Read more: https://support.phrase.com/hc/en-us/articles/5709717879324 Let me know, if you have any questions. Best regards, {sender.firstName} {sender.lastName} {sender.email} P.S. This email was generated automatically.
-
Launched automatically.
-
When a Vendor changes a project status, an email notification is sent to the Buyer.
Type:
Shared project status changed
Suggested name:
Project Status Changed (en)
Suggested subject:
Project Status Changed
Suggested body:
Dear {recipient.firstName}, Your vendor {vendor.name} has changed the status of the project below to: {project.status}. Project name: {project.name} Project url: {project.url}
-
Launched automatically.
-
The Buyer will receive an email when a Project Manager shares a project with them by clicking on Share and selecting menu in the project.
Type:
Project transferred to buyer
Suggested name:
New Project (en)
Suggested subject:
New Project
Suggested body:
Dear {buyer.name}, A new shared project has been created by us that you can also access in your profile: {project.url} Let me know, if you have any questions. Best regards, {sender.firstName} {sender.lastName} {sender.email} {vendor.name}
-
Launched automatically.
-
When files submitted via the submitter portal cannot be processed, this email is sent to the person who submitted them.
Type:
Quote failed
Suggested name:
Quote Failed (en)
Suggested subject:
Quote Failed
Suggested body:
Dear customer, We are sorry but your quote could not be generated. Please email your files for translation directly to me by responding to this email. Thank you. Best regards, {sender.firstName} {sender.lastName} {sender.email}
-
Launched automatically.
-
This email template will be sent to customers when files are submitted via the submitter portal.
Type:
Quote ready
Suggested name:
Quote Ready (en)
Suggested subject:
Your Quote No. {automationWidgetPage.id} Is Ready
Suggested body:
Dear customer, Your quote {automationWidgetPage.id} is ready: {automationWidgetPage.url} Let me know if you have any questions. Best regards, {sender.firstName} {sender.lastName} {sender.email}
Type:
Source update via Automated Project Creation
Suggested name:
Source update via Automated Project Creation
Suggested subject:
Source update via Automated Project Creation
Suggested body:
Dear {recipient.firstName}, The source segments of "{project.name}" have been updated via your Automated Project Creation. Project: {project.url} Automated Project Creation: {apc.name} Best regards, {sender.firstName} {sender.lastName} {sender.email}
-
Launched automatically.
-
When a Project Manager sets the status of a project that was created using the submitter portal to Completed, the client is notified by email with a link from which the translation can be downloaded.
Type:
Work completed
Suggested name:
Work Completed (en)
Suggested subject:
Work Completed
Suggested body:
Dear customer, The work has been completed and your files are ready for download: Project url: {instantQuotePage.url} Let me know if you have any questions. Best regards, {sender.firstName} {sender.lastName} {sender.email}