Data-driven review collecting: ask about the service they actually bought

Why does asking about the service beat a generic ask?

A generic request is easy to ignore because it is about nobody in particular. A request that names the service the customer paid for speaks to a specific experience, and it arrives when you decide, anywhere from 1 hour to 24 hours after the visit.

Because the request is only sent when a product is picked at the scan, it goes to customers who actually bought something on that visit.

• A message that names the service picked at the scan
• A delay you choose: 1, 2, 3, 4, 6, 12, or 24 hours
• A short message of up to 30 characters, readable on the lock screen
• The review link is shown on the card in Apple Wallet and Google Wallet

Will review requests annoy your customers?

BTAQA sends at most one review request per customer per day, even if they visit twice. Requests only go to customers who gave marketing consent when they joined the card.

Review requests are off by default. They only run after you turn them on and write your own message, so BTAQA never sends text you did not write.

How do you write a message that fits every service in 30 characters?

The message is short because it is read on the lock screen, and the {product} token takes part of it. Write a sentence that works for every name on your list: "How was your {product}?" reads well for a latte, a full wash at a car wash and a beard trim alike.

If staff pick more than one service on a visit, each one is recorded in your sales, but the request names only one of them. Keep the wording general enough that it reads naturally with any service.

Before you save, read the message with your longest item name in place of the token. If your list has "Pedicure with foot massage", shorten it in the list itself to "Pedicure". A short name reads more clearly on the lock screen, and staff spot it faster in the scanner app.

• "How was your {product}?"
• "Enjoy your {product}? Rate us"
• "Rate your {product} today"

What has to be in place for the request to arrive?

Every request passes four checks before it is scheduled: a review link on the card, a Review Request switched on with a message you wrote, an item picked by staff on the visit, and a customer who gave marketing consent. The switch stays locked until you add the link; in its place you see a notice and a Go to Step 3 to add link button.

Once the delay is up, BTAQA picks the request up within minutes and sends it to the customer's card in Apple Wallet or Google Wallet. If the card is not in the customer's wallet, the request is skipped and not counted as sent. On Google Wallet the notification shows the title "Thanks for visiting" with your message underneath. The default delay is 1 hour, and a customer never gets more than one request a day: if they visit in the morning and again in the evening, the first visit's request is the only one.

Settings are per card: if you run one card for your car wash and another for a detailing service, each one has its own message and delay.

How does the review request fit with the rest of BTAQA?

The request works wherever the item is recorded. Whether staff add the stamp in the scanner app, you add it from the Customers page of the dashboard, or staff add points on a points card with an item picked, the request is scheduled under the same rules.

Before any later visit, the review redirect after card install catches the customer even earlier: when they return to the join page after adding the card, they go straight to your review page. That feature is on all three plans, so you can collect reviews on Connect too.

The review request sits in the same Auto Notifications tab as the Welcome Message, We Miss You and the Birthday Greeting, so you manage your automated messages in one place. To compare what each plan includes, see pricing.