You are here:
Configure and Use Identity Verification in Public Sector
Use a flow to verify a constituent's identity before sharing private information over the phone or through another engagement channel.

Use more general search terms.
Select fewer filters to broaden your search.
You are here:
Use a flow to verify a constituent's identity before sharing private information over the phone or through another engagement channel.
| View supported product editions. |
| User Permissions Needed | |
|---|---|
| To set up Identity Verification flows: | Customize Application AND Industry Service Excellence |
| To use Identity Verification flows: | Industry Service Excellence |
Before sharing benefit details or other sensitive and private information with a constituent, make sure that Public Sector representatives confirm who they're talking to. With Identity Verification, use a flow to verify the identity of individuals who initiate an engagement in person, though a phone call, over Open CTI, or by using a messaging session. Agents can even verify the identity of an authorized representative, such as a constituent's spouse or legal guardian.
By default, agents can verify a constituent or their representative’s account name, birth date, phone number, and postal code. You can also customize identity verification flows with your own processes and questions. Add the flow to engagement interaction or voice call record pages, or to the utility bar of one of the Public Sector Lightning apps, so agents can start it easily from wherever they're working. Every verification generates an engagement interaction record, which is used to create an audit trail.

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.