CIAM elevates the customer experience (CX) by simultaneously reducing friction and building trust.
Reduce Friction
With CIAM, you no longer need to push every customer through the same rigid authentication processes when they visit your site.
For example, if they’re registering for the first time, you don’t necessarily need to ask them to enter all their personal data immediately—you could just ask them to provide their email address and set a password and then let them browse your site to their heart’s content. Then, at the point when they decide to place their first order, you can ask them for their address and payment details. At any given point in their journey, you’re only asking them for the information you actually need, so they can focus on their shopping experience rather than filling in forms.
Similarly, when an existing customer wants to log into your site, you can make smarter decisions about how many authentication hoops you should make them jump through. For example, if they logged in successfully an hour ago on the same PC with the same IP address, and their mouse movements and typing patterns are the same as they were before, you might decide they don’t need to enter their password again.
Essentially, CIAM allows you to adjust the level of friction in your authentication experience appropriately so that customers don’t feel they’re being bothered unnecessarily.
Build Trust
When we talk about adjusting friction, the key word is “appropriately”. Zero friction isn’t always the right answer from a security perspective—and it’s not always what customers want, either.
For example, imagine you get a login request that seems to be coming from an existing customer, but the IP address shows that they are in a different country and using an unknown device. In that case, you might decide to send a multi-factor authentication request to make sure the customer is who they say they are.
Let’s say the request does come from a genuine customer—perhaps they’re traveling overseas, and they’ve borrowed a friend’s device because their own smartphone won’t connect to the local network. In this situation, receiving an additional security challenge doesn’t feel like unnecessary friction—it’s actually reassuring for the customer because it shows them that you’re taking their account security seriously.
Only asking for the authentication that you need, and always asking for authentication when you need it, are two sides of the same coin. If you can prove to customers that the friction added to the experience is always proportionate to the situation, you’ll find it much easier to win their trust.