Enhancing user engagement with your mobile wallet passes can be as simple as setting up location-based lock screen messages. These messages pop up on a user's lock screen when they are in proximity to a specified location, providing timely and relevant notifications.
What Are Location-Based Lock Screen Messages?
Location-based lock screen messages are notifications that appear on the mobile device's lock screen triggered by the user's geographical position. They rely on geofencing technology to deliver personalized communication when users are near a particular venue or store.
Benefits of Location-Based Messaging
Timely Engagement: Reach out to pass holders at the moment when they're most likely to visit your store.
Increased Foot Traffic: Prompt reminders can entice pass holders to enter your establishment when they're nearby.
Personalized Experience: Tailor messages based on location to create a more personalized customer experience.
How to Set Up Location-Based Messages:
Determine Your Target Locations: Identify the physical locations where you want to trigger lock screen messages. This could be your store, an event venue, or other relevant areas.
Navigate to the Pass Editor page
Click the "Features Tab"
"Add Location"
Enter the address, and if necessary drag the pin to specify the exact location
Set your message
Craft Your Messages:
Write clear, concise messages that will appear on users' lock screens. Ensure they are compelling and offer value to encourage users to act.
Best Practices for Location-Based Lock Screen Messages:
Clarity is Key: Keep messages short and to the point to quickly convey the value proposition.
Value-Driven Content: Offer discounts, reminders, or other benefits to the user for being in the vicinity of your location.
Frequency Management: Avoid overwhelming users by limiting the number of times a message is triggered.
By leveraging location-based lock screen messages, you create another touchpoint with your pass holders, driving engagement, and potentially, sales. Ensure you respect user privacy while implementing this feature.