Question: Default delivery method based on email address presence?

Hi folks,

Excitingly today is go live day for us at the National Museum of Rural Life! We're trying to find the best setup for the team here and hitting what feels to me like something that might be solvable and curious to hear what others do...

CURRENT SETUP

We have auto-attend ticked against the MOS as it's almost all in-person on-the-day sales and customers don't require a ticket after visiting the desk. The default delivery method is e-tickets, but if someone comes and doesn't give an email address, it becomes a bit of a faff to get auto-attend to work. The team use Quicksale primarily. Here are two solutions we're weighing up:

Solution 1

Create the order as usual

Go to order details

Change delivery method to HABO

Click print order

Check print tickets

Change to NULL printer

Press done

Solution 2

Add a fake email address to the constituents account so that the e-tickets do 'send' and therefore get auto-attended. From a user POV, much simpler, but from a data POV I do not like that one bit.

IDEAL SETUP

The delivery method defaults to HABO if the attached constituent doesn't have an email address, but is still e-tickets for those that do have email addresses. *crossing all my fingers this is a tickbox I haven't found*

What do others do in this situation?

Thanks!

Tom

Parents
  • Here is my 2 cents worth (not worth that much with today's inflation). We accomplish the same thing by training our staff to first choose the MOS before they do anything else. We have non-online MOS that do not default to PAH delivery. This will be especially important if you end up using Allocations, since they are assigned to MOS's. We have Member and Non-Member allocations. By training staff to always start with the MOS, this allows us to automate the Allocations and delivery methods.

Reply
  • Here is my 2 cents worth (not worth that much with today's inflation). We accomplish the same thing by training our staff to first choose the MOS before they do anything else. We have non-online MOS that do not default to PAH delivery. This will be especially important if you end up using Allocations, since they are assigned to MOS's. We have Member and Non-Member allocations. By training staff to always start with the MOS, this allows us to automate the Allocations and delivery methods.

Children
  • Hey Neil, thanks for your 2 cents (much better than none-cents!). That is a good idea. That would allow us to change the 'confirm mode' checkbox between the two MOS too so that removes the printing/acknowledgement clicks. And I think there's an argument for the default printer being NULL too rather than a BOCA. So all in all likely to just be a MOS switch! Will do some testing and see if it behaves as expected. Many thanks!