TRBO Feedback - Pros & Cons?

Hi Jessica,

We're using TRBO for sales at a seasonal satellite location, line-busting, and (starting this year) roving sales. So far, we've had a pretty positive experience.

Staff find it very easy to use, since the devices are standard Android tablets and anyone that has used QuickSale is familiar with the button layout in TRBO. We're using 2 Motorola ET1s (replaced by the ET50/55) and a Galaxy Tab 4. The ET1s are used for roving staff and the Galaxy Tab 4 for the satellite location (since it lives on a desk and doesn't need to be rugged). We're also using Zebra iMZ220 printers for receipts and tickets, in addition to the built-in email functionality.

About the email functionality - you do not need a ticket printer to use TRBO. In fact, the default option is to email tickets and receipts. This can be accomplished via TRBO-specific designs that are simplified text-and-QR-code-only templates OR by using a PAH delivery method to access your normal PAH templates. The TRBO templates work for both General Public and constituent sales while the PAH option only works for constituent sales. In both cases, the guest either selects or enters their email address as they are checking out on the tablet (while your staff will do 95% of the work, the customer does need to sign and select/type in their email).

I personally have only two problems with TRBO:

1. You need very stable WiFi and an excellent signal to run at a decent clip. Maybe WAN/LTE is an option, but I'm not sure how that would work configuration-wise (or if it's even an option).

2. If you're using source codes to manage discounts, it's very cumbersome to switch sources. So much so that we direct customers with discounts to purchase from the ticket windows rather than TRBO.

Let me know if you have any other questions about TRBO and I'd be happy to answer them, if I can!

- Justin

Hi Jessica,

We're using TRBO for sales at a seasonal satellite location, line-busting, and (starting this year) roving sales. So far, we've had a pretty positive experience.

Staff find it very easy to use, since the devices are standard Android tablets and anyone that has used QuickSale is familiar with the button layout in TRBO. We're using 2 Motorola ET1s (replaced by the ET50/55) and a Galaxy Tab 4. The ET1s are used for roving staff and the Galaxy Tab 4 for the satellite location (since it lives on a desk and doesn't need to be rugged). We're also using Zebra iMZ220 printers for receipts and tickets, in addition to the built-in email functionality.

About the email functionality - you do not need a ticket printer to use TRBO. In fact, the default option is to email tickets and receipts. This can be accomplished via TRBO-specific designs that are simplified text-and-QR-code-only templates OR by using a PAH delivery method to access your normal PAH templates. The TRBO templates work for both General Public and constituent sales while the PAH option only works for constituent sales. In both cases, the guest either selects or enters their email address as they are checking out on the tablet (while your staff will do 95% of the work, the customer does need to sign and select/type in their email).

I personally have only two problems with TRBO:

1. You need very stable WiFi and an excellent signal to run at a decent clip. Maybe WAN/LTE is an option, but I'm not sure how that would work configuration-wise (or if it's even an option).

2. If you're using source codes to manage discounts, it's very cumbersome to switch sources. So much so that we direct customers with discounts to purchase from the ticket windows rather than TRBO.

Let me know if you have any other questions about TRBO and I'd be happy to answer them, if I can!

- Justin