An existing contact with multiple matches

Prerequisite: External Contacts > Identify > Merge permission 

Single customer view auto stitches an interaction to an external contact considered to be the best match that is the first created external contact with an identifier, for example, a phone number for a voice call, an email address for an email, and a social identifier for a Genesys cookie. If Genesys Cloud finds other external contacts for that identifier, the search box is auto populated with that identifier and does a search. The search results show other external contacts related to that identifier.

For example,

• A contact named Alexis is created with her phone number +1 803-123-0000 on February 4.
• Another contact named David is created with the same phone number +1 803-123-0000 on March 20.
• On receiving a phone call from +1 803-123-0000, the interaction is auto stitched to Alexis and not David as Alexis is the first created external contact with the phone number. 

Notes:

• Only if the agent deletes the first created external contact from the system manually or via API, Genesys Cloud points the interaction to the next created external contact.
• If you determine that this contact is incorrect, then to unlink the contact, in the upper right corner, click Unlink .

Inbound call interaction

No existing contact for the identifier

Prerequisite: External Contacts > Identify > Promote permission

If the agent identifies that the existing external contact is not the best match for that interaction, the agent can choose the best match from the other possible external contact and link that interaction to the external contact. If Genesys Cloud cannot find the existing external contact using the contact identifiers, Genesys Cloud displays the Temporary contact data box. The agent can click the Save Contact button to create and save the external contact. 

For more information about creating a contact, see Add a contact.

Email interaction

A web messaging interaction

Prerequisite: External Contacts > Contact > View  permission

If a web messaging interaction does not have a related email address or phone number, the single customer view uses a Genesys cookie to create a temporary or ephemeral contact.

Because the identifier information does not include the contact’s name, the single customer view does not display a name and saves the Genesys cookie with the ephemeral contact. The Genesys cookie does not appear on the External Contact record.

To save the contact, click Create Contact. Then, enter the customer’s information and click Save. The first name and last name are required to save the contact.

Web messaging interaction

Add a contact

Callback and campaign interactions

The single customer view does not currently support campaign callbacks and campaigns. The single customer view automatically populates the phone number in the search box and automatically searches for the contact during campaign callbacks and campaigns.

The agent can now select an existing contact or create a new contact with the phone number of the campaign. The single customer view makes it easier for the agents to manually add the interaction to the correct contact. The customer conversation data does not appear in the Customer Journey tab.

To search for a contact, in the search box, type the phone number, and then select it from the results.

Search for a contact

New visit with website form fill

This scenario describes a web message with data collected from a web form fill. The data includes the contact’s name, phone number, and email address. The screenshot shown as an example displays the email address. 

The single customer view automatically searches for an existing External Contact using an identifier such as phone number and email address and displays the existing contact, if any. If necessary, the agent can manually search for a contact and view the matching results. If necessary, the agent can also merge all the contact details with the existing contact.

To search for a contact, in the search box, type the phone number, and then select it from the results.

For more information about different external contact user scenarios with Predictive Engagement, see External contact enrichment scenarios with Predictive Engagement. 

Web messaging interaction

Social messaging interaction

If the single customer view does not find an existing contact with the social identifier, then the Temporary contact data box appears. 

To save the contact, click Save Contact. Then, enter the customer’s information and click Save.

Note: For WhatsApp interactions, the single customer view does not automatically search on the WhatsApp phone number. The single customer view saves the number as a WhatsApp identifier under Channels.

WhatsApp messaging interaction

Lack of permissions

Prerequisite: 

The following permissions:

• External Contacts > Conversation > Associate
• External Contacts > Identity > Promote
• External Contacts > Identity > Merge

The single customer view automatically searches for an existing External Contact and retrieves the associated contacts. After retrieving, Genesys Cloud verifies the agent’s permissions on the retrieved contacts and displays the Permission required message in the following scenarios:

• If the conversation doesn’t have an associated contact and the agent lacks associate permissions to associate the new contact with the existing External Contact.
• If the contact is an ephemeral contact and the agents lacks merge, promote, and associate permissions.

When there are multiple participants in an interaction

Prerequisite

The following permissions:

• External Contacts > Conversation > Associate
• External Contacts > Identity > Promote
• External Contacts > Identity > Merge

In single customer view, an agent interacting with multiple participants (internal or external) and who does not have the required permissions to perform a specific action is displayed with the Multiple participants message. The following are some of the example scenarios:

• When an agent sends an email to multiple participants (internal or external) at once.
• In case of transfer, if the conversation is transferred to another participant, and that participant gets added to the conversation.
• If the call flow contains a bot in the conversation, which is considered as an internal participant.

When there are missing permissions during contacts merge

Prerequisite

The following permissions:

• External Contacts > Conversation > Associate
• External Contacts > Identity > Promote
• External Contacts > Identity > Merge

Missing permissions is displayed when:

• in an interaction, if the single customer view identifies a matching curated contact in Genesys Cloud, but the agent lacks associate permission.
•  in an interaction, if the single customer view identifies matching contacts in Genesys Cloud, but the agent lacks merge permissions to merge the contacts.