Users are going mobile more than ever before. They are registering for services on mobile devices and replacing browsers with apps to log into mail, get news, and share updates. Yet, the current mobile browser or app registration process is stuck in the desktop computer era.
This presentation will show you:
— Workflows to speed up and simplify mobile registrations
— Tactics to block fake users
— UX/UI best practices for mobile registration
— Tips on user account protection
3. Agenda
•
The Impact of Mobile Identity
•
Mobile Browser and App Registration
•
Mobile Identity in Action
•
Checklist for Mobile Registration Rollout
3
4. Registration
User Experience
•
•
•
•
Too much typing
Too many screens
Abandonment
Email verification takes you
out of the interface
Security
•
•
•
•
No info about the user
Fake accounts
Spam and fraud
Vulnerable accounts
4
5. Mobile Identity = Mobile Phone Number
A mobile number is the only truly unique and
readily verifiable form of online identity.
5
7. Account Registration
We need your mobile
number to verify your
account, but don’t
worry we won’t spam
you.
}
Tell the user why you need their phone number
7
8. Account Registration
PhoneID Data
Assesses the risk of a phone number
associated with an account registration or
transaction.
Phone Number
Phone Type
}
Confirm the user’s phone number
415 XXX XXXX
MOBILE
Risk
recommendation
Allow
Score
1
Risk Level
Low
Score Recommendations
Score
Risk Level
Recommendation
801-1000
High
Block
601-800
Medium-high
Block
401-600
Medium
Flag
201-400
Medium-low
Allow
Low
Allow
Neutral
N/A
0-200
N/A
8
9. Account Registration
}
Include the 4-6 digit code and
your brand name in the text.
Offer as many language
options as your use’s speak.
Ask user to enter the
code
}
Set expectations and provide
the option to re-send the
code
Offer users a voice option
}
}
9
12. Mobile Identity in Action
User
Registration
(415) 877 – 3727
Account
Alert
User Adds
New Device
Feb
Jan
July
April
Password
Reset
Dec
Aug
Suspicious
Login Location
User
Engagement
12
13. Checklist
SMS and Voice Provider
•
•
•
Support Services
•
•
•
Global connections and route failovers
Phone number cleansing
Message encoding for all languages &
dialects
UI/UX best practices
24x7 technical support included
Reporting and dashboards
Phone Number Data
Other Advice
•
•
•
•
•
•
Phone type and carrier
Risk level and recommendation
Name and address
User education
Provide a voice option
Link mobile and desktop accounts
13
14. CONTACT
Darren Berkovitz | VP, and Co-founder
direct:
+1 310 740 9709
mobile: +1 818 620 1074
email:
darrenb@telesign.com
TeleSign USA Headquarters
4136 Del Rey Av | Marina del Rey, CA 90202
+1 310 740 9700 | 1 800 850 3485
TeleSign EMEA
2nd Floor Kingsgate House | 115 High Holborn
London, WC1V 6JJ | United Kingdom
+44 (0) 330 808 0081
16. Phone Number Cleansing
Corrects improperly formatted phone numbers to
adhere to international dialing standards. It can
recover phone numbers that are undialable,
increasing deliverability and call completion.
Deliverability
•
Improves deliverability by 10%
in average.
International Standards
Examples
Original
Complete Phone Number
5266418866XX
Country Code
52
Phone Number
66418866XX
Cleansing – Call & SMS
Country Code
52
Phone Number
•
11
Min Length
•
Brazil added a “9” to their
numbering plan in most
cities – but not all
Argentina adds the prefix
“15” to dial local mobile
numbers. The prefix must be
dropped from abroad.
In Mexico, mobile numbers
must be added a “1” if dialed
from abroad (example shown)
166418866XX
Max Length
•
11
16
17. TeleSign Verify SMS and Voice
TeleSign Verify SMS and Voice can authenticate a known
user, verify a transaction, or block fraudsters from opening
thousands of accounts.
TeleSign Verify
SMS
TeleSign Verify
Voice
SMS and Voice
•
•
•
Phone number cleansing
87 languages in +200
countries
5+ routes per country
API Integration
•
•
•
REST APIs
SDKs
24/7 support
Mobile Identity
•
•
•
Phone number on all
accounts
Global coverage
Block suspicious users
17
18. PhoneID Standard
Delivers real-time intelligence associated with a phone Phone Type
• High-risk numbers
number and includes phone type, phone registration
• Send SMS only to
SMS-enabled phones
information and telecom carrier.
•
Data returned on all records
Phone number
9336954XX
Country Code
34
API Integration
Complete Phone
Number
349336954XX
•
•
•
Phone type
FIXED_LINE
Carrier
Telefonica de Espana
S.A.U.
Max Length
9
Min Length
9
City
Barcelona
Country
Spain
REST APIs
SDKs
Dynamic data
Mobile Identity
•
•
•
Identify anomalies
Global coverage
Block suspicious users
18
19. PhoneID Score
Assesses the risk of a phone number
associated
with an account registration or transaction.
Phone Number
MOBILE
Risk
recommendation
Allow
Score
1
Risk Level
•
•
•
Phone characteristics
Traffic patters
Reported fraud & trends
310 XXX XXX
Phone Type
Predictive Data
Low
API Integration
•
•
•
REST APIs
SDKs
Dynamic data
Mobile Identity
•
•
•
Score Recommendations
Score
Risk Level
Recommendation
801-1000
High
Block
601-800
Medium-high
Block
401-600
Medium
Flag
201-400
Medium-low
Allow
Low
Allow
Neutral
N/A
Block suspicious users
Stop bad transactions
Global coverage
0-200
N/A
19
Hinweis der Redaktion
Brenna Slide: intro Darren and TeleSIgn + mention survey. Why should you listen to you listen to us talk about Mobile Registration. For those of you who don’t know us, we currently power global new account verification and 2FA for 19 of the top 25 largest website in the world. Even been boardlyreconized by Garnter as a visionary and by delioteaas a fast growing companies and we’ve picked up a few awards a long the way. We help companies establish their users’ mobile identity with phone data and SMS, Voice, and app-based verification.Darren is our VP and co-found and he spends his days working with our largest global websites helping them roll out Mobile registration and take advantage of mobile identity.
Terrible user experience. CATCHA is even worseIf you doing email verification you take the user out of the app or browser experience. Email is not very secure and doesn’t tell you anything about your user. Need to meet the needs of Marketing (get user’s in) and Securtity (Keep fraudsters out)
Darren notes: Delete the part about about email in the formSean: get bolder and make a prediction. “From what we are hearing from our customer, we predict that the mobile phone number will be the standard online identifier”
Best practice to deflaut to SMS but if you do that make sure your SMS provider can alert you when someone has provided a number that can’t receive an SMS.
Add a voice options next to re-send code. “send via voice”
Add a voice options next to re-send code. “send via voice”
Add a voice options next to re-send code. “send via voice” Only 5.5% percent of the population is a native English speaker.
Add a voice options next to re-send code. “send via voice” Sean: we make best practices recommendations on # of SMS retries and pin-code entry retries, and PIN code length. One large customer saw an increase in registration conversions of 20% by decreasing the PIN code length from 7 digits to 5
Add a voice options next to re-send code. “send via voice”
Benefits of verification and future 2FA. Add dates