Engaging customers via their mobile devices is an exciting proposition for many organizations; however, it has to be done with care. These solutions often carry a significant cost and depend on a Return on Investment (ROI) model to make sense.
Achieving this ROI requires walking a fine line between meaningful engagement and being a nuisance. Here are five best practices to help you do that.
5 ways to ensure your mobile strategy works
1. Think big picture
The goal is to create a user experience that provides vast amounts of data to the organization while delivering value to the customer. Accomplishing that means the experience needs to be immersive and omni-channel (e.g., SMS, email, app-based, digital signage, direct mail, etc.).
Too many organizations jump straight to the mobile application without realizing adoption of mobile applications is low and retention of those mobile apps is even lower. A holistic approach that embraces the web (traditional and mobile), mobile apps, digital and physical signage, and some of the emerging areas such as augmented reality (AR) and context-aware chatbots will be far more successful.
Analytics and business intelligence tools must be included because understanding the success of these messages and their impact on the bottom line is a necessity, as engagement attempts that are ill-received may create a negative effect on the business.
2. Establish a baseline
Before rolling out any new engagement solution or even a single targeted campaign, it is important to understand the baseline. What is normal for a specific time of day, day of week, demographic, location, etc.
If there are areas in which these baselines are unknown, the success of an engagement will also likely be unknown. The length of time to determine a credible baseline depends on business and vertical; however, a month of data will provide statistically valuable data for many organizations.
3. Consider your social credibility
Each engagement or touchpoint with the user must be carefully weighed prior to being implemented, as the organization is spending “social credibility" with the customer in issuing these engagements. Determining that a message is hitting the right person at the right time and place is paramount to success.
While the organization may want to drive a specific behavior, it must be done in such a way that it is graciously accepted by the recipient. For less important messages, consider other channels for delivery—email, direct mail and digital signage integrations are options that are less invasive than a targeted push message.
4. Leverage employee engagement
Business should ensure the human component isn’t lost in this digital marketing frenzy.
Consider a scenario in which an employee could be notified when a user has spent more than five minutes in front of a specific retail display or there has been a high density of users in line for a drink at a sports game or concert venue. Rather than trying to ping users to have them go find another bar, consider triggers that have an employee come over with a mobile payment system and perform line-breaking transactions. This human component may still be considered a “digital engagement," but it won’t feel like it to the consumer.
5. Keep it fresh
Digital engagements should always be timely and relevant. Organizations can’t afford to be lazy about managing these platforms because pushing irrelevant messages will drive away customers, cause them to remove their mobile apps, and even consider competitors.
Campaigns should also create a sense of urgency—create a fear of missing out or at least ensure customers understand this immediate deal is good for only the first 100 redemptions.
Gamification is one way to keep things interesting for consumers, and it can drive additional spend as it may promise “bonus" rewards for the additional engagement. The solutions should be simple enough that they can be managed by marketing teams and not IT.
Originally posted here with Network World. Republished with permission as originating author. Also available on my LinkedIn page.
- Strive for a Single Source of Truth—As an administrator there should be a single place that you manage information about a specific set of users or devices (e.g. Active Directory as the only user database). Everything else on the network should reference that source for its specific information. Multiple domains or maintaining a mix of LDAP and RADIUS users makes authentication complicated and arguably may make your organization less secure as maintaining these multiple sources is burdensome. Invest in doing one right and exclusively.
- Standardization—A tremendous amount of time savings can be found by eliminating one-off configurations/sites, situations, etc. An often overlooked part in this time savings is in consulting and contractor costs, the easier it is for an internal team to quickly identify a location, IDF, device, etc. the easier it will be for your hired guns as well. A system should be in place for IP address schemes, VLAN numbering, naming conventions, low voltage cabling, switch port usage, redundancy, etc.
- Configuration Management—Creating a plan for standardization is one thing, ensuring it gets executed is tougher. There are numerous tools that allow for template-based configuration or script-based configuration. If your organization is going to take the time to standardize the network, it is critical that it gets followed through on the configuration side. DevOps environments may turn to products like Chef, Puppet or Ansible to help with this sort of management.
- Auditing and Accountability—Being proactive about policing these efforts is important and to do that some sort of accountability needs to be in place. This should happen in change control meetings to ensure changes are well thought out and meet the design standards, safeguards are in place to ensure the right people are making the changes and that those changes can be tracked back to a specific person (no shared “admin" or “root" accounts!) to help ensure that all of the hard work put in to this point is actually maintained. New hires should be trained and indoctrinated in the system to ensure that they follow the process.
- Determine What is Important—What is most important to your organization is likely different than that of your peers at other organizations, albeit somewhat similar in certain regards. Monitoring everything isn’t realistic and may not even be valuable if nothing is done with the data that is being collected. Zero in on the key metrics that define success and determine how to best monitor those.
- Break it Down into Manageable Pieces—Once you’ve determined what is important to the business, break that down into more manageable portions. For example if blazing fast website performance is needed for an eCommerce site, consider dividing this into network, server, services, and application monitoring components.
- Maintain an Open System—There is nothing worse than being locked into a solution that is inflexible. Leveraging APIs that can tie disparate systems together is critical in today’s IT environments. Strive for a single source of truth for each of your components and exchange that information via vendor integrations or APIs to make the system better as a whole.
- Invest in Understanding the Reporting—Make the tools work for you, a dashboard is simply not enough. Most of the enterprise tools out there today offer robust reporting capabilities, however these often go unimplemented.
- Review, Revise, Repeat—Monitoring is rarely a “set and forget" item, it should be in a constant state of improvement, integration, and evaluation to enable better visibility into the environment and the ability to deliver on key business values.