You can include individual attendee booking information by adding content to your trigger emails in the form of 'regions'.
Please see the attached notebook text, which includes the booking information that is available to you to pull through into the content of your trigger email. All you have to do is copy from the notepad text the required information and paste this into the trigger email wysiwyg editing box.
You must ensure that the string of code starts with:
{STARTREGION:Attendee}
and ends with
{ENDREGION:Attendee}
It is also worth thinking about the wording that introduces this string of information, for example if you include the line
'Below is the details of all attendees within your booking:'
and there are no other attendees, nothing will pull through and there will be just an empty gap in the email.
It is definitely advisable that you carry out a few tests amongst your team to ensure you get the desired information and format.
*** Attendee Regions ***
Below is the details of all attendees within your booking:
{STARTREGION:Attendee}
{Attendee full name}
{Attendee title}
{Attendee forename}
{Attendee surname}
{Attendee reference}
{Attendee organisation}
{Attendee occupation}
{Attendee email}
{Attendee telephone}
{Attendee address 1}
{Attendee address 2}
{Attendee address 3}
{Attendee address town}
{Attendee address county}
{Attendee address postcode}
{Attendee address country}
{Attendee type}
{Attendee ticket type}
{Attendee custom field[customFieldId]:Custom field name} e.g. {Attendee custom field[1]:What is your job title?} note: the custom field name is to make the tag more readable, and doesn't need to exactly match the actual custom field name
{Attendee global custom field[globalCustomFieldId]:Global custom field name} as above but uses global custom field details
{ENDREGION:Attendee}
Would become...
Below is the details of all attendees within your booking:
Mr Symphony Test
Mr
Symphony
Test
A001
Quba
Developer
test@symphonyem.co.uk
0114 2797779
Quba New Media
Belgravia House
115 Rockingham Street
Sheffield
South Yorkshire
S1 4EB
UK
Attendee Type
Ticket Type
Google
Some global custom field value
Mr Richard Pursehouse
Mr
Richard
Pursehouse
A002
Quba
Developer
rpursehouse@symphonyem.co.uk
0114 2797779
Quba New Media
Belgravia House
115 Rockingham Street
Sheffield
South Yorkshire
S1 4EB
UK
Attendee Type
Ticket Type
Newspaper
Some different global custom field value
*** Days Attending Regions ***
Must occur within an attendee region.
{STARTREGION:DaysAttending}
{Date}
{ENDREGION:DaysAttending}
So we could write this like:
{STARTREGION:Attendee}
{Attendee full name} is attending the following days:
{STARTREGION:DaysAttending}
{Date}
{ENDREGION:DaysAttending}
{ENDREGION:Attendee}
Would become...
Mr Symphony test is attending the following days:
16/06/2011
17/06/2011
18/06/2011
Mr Richard Pursehouse is attending the following days:
16/06/2011
17/06/2011
*** Session Signup Regions ***
Must occur within an attendee region.
{STARTREGION:SessionSignup}
{Session name}
{Cost}
{IsAllocated}
{Date}
{Start time}
{End time}
{ENDREGION:SessionSignup}
So we could write this like:
{STARTREGION:Attendee}
{Attendee full name} has the following session signups:
{STARTREGION:SessionSignup}
{Session name} ({Cost}) on {Date} at {Start time} - {End time}. Allocated = {IsAllocated}.
{ENDREGION:SessionSignup}
{ENDREGION:Attendee}
Would become...
Mr Symphony Test has the following session signups:
A session (£10.00) on 16/06/2011 at 13:00 - 14:00. Allocated = true.
A different session (£0.00) on 17/06/2011 at 15:00 - 16:00. Allocated = false.
Mr Richard Pursehouse has the following session signups:
A different session (£0.00) on 17/06/2011 at 15:00 - 16:00. Allocated = true.
*** Reservation Regions ***
Must occur within an attendee region.
{STARTREGION:Reservation}
{Hotel}
{Cost}
{Room type}
{Night}
{ENDREGION:Reservation}
So we could write this like:
{STARTREGION:Attendee}
{Attendee full name} has the following hotel reservations:
{STARTREGION:Reservation}
{Hotel} in a {Room type} on {Night} at a cost of {Cost}.
{ENDREGION:Reservation}
{ENDREGION:Attendee}
Would become...
Mr Symphony Test has the following hotel reservations:
Posh hotel in a double room on 16/0/6/2011 at a cost of £100.00.
Even more expensive hotel in a king size room on 17/06/2011 at a cost of £200.00.
Mr Richard Pursehouse has the following hotel reservations:
Shack in a single room on 18/06/2011 at a cost of £0.00
*** Custom Field Regions ***
Must occur within an attendee region.
Note how this differs from the other custom field merge tag. Since this is a custom field region,
it will return all custom field names and values rather than a specific custom field value as mentioned
earlier in the attendee regions.
{STARTREGION:CustomField}
{Custom field name}
{Value}
{ENDREGION:CustomField}
So we could write this like:
{STARTREGION:Attendee}
{Attendee full name} entered the following details:
{STARTREGION:CustomField}
{Custom field name}: {Value}
{ENDREGION:CustomField}
{ENDREGION:Attendee}
Would become...
Mr Symphony Test entered the following details:
How did you hear?: Google
Gender: Male
Place of Birth: London
Mr Richard Pursehouse entered the following details:
How did you hear?: Newspaper
Gender: Male
Place of Birth: Sheffield
0 Comments