Support

January 25, 2016 at 4:06 am

Hi Nick,

The newsletter message type is a ‘contact’ based messenger. Meaning when you select the registrations your sending the newsletter to it loops through and grabs all the contacts for those registrations to send the message to.

At the point in which the newsletter message is sent the messenger does not know which registration (or event) that message is sent for, it only has access to the ‘contact’. So the problem is that [RECIPIENT_TICKET_URL] is pulling the link in from the contact and using the first link it finds. In the case of contacts with multiple registrations they are being sent the wrong link as a single contact can be assigned to multiple registrations.

Due to messenger being based on contacts there is no way to reliably pull in the correct registration based information such as [RECIPIENT_TICKET_URL] when multiple registrations are assigned to a single contact and that shortcode will likely be removed from the message type until we can find a better solution.

To send the users the [RECIPIENT_TICKET_URL] you could use the re-send ticket notice action within the registrations view – http://take.ms/0r39a

You can assign a custom message template to that messenger so that you can include custom information within that message however there is no option to ‘bulk send’ that message like the newsletter message type so each user would need the message manually triggered.

January 27, 2016 at 1:54 pm

Hi Nick,

We appreciate your suggestion.

January 28, 2016 at 1:51 pm

Hi Nick,

Do you use the Multi Event Registration Add-on (MER)?

Do you allow more than one ticket to be purchased at once? Meaning a user could have input their details for more than one ticket in a single registration?

Those steps above will work if not user MER but if users have registered with the same details for multiple tickets you would be better using the [TXN_TICKETS_APPROVED_URL] shortcode which shows ALL of the approved tickets on a transaction. If this is a single ticket they see the one ticket, if they have registered with the same details across multiple tickets, they see all the tickets…. however if they have registered on multiple tickets, each with their own details all registrants links will open the link to see all tickets for that group.

You will also want to disable the Event Admin context on the custom template by setting the TO field to nothing and saving that context, otherwise the admin will also receive multiple reg approved messages.

January 28, 2016 at 3:48 pm

Yes you can use the above with the note about [TXN_TICKETS_APPROVED_URL]

I would that that shortcode and send all tickets to all registrations (or only select the primary registrations) as then at least all the tickets are sent to at least 1 registrant (if not all registrants) in a group.

January 29, 2016 at 2:06 am

I need to send tickets to all registrants, so will the [TXN_TICKETS_APPROVED_URL] shortcode work for all tickets, including tickets for which payment is still due?

If you are selecting all registrations and using approve and notify, you’ll be approving all the registrations that your send a message to.

[TXN_TICKETS_APPROVED_URL] sends a link that will display all tickets for Approved registrations (regardless of payment status) if you have a group of 5 registrations in the same group 3 reg approved and 2 pending payment the link opens 3 tickets. It is the registration status that determines this, not payment status)

But if your selecting all 5 and then clicking Approve and notify, your Approving all 5 before sending the notification, so the link will open all 5 tickets.

There is also [TXN_TICKETS_URL] which sends a link for all ticket regardless of registration status. So if you have a group of 5 registrations, 3 registrations approved and 2 pending payment (in the same group) the link opens all 5.

Use this if you want to be really sure that ALL ticket are available.

And if you could just confirm that the ‘Approve and Notify Registrants’ option corresponds with the Registration Approved message I’d be grateful. It sounds like it from what you have said, but I just want to be sure.

Yes it does correspond to the Registration Approved message template.

What that option does it switch any registrations select to have a status of Approved. If the ‘notify’ option is set, it also sends the related messages for that new status (Reg Approved)

One issue is that it you have unpaid registrations that your sending the tickets to and to send the tickets you are approving the registration which basically tells EE ‘I don’t care about payment status, this attendee is going to the event’. Is that expected?

If your scanning the tickets and not using Continuious mode you will see the payment status before you click check-in, but if using continuous mode the attendee with an Approved ticket but incomplete payment will be checked in as normal.

January 29, 2016 at 3:54 am

Thanks Tony. This is getting quite in depth!

Yeah its not a simple solution because of the many different registration setups that are possible and the many different way in which users want to use/send information.

1. I would like each registrant to get a single email with a link to just their ticket (i.e. it would take them to the same URL that the ticket link in the admin registration list view goes to). So it sounds like I should be using the [TXN_TICKETS_URL] for this. Correct?

No.

[TXN_TICKETS_URL] & [TXN_TICKETS_APPROVED_URL] send a link to ALL of the tickets assigned to a transactions. If you have multiple registrations on a single transaction (a group booking where they have selected multiple tickets) then ALL of the recipients that receive an email will receive ALL of the tickets.

Also, when using the ‘Approve and Notify’ method (still not sure I will be using this method due to it changing the status of registrations), do all registrants in a group booking get an email, or just the primary registrant?

This is where it gets tricky. If a user has used the same details across multiple tickets, they will receive a single email. EE is designed to try and reduce the amount of ‘duplicate’ emails (they aren’t actually duplicates but we received a lot of feedback that user wanted the emails reduced) so it checks if the registrations are all assigned to the same contact and only sends a single email.

If they didn’t use the same details, each registration gets an email.

2. There will not be any group registrations where some people have paid and some not. Either we have a payment for an individual/group booking or we don’t.

Then it depends what you want to use. [TXN_TICKETS_URL] sends all the tickets for all registrations in a group, regardless of payment status.

3. I think I will be using Lookup Attendee mode when scanning people in to the conference, though I am not yet sure about this, as we have a lot of people to scan in an relatively short space of time, so perhaps Continuous Scanning would work better… [I will be getting on to testing out the modes once I have sent out the ticket links today]

Lookup mode adds an additional step in that it loads up the information for the attendee for you to review, you’ll need this if you approve all your registrations.

I think I don’t fully understand the different statuses of registrations. Am I right in thinking that there are two aspects to the status? At the moment all of my registrations appear to be either:

There’s actually more.

A registration can have a status of Approved, Pending Payment, Incomplete, Not Approved, Declined & Cancelled.

Ever registration is assigned to a transaction… a transaction is a place to store the payments for a single or group registration.

The registration status can be set independently of the transaction status but EE automatically updates the registration status when it make sense to do so, for example if a user applies a payment for the full amount of the transaction, the transaction is complete… EE updates the registrations on that transaction to Approved.

Approved (and only approved) registrations apply to the events sold limits.

I want to be able to keep this status if possible, or at least I want those people at the registration desk to be able to clearly and quickly tell the status of the registration.

Then do not select Pending Payment registrations and Approve them to send the registration approve message, this forces you to check EVERY ticket using lookup to confirm that the Transaction has been complete – http://take.ms/Cm3nc

Continuous mode will just check the user in without showing you any details.

January 29, 2016 at 5:19 am

The shortcode I used previously (with the newsletter) was [RECIPIENT_TICKET_URL] and I think it is the link generated by this shortcode that gives each registrant (whether primary or additional) a link to their own individual ticket. Is this correct?

Yes, it does.

1. Create a custom ‘Registration Approved’ message (including the [RECIPIENT_TICKET_URL] shorcode) and link this to the event.
2. Select all approved registrations in the admin list view and then select ‘Approve and Notify Registrations’.

Yes…. but, you have a problem here if 1 user purchased multiple tickets and the registrations are all under 1 contact (all used the same details)

Only the Primary Registrant will receive an email, so [RECIPIENT_TICKET_URL] will parse to the ticket for that single primary registrant and not the full group.

1. Create a custom ‘Registration Pending Payment’ message (including the [RECIPIENT_TICKET_URL] shorcode) and link this to the event.
2. Select all pending payment registrations in the admin list view and then select ‘Set Registrations to Pending Payment and Notify’

Yes again. However the above concerning multiple registrations still applied.

This is why I ended up suggesting [TXN_TICKETS_URL] & [TXN_TICKETS_APPROVED_URL]

To give working example, take a look at this registration list – http://take.ms/pzQK5

Select all registration and do Approve and notify – http://take.ms/acaCS

Your expecting 3 emails, only 2 will be sent – http://take.ms/tQxp2

This only happens if the registration is using the same contact, IE either you do not request information for additional registrations or the user inpur the same details across all requested info anyway.

January 29, 2016 at 6:01 am

Yes, I can’t see any reason why not 🙂

January 29, 2016 at 6:39 am

Yeah that’s a good point, I’d missed that!

Hmm, do you have many pending payment registrations?

I’m thinking the way to work with those is to use the resend ticket notice button on those registrations.

January 29, 2016 at 7:08 am

So this way I would create a custom template for the ‘Ticket Notice’ message, link this to the event, and then manually email each of those with payment pending status using the ‘Resend Ticket Notice’ option next to their registration in the admin list view?

Yes, after you have set the custom ticket notice message, refresh the Registration list page before clicking re-sending.

If this is the most reliable way of getting a ticket to everyone, I will do this, but I hope in the future there will be a simpler way!

It is the most reliable way currently.

I have created a ticket to see what we can do to make this easier in future versions.