Email Templates
    1. Help Center | Memsource
    2. Settings & Subscription
    3. Email Templates
    Follow

    Email Templates and Automation Widget Macros

    Email Templates Overview

    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.

    Memsource selects the first email template available for automated notifications.

    To modify an email template, follow these steps:

    1. From the Setup Setup_gear.png page, scroll down to the Administration section and click on Email Templates.

      The Email Templates page opens.

    2. Click on the name of a template.

      The Edit Email Template page opens.

    3. Modify the template as required and click Save.

      The changes are applied to the selected template.

    Supported Email and Automation Widget Macros

    These can be used in email templates and Automation Widget templates.

    Some macros are specific and can be used only in specific templates and in specific places. Test templates before using.

    • {linguist.email}

    • {linguist.firstName}

    • {linguist.lastName}

    • {linguist.userName}

    • {sender.email}

    • {sender.firstName}

    • {sender.lastName}

    • {sender.timezone}

    • {sender.userName}

    • {recipient.email}

    • {recipient.firstName}

    • {recipient.lastName}

    • {recipient.timezone}

    • {recipient.userName}

    • {vendor.name}

    • {buyer.name}

    • {jobs.count}

    • {job.number}

    • {jobs.newStatus}

    • {job.status}

    • {job.wordCount}

    • {project.id}

    • {project.internalId}

    • {project.client}

    • {project.domain}

    • {project.name}

    • {project.owner}

    • {project.owner.email}

    • {project.status}

    • {project.url}

    • {quote.confirmUrl}

    • {quote.price}

    • {quote.targetLang}

    • {automationWidget.submissionDate} | (previously: {instantQuote.submissionDate})

    • {automationWidget.quote} | (previously: {instantQuote.price})

    • {automationWidgetUser.email} | (previously: {instantQuoteUser.email})

    • {automationWidgetPage.id} | (previously: {instantQuotePage.id})

    • {automationWidgetPage.url} | (previously: {instantQuotePage.url})

    • {jobBoardPosting.title}

    • {jobBoardPosting.sourceLang}

    • {jobBoardPosting.targetLang}

    • {jobBoardPosting.wordsCount}

    • {jobBoardResponse.wordRate}

    • {jobBoardPosting.subject}

    • {jobBoardPosting.dateClosed}

    • {jobBoardPosting.dateDelivery}

    • {jobBoardPosting.url}

    • {jobBoardResponse.targetLang}

    • {jobBoardResponse.url}

    • {jobBoardResponse.name}

    • {jobBoardResponse.email}

    • {jobBoardResponse.total}

    • {jobBoardResponse.profileUrl}

    • {jobBoardResponse.note}

    • {job.previousWorkflow.dateDue}

    • {workflow.abbr}

    • {workflow.name}

    • {previousWorkflow.name}

    • {system.url.passwordReset}

    • {system.url}

    • Macros related to translation jobs:

      • {jobInfo}

      • File: {job.name}

      • Wordcount: {job.wordCount}

      • Language: {job.sourceLang} -> {job.targetLang}

      • Due: {job.dateDue}

      • {/jobInfo}

    • Macros related to Automation Widgets Default Project name:

    • Macros related to quotes:

      • {quote.id}

      • {quote.url}

      • {quote.status}

      • {quote.name}

    Was this article helpful?

    Sorry about that! In what way was it not helpful?

    The article didn’t address my problem.
    I couldn’t understand the article.
    The feature doesn’t do what I need.
    Other reason.

    Note that feedback is provided anonymously so we aren't able to reply to questions.
    If you'd like to ask a question you can leave a public comment below or Submit a request to our Support team.
    Thank you for your feedback.

    Comments

    0 comments

    Article is closed for comments.