Naming Convention
CLIENT NAME _ Participant Comms _ Project Name (if customised) / GENERIC_DATE / Version number
Richardson Banner
<img src="https://cdn2.hubspot.net/hubfs/468013/RICHARDSON_HORIZONTAL_4C_LOGO_2016-1.png" alt="Richardson Sales Training Logo" height="50" width="300" />
Metatags:
EMAIL RECIPIENT = <~recipient given name~>
JOB HOLDER FIRST NAME = <~job holder given name~>
JOB HOLDER SURNAME = <~job holder family name~>
USERNAME = <~username~>
PASSWORD = <~password~>
COMPLETION DATE/ CLOSE DATE = <~project close date~> -- Use for V3
Formatting code
<br /> <br/> (use at the end of a sentence)
<b> XXXX </b> (used to bold XXX text)
Guidelines for setting up Participant Comms
- Metatags will not pull in the subject line
- Use metatags and keep the communication as general as possible in relation to specific program names.
- Please use the following naming convention for the file;
CLIENT NAME _ Participant Comms _ Project Name (if customised) / GENERIC_DATE / Version number
- Please DO NOT put hard coded dates in to any participant communications.
- Always contact [email protected] if unsure of email comms
- Avoid using specific Project Names where possible (please include this within the Communication Name if unavoidable