SSO — End Customers
Enable brand-managed SSO for customer login across Reach-powered web and app experiences.
Overview
End-customer SSO lets customers log in to Reach-powered experiences using brand-managed credentials.
Reach delegates authentication to your Identity Provider (IdP). Reach does not store passwords.
What it is: Brand-managed SSO for customer login.
What problem it addresses: Eliminates duplicate accounts and centralizes security policies.
Who it is intended for: Customers using Reach-powered web and app experiences.
Typical use cases
Let customers reuse an existing brand login
Reduce friction in checkout and self-care
Centralize MFA and security policy under the brand
Scope
What is included:
SSO integration for customer login across Reach-powered surfaces:
brand website
mobile web
mobile apps
checkout and self-care portals
Session creation and identity linkage
What is excluded:
Agent SSO for Reach Central
Brand password reset and credential management
Customer identity merges or migrations
Brand inputs
Which IdP will be used and who owns it
Which identity fields will be used to match customers
A small set of test customers for validation
Approval owner for go-live
Requesting this bolt-on
For the standard request process, commercial notes, and support, see Bolt-ons catalog.
Technical details
For the implementation-specific setup details, visit: SSO technical details
Frequently asked questions
When should we request end-customer SSO?
Request it when your brand identity system is ready for integration.
What happens after we purchase?
Reach confirms the scope and collects your IdP details.
Last updated