Skip to main content
Planview Customer Success Center

Email Template Variables

Introduction

Variables can be used in the email templates to link to ideas, users (first name, last name, username), communities, dates, etc. Supported variables appear at the bottom of each email template. Only the variables listed can be used in that template.

Variables use the format of ${variable}. When copying or typing variables, check the HTML source to ensure that no hidden HTML formatting appears between the brackets. The 83 variables are listed on the table below, followed by descriptions of the various Email Templates.

Variable Name Variable Value as used in a template Description Example value
LINK_TOKEN   $__link__  Full path link to an idea or other specific page http://acme.spigit.com/Page/ViewIdea?ideaid=1234
CLOSE_LINK_TOKEN   $__closelink__ Full path link to close an idea http://acme.spigit.com/Idea/CloseIdea?ideaid=1234
CLOSE_RELLINK_TOKEN   $__closerellink__ Relative link to close an idea /Idea/CloseIdea?ideaid=1234
RELATIVE_LINK_TOKEN   $__rellink__  Link relative to the current URL, does not include the website URL /Page/ViewIdea?ideaid=1234
FNAME_TOKEN   $__fname__ User's first name John
LNAME_TOKEN   $__lname__ User's last name Doe
FAX_TOKEN   $__fax__ User's Fax number 555-123-4567
MOBILE_TOKEN   $__mobile__ User's mobile number 555-987-6543
ADDRESS1_TOKEN   $__address1__ User's address line 1 123 Main st.
ADDRESS2_TOKEN   $__address2__ User's address line 2 PO Box 45
CITY_TOKEN   $__city__ User's city Anywhere
CITY_COMMA_TOKEN   $__citycomma__ User's city with a comma after it Anywhere,
STATE_TOKEN   $__state__ User's state ZZ
ZIP_TOKEN   $__zip__ User's zip code 11223
ZIP_COMMA_TOKEN   $__zipcomma__ User's zip code with a  comma after it 11223,
ZIP_HYPHEN_TOKEN   $__ziphyphen__ User's zip code with a hyphen after it 11223-
COUNTRY_TOKEN   $__country__ User's country US
WEBSITE_NAME_TOKEN   $__website_name__ User's website  http://www.johndoe.com
IM_NAME_TOKEN   $__im_name__ User's IM name john.doe
BIO_TOKEN   $__bio__ User's biography Info about me…
SIGNATURE_TOKEN   $__signature__ User's signature John Doe   555-987-6543
PROFILE_TAG_TOKEN   $__profile_tag__ User's profile This is John Doe
HOMETOWN_TOKEN   $__hometown__ User's hometown Anywhere
JOBTITLE_TOKEN   $__jobtitle__ User's job title Chief Ideator
COMPANY_TOKEN   $__company__ User's company name Acme
PHONE_TOKEN   $__phone__ User's phone number 555-192-8347
INVITER_TOKEN   $__inviter__ Name of the user triggering this email John Doe
MESSAGE_TOKEN   $__message__ Message user entered to be sent Check out my idea!
TITLE_TOKEN   $__title__ Title of the node, usually an idea but could blog entry or category Never mow the lawn again
USERNAME_TOKEN   $__username__ User's username john.doe
RECIPIENT_TOKEN   $__recipient__ Name of the person the message is being sent to Bob Smith
PASSWORD_TOKEN   $__password__ User's password p@55w0rd
PERMALINK_TOKEN   $__permalink__ relative permalink to the idea /permalink/Never_mow_the_lawn_again
APPLICATION_NAME_TOKEN   $__applicationname__ Company's name for the Spigit application ACME Idea Station
INFO_EMAIL_TOKEN   $__infoemail__ information email address info@spigit.com
WEBADMIN_EMAIL_TOKEN   $__webadminemail__ email address for the website administrator webadmin@spigit.com
APPLICATION_COMPANY_NAME_TOKEN   $__applicationcompanyname__ Name of the company who purchased the Spigit application ACME
COPYRIGHT_COMPANY_NAME_TOKEN   $__copyrightcompanyname__ Copyrighted name of the company ACME
WEBSITE_URL_TOKEN   $__website__ URL for the Spigit application website http://acme.spigit.com
EMAIL_TOKEN   $__email__ email address for the user john.doe@acme.com
RESOURCESERVER_URL_TOKEN   $__resourceserver__ URL for the resource server http://acme.spigit.com
SITETHEME_TOKEN   $__sitetheme__ name of the site theme Blue
STATUS_TOKEN   $__status__ Status of the node Approved
NODETITLE_TOKEN   $__nodetitle__ Title of the node, usually an idea but could blog entry or category Never mow the lawn again
IDEATITLE_TOKEN   $__ideatitle__ Title of the node, usually an idea but could blog entry or category Never mow the lawn again
NODECONTENT_TOKEN   $__nodecontent__ Content of the node With this new idea you'll never have to mow the lawn again….
NODEPARENTTITLE_TOKEN   $__nodeparenttitle__ Title of the node parent, usually a category or idea for comments Time saving ideas
NODETYPE_LABEL_TOKEN   $__nodetypelabel__ Type of the node, idea, review, comment, blog post etc. Idea
NODETYPE_LABEL_LOWER_TOKEN   $__nodetypelabellower__ Lower case version of the node type idea
INVITEE_TOKEN   $__invitee__ Name of person being invited to be a member of an idea Bob Smith
NODECREATOR_TOKEN   $__nodecreator__ Name of the creator of the node John Doe
SESSIONUSER_TOKEN   $__sessionuser__ Name of person logged in who generated this email John Doe
OWNER_TOKEN   $__nodecreator__ Name of the Owner of the node John Doe
NODEEDITOR_TOKEN   $__nodeeditor__ Name of the person who edited the node Bob Smith
NODEPARENTCREATOR_TOKEN   $__nodeparentcreator__ Name of the person who created the node parent John Doe
MAX_MEMBERS_TOKEN   $__maxmembers__ Max numbers of members a community can have 500
SITETYPE_TOKEN   $__sitetype__ Type of community it is Private - Members Only
IDEA_LABEL_TOKEN   $__idealabel__ What ideas are called on the site Idea
TOTAL_SPOCKS_TOKEN   $__totalspocks__ Spocks offered to a user to be a member of a idea 250
SPOCKS_LABEL_TOKEN   $__spockslabel__ Plural spocks label on the site Spocks
SPOCK_LABEL_TOKEN   $__spocklabel__ Singular spocks label on the site Spock
MY_SPIGIT_TOKEN   $__myspigit__ Name of user's profile page My Profile
TEAM_MEMBER_TOKEN   $__teammember__ Singular team member name Collaborator
TEAM_MEMBERS_TOKEN   $__teammembers__ Plural team members name Collaborators
PRICE_TOKEN   $__price__ Spock price of an idea 55.23
IDEA_STAGE_TOKEN   $__ideastage__ The stage of the idea Emergence
PREVIOUS_IDEA_STAGE_TOKEN   $__previousideastage__ The previous stage of the idea Incubation
CURRENT_STAGE_TOKEN   $__currentstage__ Redundant label for backward compatibility use IDEA_STAGE_TOKEN instead  
PREVIOUS_STAGE_TOKEN   $__previousstage__ Redundant label for backward compatibility use PREVIOUS_STAGE_TOKEN instead  
PREDICTION_INSTRUMENT_TOKEN   $__predictioninstrument__ URL to the prediction market trade shares page http://acme.spigit.com/PredictionMar...e/?instid=1234
PREDICTION_INSTRUMENT_PRICE_TOKEN   $__predictioninstrumentprice__ Price of a share on the prediction market 12.48
CATEGORY_FROM_TOKEN   $__category_from__ Name of the category the node moved from Other
CATEGORY_TO_TOKEN   $__category_to__ Name of the category the node moved to Time saving ideas
IDEA_WATCH_LINK_TOKEN   $__ideawatchlink__ URL to watch the idea http://acme.spigit.com/Idea/Subscribe?ideaid=1234
CATEGORY_WATCH_LINK_TOKEN   $__catwatchlink__ URL to watch the category http://acme.spgit.com/Core/Subscribe?nodeid=12
REASON_GIVEN_TOKEN   $__reasonGiven__ Description given for idea closing Idea was implemented
ORDER_DETAILS_TOKEN   $__order_details__ details of the order 1 Gift card at 5 spigits
QUANTITY_TOKEN   $__quantity__ Quantity of the item ordered 1
ITEM_NAME_TOKEN   $__item_name__ Name of the item Gift card
COST_TOKEN   $__cost__ Cost of the item 5
SPIGITS_TOKEN   $__spigits__ Label for spigits on the site spigits

 

Category: User Accounts

Email Template: Password Reset

Sent to: Member

Description: Email sent to users who requested that their password be reset.  The password will be randomly generated.

Editable Subject?: Yes

Variables - Body: ${website}, ${link}, ${sitetheme}, ${recipient}, ${username}, ${password}

Variables Subject:---

 

Email Template: Invitation for New Users to Sign Up (a.k.a. Register Invite Users)

Sent to: Requested member

Description: Email request for someone to join the website. This email is sent via the ‘Invite Users’ page in the Administration tab.

Editable Subject?: Yes

Variables - Body: ${website}, , ${link}, ${rellink}, ${sitetheme}, ${inviter}

Variables Subject: ${inviter}

 

Email Template: New User Welcome – User Added by Admin (a.k.a. Add User)

Sent to: New member

Description: Email notification that a user has been added to the website by an administrator. Default template includes the site URL, username and password for easy reference. Good opportunity to provide some initial “things you should do” steps.

Editable Subject? Yes

Variables - Body: ${username}, ${fname}, ${recipient}, ${lname}, ${password}

Variables Subject: ${website}

 

Email Template: Invitation to Join My Social Network (a.k.a. Invite Connection)

Sent to: Member

Description: Email request inviting a user as a connection. Found on my profile page.

Editable Subject?Yes

Variables - Body: ${website}, ${inviter}, ${link}, ${sitetheme}, ${rellink}

Variables Subject: ${inviter}

 

Category: Site Challenge

Email Template: Challenge Announcement

Sent to: Member

Description: Email notification of initial challenge phase starting. Note this email can be used to announce the beginning of the both the challenge and the initial challenge phase.

Editable Subject?: Yes

Variables - Body: ${challengetitle}, ${challengetitlelink}, ${challengequestion}, ${challengestartdate}, ${challengeenddate}, ${phasename}, ${phasedescription}, ${phasestartdate}, ${phaseenddate}, ${phaseactivities}, ${challengeideastotal}

Variables Subject: ${challengetitle}, ${challengetitlelink}, ${challengequestion},${challengestartdate},${challengeenddate}, ${phasename}, ${phasedescription}, ${phasestartdate}, ${phaseenddate}, ${phaseactivities}, ${challengeideastotal}

 

Email Template: Challenge Reminder

Sent to: Admin

Description: Email reminder of upcoming end of the last phase of a challenge. Note this email can be used as a reminder of the ending of the both the challenge and the last challenge phase.

Editable Subject? Yes

Variables - Body: ${challengetitle}, ${challengetitlelink}, ${challengequestion}, ${challengestartdate}, ${challengeenddate}, ${phasename}, ${phasedescription}, ${phasestartdate}, ${phaseenddate}, ${phaseactivities}, ${challengeideastotal}

Variables Subject: ${challengetitle}, ${challengetitlelink}, ${challengequestion}, ${challengestartdate}, ${challengeenddate}, ${phasename}, ${phasedescription}, ${phasestartdate}, ${phaseenddate}, ${phaseactivities}, ${challengeideastotal}

 

Category: Submitted Ideas

Email Template: Idea Submission to Admins

Sent to: Admin, Moderator and Experts by default (dpa configurable)

Description: Email notification that a new idea was posted to the community. Sent to all Admin roles.

Editable Subject?: No

Variables - Body: ${website}, ${link}, ${closelink}, ${resourceserver}, ${sitetheme}, ${rellink}, ${closerellink}, ${username}, ${nodetitle}, ${nodecontent} or ${nodesummary}, ${nodeparenttitle}, ${nodetypelabel}, ${nodetypelabellower}, ${message}, ${status}, ${nodecreator}, ${sessionuser}, ${nodeeditor}, ${nodeparentcreator}

Variables Subject: ${closerellink}, ${username}, ${nodetitle,} ${nodecontent}, ${nodeparenttitle}, ${nodetypelabel}, ${nodetypelabellower}, ${message} ,${status}, ${nodecreator}, ${sessionuser}, ${nodeeditor}, ${nodeparentcreator}

 

Email Template: Idea Submission Confirmation to Owner (a.k.a. Idea Submission to Owner)

Sent to: Idea Owner

Description: Confirmation email to owner that their idea was submitted to the category.

Editable Subject?: No

Variables - Body: ${website}, ${link}, ${closelink}, ${resourceserver}, ${sitetheme}, ${rellink}, ${closerellink}, ${username}, ${nodetitle}, ${nodecontent} or ${nodesummary}, ${nodeparenttitle}, ${nodetypelabel}, ${nodetypelabellower}, ${message}, ${status}, ${nodecreator}, ${sessionuser}, ${nodeeditor}, ${nodeparentcreator}

Variables Subject: ---

 

Email Template: Notice for Idea Posted via Email (a.k.a. Emails to Ideas)

Sent to: Community Admin, Idea Owner

Description: Confirmation email to admin and owners that an idea has been posted to the community via email.

Editable Subject?: No

Variables - Body: ${link}, ${nodetitle}, ${nodecontent} or ${nodesummary}

Variables Subject: ${nodetitle}

 

Category: Idea Generation 

Email Template: Idea Graduation Notice {Stage N} to {Stage N+1} (aka Idea Graduated)

Sent to: Idea Owner, Admin, Moderator and Experts by default (dpa configurable)

Description: Email notification to owner that their idea has graduated from one stage to another. Different email templates can be applied to each stage. Great opportunity to describe to the idea owner what’s next for their idea.

Editable Subject?: Yes – 1 only

Variables - Body: ${website}, ${link}, ${closelink}, ${resourceserver}, ${sitetheme}, ${rellink}, ${price}, ${ideastage}, ${spocklabel}, ${previousideastage}, ${nodecreator}, ${nodetitle}, ${ideatitle}, ${idealabel}, ${teammembers}, ${nodeeditor}, ${reasongiven}

Variables Subject: ${price}, ${ideastage}, ${spocklabel}, ${previousideastage}, ${nodecreator}, ${nodetitle}, ${ideatitle}, ${idealabel}, ${teammembers}, ${nodeeditor}, ${reasongiven}

 

Email Template: Expert Review Request

Sent to: Admin (editable)

Description: Email request sent to admins that an idea owner requests a formal review by an expert. The recipients of these emails can be changed from Admins.

Editable Subject?: No

Variables - Body: ${website}, ${link}, ${closelink}, ${resourceserver}, ${sitetheme}, ${rellink}, ${closerellink}, ${username}, ${nodetitle}, ${nodecontent} or ${nodesummary}, ${nodeparenttitle}, ${nodetypelabel}, ${nodetypelabellower}, ${message}, ${status}, ${nodecreator}, ${sessionuser}, ${nodeeditor}, ${nodeparentcreator}

Variables Subject: ${closerellink}, ${username}, ${nodetitle}, ${nodecontent}, ${nodeparenttitle}, ${nodetypelabel}, ${nodetypelabellower}, ${message}, ${status}, ${nodecreator}, ${sessionuser}, ${nodeeditor}, ${nodeparentcreator}

 

Category: Idea Closing

Email Template: Idea Closed Successfully Notice (a.k.a. Email body to be used when an Idea is closed Successfully)

Sent to: Idea Owner, Admin, Moderator and Experts by default (dpa configurable)

Description: Email notification to owner that their idea has been closed as successful.

Editable Subject?: Yes

Variables - Body: ${website}, ${link}, ${closelink}, ${resourceserver}, ${sitetheme}, ${rellink}, ${price}, ${ideastage}, ${spocklabel}, ${previousideastage}, ${nodecreator}, ${nodetitle}, ${ideatitle}, ${idealabel}, ${teammembers}, ${nodeeditor}, ${reasongiven}

Variables Subject: ${price}, ${ideastage}, ${spocklabel}, ${previousideastage}, ${nodecreator}, ${nodetitle}, ${ideatitle}, ${idealabel}, ${teammembers}, ${nodeeditor}, ${reasongiven}

 

Email Template: Idea Closed Unsuccessfully Notice (aka Email body to be used when an Idea is closed UnSuccessfully)

Sent to: Idea Owner, Admin, Moderator and Experts by default (dpa configurable)

Description: Email notification to owner that their idea has been closed as unsuccessful.

Editable Subject?: Yes

Variables - Body: ${website}, ${link}, ${closelink}, ${resourceserver}, ${sitetheme}, ${rellink}, ${price}, ${ideastage}, ${spocklabel}, ${previousideastage}, ${nodecreator}, ${nodetitle}, ${ideatitle}, ${idealabel}, ${teammembers}, ${nodeeditor}, ${reasongiven}

Variables Subject: ${price}, ${ideastage}, ${spocklabel}, ${previousideastage}, ${nodecreator}, ${nodetitle}, ${ideatitle}, ${idealabel}, ${teammembers}, ${nodeeditor}, ${reasongiven}

 

Email Template: Request to Close Idea as Successful (aka Idea Close Request)

Sent to: Admin

Description: Email request from owner to admin to close an idea as successful.

Editable Subject?: No

Variables - Body: ${website}, ${link}, ${closelink}, ${resourceserver}, ${sitetheme}, ${rellink}, ${closerellink}, ${username}, ${nodetitle}, ${nodecontent} or ${nodesummary}, ${nodeparenttitle}, ${nodetypelabel}, ${nodetypelabellower}, ${message}, ${status}, ${nodecreator}, ${sessionuser}, ${nodeeditor}, ${nodeparentcreator}

Variables Subject: ${closerellink}, ${username}, ${nodetitle}, ${nodecontent}, ${nodeparenttitle}, ${nodetypelabel}, ${nodetypelabellower}, ${message}, ${status}, ${nodecreator}, ${sessionuser}, ${nodeeditor}, ${nodeparentcreator}

 

Email Template: Request to Close Idea as Unsuccessful (a.k.a. Close Idea Request - Unsuccessful)

Sent to: Admin

Description: Email request from owner to admin to close an idea as unsuccessful.

Editable Subject?: No

Variables - Body: ${website}, ${link}, ${closelink}, ${resourceserver}, ${sitetheme}, ${rellink}, ${closerellink}, ${username}, ${nodetitle}, ${nodecontent} or ${nodesummary}, ${nodeparenttitle}, ${nodetypelabel}, ${nodetypelabellower}, ${message}, ${status}, ${nodecreator}, ${sessionuser}, ${nodeeditor}, ${nodeparentcreator}

Variables Subject: ${closerellink}, ${username}, ${nodetitle}, ${nodecontent}, ${nodeparenttitle}, ${nodetypelabel}, ${nodetypelabellower}, ${message}, ${status}, ${nodecreator}, ${sessionuser}, ${nodeeditor}, ${nodeparentcreator}

 

Category: Idea Expiration

Email Template: Idea Expiration Notice (a.k.a. Idea Expiry)

Sent to: Idea Owner

Description: : Email notification to owner that their idea has expired. Idea expiration periods per stage are managed on the Idea Management page under Administration.

Editable Subject?: No

Variables - Body: ${nodetitle}, ${link}, ${recipient}

Variables Subject: ${nodetitle}

 

Email Template: Idea Expires in {N} Days Notice (a.k.a. Idea Expiry Due From Today)

Sent to: Idea Owner

Description: Email notification that an owners idea will expire in {N} days.

Editable Subject?: No

Variables - Body: ${nodetitle}, ${link}, ${recipient}

Variables Subject: ${nodetitle}

 

Category: Content Operations

Email Template: Content Edited Notice (aka Node Edited)

Sent to: Post Owner

Description: Email sent to owner of idea, comment, blog, or review that was edited by someone else.

Editable Subject?: No

Variables Body: ${nodetypelabel}, ${link}, ${nodetitle}, ${nodeeditor}, ${reasongiven}

Variables Subject: ${nodetypelabel}, ${link}, ${nodetitle}

 

Email Template: Content Marked as Spam Notice (a.k.a. Node Marked as Spam)

Sent to: Admin, Moderator

Description: Email notification to admins and category moderators that an idea, comment, blog, or review was marked as spam.

Editable Subject?: Yes

Variables Body: ${nodetypelabel}, ${link}, ${nodetitle}

Variables Subject: ${nodetitle}, ${nodetitle}

 

Email Template: Idea Thread Approval

Sent to: Post Owner

Description: Email notification to owner that their idea after being moderated.

Editable Subject?: No

Variables Body: ${website}, ${link}, ${closelink}, ${resourceserver}, ${sitetheme}, ${rellink}, ${closerellink}, ${username}, ${nodetitle}, ${nodecontent} or ${nodesummary}, ${nodeparenttitle}, ${nodetypelabel}, ${nodetypelabellower}, ${message}, ${status}, ${nodecreator}, ${sessionuser}, ${nodeeditor}, ${nodeparentcreator}

Variables Subject: ${closerellink}, ${username}, ${nodetitle}, ${nodecontent}, ${nodeparenttitle}, ${nodetypelabel}, ${nodetypelabellower}, ${message}, ${status}, ${nodecreator}, ${sessionuser}, ${nodeeditor}, ${nodeparentcreator}

 

Email Template: Notice that Idea in Moderation Has Been Rejected (a.k.a. Node Rejected) 

Sent to: Post Owner

Description: Email notification to owner that their idea was rejected after being moderated.

Editable Subject?: No

Variables Body: ${closerellink}, ${username}, ${nodetitle}, ${nodecontent}, ${nodeparenttitle}, ${nodetypelabel}, ${nodetypelabellower}, ${message}, ${status}, ${nodecreator}, ${sessionuser}, ${nodeeditor}, ${nodeparentcreator}${website}, ${link}, ${closelink}, ${resourceserver}, ${sitetheme}, ${rellink}, ${closerellink}, ${username}, ${nodetitle}, ${nodecontent} or ${nodesummary}, ${nodeparenttitle}, ${nodetypelabel}, ${nodetypelabellower}, ${message}, ${status}, ${nodecreator}, ${sessionuser}, ${nodeeditor}, ${nodeparentcreator}

Variables Subject: ${closerellink}, ${username}, ${nodetitle}, ${nodecontent}, ${nodeparenttitle}, ${nodetypelabel}, ${nodetypelabellower}, ${message}, ${status}, ${nodecreator}, ${sessionuser}, ${nodeeditor}, ${nodeparentcreator}

 

Email Template: Idea Moved to Different Category Notice (a.k.a. Idea Moved To Another Category)

Sent to: Idea Owner

Description: Email notification to owner when an idea is moved from one category to another by someone else.

Editable Subject?: No

Variables Body: ${website}, ${link}, ${closelink}, ${resourceserver}, ${sitetheme}, ${rellink}, ${closerellink}, ${username}, ${nodetitle}, ${nodecontent} or ${nodesummary}, ${nodeparenttitle}, ${nodetypelabel}, ${nodetypelabellower}, ${message}, ${status}, ${nodecreator}, ${sessionuser}, ${nodeeditor}, ${nodeparentcreator}

Variables Subject: ${closerellink}, ${username}, ${nodetitle}, ${nodecontent}, ${nodeparenttitle}, ${nodetypelabel}, ${nodetypelabellower}, ${message}, ${status}, ${nodecreator}, ${sessionuser}, ${nodeeditor}, ${nodeparentcreator}

 

Category: Saved Searches

Email Template: Daily Saved Search Email (a.k.a. Saved Search Notification Daily)

Sent to: Member

Description: Email sent to users who have subscribed to saved search results on a daily basis.

Editable Subject?: No

Variables Body: ${message}

Variables Subject: ---

 

Email Template: Weekly Saved Search Email (a.k.a. Saved Search Notification Weekly)

Sent to: Member

Description: Email sent to users who have subscribed to saved search results on a weekly basis.

Editable Subject?: No

Variables Body: ${message}

Variables Subject: ---

 

Email Template: Notice for Idea Comment Posted via Email (a.k.a. Emails To Idea Comments)

Sent to: Member

Description: Email notification of a new comment posted via email, sent to anyone following a category or an individual idea.

Editable Subject?: No

Variables Body: ${link}, ${nodetitle}, ${nodecontent} or ${nodesummary}

Variables Subject: ${nodetitle}

 

Category: Purchase Operations

Email Template: Order Placed Notification – Administrator (a.k.a. "Order Placed" AdminEmail)

Sent to: Admin

Description: Email notification sent to administrator that a member has placed an order for an item in the store.

Editable Subject?: Yes

Variables Body: ${order_details}, ${username}

Variables Subject: ${order_details}, ${username}

 

Email Template: Order Placed Notification – Buyer (a.k.a. "Order Placed" Buyer Email)

Sent to: Buyer

Description: Email confirmation sent to member who has placed an order for an item in the store.

Editable Subject?: Yes

Variables Body: ${order_details}, ${username}

Variables Subject: ${order_details}, ${username}

 

Email Template: Order Canceled Notification (aka "Order Cancelled" Email)

Sent to: Buyer

Description: Email notification sent to buyer that their order has been canceled.

Editable Subject? Yes

Variables Body: ${username}, ${quantity}, ${item_name}, ${cost}, ${spigits}

Variables Subject: ${username}, ${quantity}, ${item_name}, ${cost}, ${spigits}

 

Email Template: Order Picked Up Notification (a.k.a. "Order Picked Up" Email)

Sent to: Buyer

Description: Email notification sent to buyer that their order has been picked up.

Editable Subject? Yes

Variables Body: ${username}, ${quantity}, ${item_name}

Variables Subject: ${username}, ${quantity}, ${item_name}

 

Email Template: Order Shipped Notification (a.k.a. "Order Shipped" Email)

Sent to: Buyer

Description: Email notification sent to buyer that their order has been shipped.

Editable Subject? Yes

Variables Body: ${username}, ${quantity}, ${item_name}

Variables Subject: ${username}, ${quantity}, ${item_name}

 

Email Template: Order Shipped Notification (a.k.a. "Order Shipped" Email)

Sent to: Buyer

Description: Email notification sent to buyer that their order has been shipped.

Editable Subject? Yes

Variables Body: ${username}, ${quantity}, ${item_name}

Variables Subject: ${username}, ${quantity}, ${item_name}

 

Category: Pairwise

Email Template: Pairwise email notice

Sent to: Member

Description: Email notice with list of stages if pairwise voting configuration has a start date defined with the notification by email option enabled.

Editable Subject? Yes

Variables Body: ---

Variables Subject: ${__stages__}