Known Limitation:
In the current version of the External Contacts CSV Bulk Import feature, if there is only one identified contact that matches a contact being imported from the CSV ( by phone number or email address), the identified contact will not automatically merge with the imported contact, and the identified contact will not be promoted into a curated contact.

However, if there are multiple identified contacts matching the imported contact, the system will merge them, resolving the issue for the user.

Recommended Workaround: To ensure smooth merging of contacts during CSV import, follow these steps:

1. Prepare Your CSV:

   • Remove phone and email fields from the CSV OR Alternatively Uncheck the "Match Contacts By: Email and Phone" fields in your import profile.

   • Ensure all rows include valid ExternalIDs.

   • Leave the default match and merge conditions unchanged in the import settings page.

2. Upload and import the CSV File:

   • This will create new curated contacts, each with an ExternalID.

3. Update Your CSV:

   • Add the phone and email fields back to the CSV, ensuring that ExternalID fields remain the same.

   • Leave the default match and merge conditions unchanged in the import settings page.

4. Upload the Updated CSV:

   • This step will merge the autogenerated contacts (with phone/email data) into the curated contacts created in step 1.

Future Enhancement:
In an upcoming release, we plan to address this user experience issue. Genesys Cloud Admins will be able to ensure that identified contacts (with phone or email data autogenerated by the platform) that match the CSV records are enriched and always transformed to curated contacts and merged.

For more information about the the new CSV Bulk Import feature for External Contacts, checkout the enhancement announcement and the video. 

Thanks for that info Mojdeh! 

Will the upcoming changes be part of a public Beta?

Known Limitation:
In the current version of the External Contacts CSV Bulk Import feature, if there is only one identified contact that matches a contact being imported from the CSV ( by phone number or email address), the identified contact will not automatically merge with the imported contact, and the identified contact will not be promoted into a curated contact.

However, if there are multiple identified contacts matching the imported contact, the system will merge them, resolving the issue for the user.

Recommended Workaround: To ensure smooth merging of contacts during CSV import, follow these steps:

1. Prepare Your CSV:

   • Remove phone and email fields from the CSV OR Alternatively Uncheck the "Match Contacts By: Email and Phone" fields in your import profile.

   • Ensure all rows include valid ExternalIDs.

   • Leave the default match and merge conditions unchanged in the import settings page.

2. Upload and import the CSV File:

   • This will create new curated contacts, each with an ExternalID.

3. Update Your CSV:

   • Add the phone and email fields back to the CSV, ensuring that ExternalID fields remain the same.

   • Leave the default match and merge conditions unchanged in the import settings page.

4. Upload the Updated CSV:

   • This step will merge the autogenerated contacts (with phone/email data) into the curated contacts created in step 1.

Future Enhancement:
In an upcoming release, we plan to address this user experience issue. Genesys Cloud Admins will be able to ensure that identified contacts (with phone or email data autogenerated by the platform) that match the CSV records are enriched and always transformed to curated contacts and merged.

For more information about the the new CSV Bulk Import feature for External Contacts, checkout the enhancement announcement and the video. 

We do not have a Beta release planned for these fixes. They will be released directly to GA, with the timeline set for March 2025.

Once the changes are GA'd, I'll post an update here. This will be part of a larger epic that includes additional enhancements to the existing CSV Bulk Import feature, such as Division Support.

Thanks for that info Mojdeh! 

Will the upcoming changes be part of a public Beta?

Known Limitation:
In the current version of the External Contacts CSV Bulk Import feature, if there is only one identified contact that matches a contact being imported from the CSV ( by phone number or email address), the identified contact will not automatically merge with the imported contact, and the identified contact will not be promoted into a curated contact.

However, if there are multiple identified contacts matching the imported contact, the system will merge them, resolving the issue for the user.

Recommended Workaround: To ensure smooth merging of contacts during CSV import, follow these steps:

1. Prepare Your CSV:

   • Remove phone and email fields from the CSV OR Alternatively Uncheck the "Match Contacts By: Email and Phone" fields in your import profile.

   • Ensure all rows include valid ExternalIDs.

   • Leave the default match and merge conditions unchanged in the import settings page.

2. Upload and import the CSV File:

   • This will create new curated contacts, each with an ExternalID.

3. Update Your CSV:

   • Add the phone and email fields back to the CSV, ensuring that ExternalID fields remain the same.

   • Leave the default match and merge conditions unchanged in the import settings page.

4. Upload the Updated CSV:

   • This step will merge the autogenerated contacts (with phone/email data) into the curated contacts created in step 1.

Future Enhancement:
In an upcoming release, we plan to address this user experience issue. Genesys Cloud Admins will be able to ensure that identified contacts (with phone or email data autogenerated by the platform) that match the CSV records are enriched and always transformed to curated contacts and merged.

For more information about the the new CSV Bulk Import feature for External Contacts, checkout the enhancement announcement and the video. 

Hi Fatemeh.

Hope this finds you well.

The Old Import format uses the 'Contact Id' as an identifier, while the new Import format uses 'External Id' as an identifier.

If an existing Org with the old 'Contact Id' chooses to use the new format primarily because they now want to link it to an external source (AD).

What happens to the old 'Contact Id' field? 

Will it be overwritten with the newer 'External Id' field if the contact matches both Email and Phone Number fields?

Thank you.

We do not have a Beta release planned for these fixes. They will be released directly to GA, with the timeline set for March 2025.

Once the changes are GA'd, I'll post an update here. This will be part of a larger epic that includes additional enhancements to the existing CSV Bulk Import feature, such as Division Support.

Thanks for that info Mojdeh! 

Will the upcoming changes be part of a public Beta?

Known Limitation:
In the current version of the External Contacts CSV Bulk Import feature, if there is only one identified contact that matches a contact being imported from the CSV ( by phone number or email address), the identified contact will not automatically merge with the imported contact, and the identified contact will not be promoted into a curated contact.

However, if there are multiple identified contacts matching the imported contact, the system will merge them, resolving the issue for the user.

Recommended Workaround: To ensure smooth merging of contacts during CSV import, follow these steps:

1. Prepare Your CSV:

   • Remove phone and email fields from the CSV OR Alternatively Uncheck the "Match Contacts By: Email and Phone" fields in your import profile.

   • Ensure all rows include valid ExternalIDs.

   • Leave the default match and merge conditions unchanged in the import settings page.

2. Upload and import the CSV File:

   • This will create new curated contacts, each with an ExternalID.

3. Update Your CSV:

   • Add the phone and email fields back to the CSV, ensuring that ExternalID fields remain the same.

   • Leave the default match and merge conditions unchanged in the import settings page.

4. Upload the Updated CSV:

   • This step will merge the autogenerated contacts (with phone/email data) into the curated contacts created in step 1.

Future Enhancement:
In an upcoming release, we plan to address this user experience issue. Genesys Cloud Admins will be able to ensure that identified contacts (with phone or email data autogenerated by the platform) that match the CSV records are enriched and always transformed to curated contacts and merged.

For more information about the the new CSV Bulk Import feature for External Contacts, checkout the enhancement announcement and the video. 

Hello Bernard,  

Previously you had all your contacts imported via the old CSV, and the Contact ID was used to fill out UUIDs from AD ? 

If you choose to re-import contacts from AD, and fill-out ExternalID field with the AD UUIDs, as long as there's an email or phone match, the old contact will be merged with the new ones you import. The Contact ID field will remain unchanged. It is a completely separate field. 

We are debating / discussing migrating ContactId data to ExternalID for all those contacts that have Contact ID filled out previously. 

I can keep you posted of the decision/results. 

Thanks,

Hi Fatemeh.

Hope this finds you well.

The Old Import format uses the 'Contact Id' as an identifier, while the new Import format uses 'External Id' as an identifier.

If an existing Org with the old 'Contact Id' chooses to use the new format primarily because they now want to link it to an external source (AD).

What happens to the old 'Contact Id' field? 

Will it be overwritten with the newer 'External Id' field if the contact matches both Email and Phone Number fields?

Thank you.

We do not have a Beta release planned for these fixes. They will be released directly to GA, with the timeline set for March 2025.

Once the changes are GA'd, I'll post an update here. This will be part of a larger epic that includes additional enhancements to the existing CSV Bulk Import feature, such as Division Support.

Thanks for that info Mojdeh! 

Will the upcoming changes be part of a public Beta?

Known Limitation:
In the current version of the External Contacts CSV Bulk Import feature, if there is only one identified contact that matches a contact being imported from the CSV ( by phone number or email address), the identified contact will not automatically merge with the imported contact, and the identified contact will not be promoted into a curated contact.

However, if there are multiple identified contacts matching the imported contact, the system will merge them, resolving the issue for the user.

Recommended Workaround: To ensure smooth merging of contacts during CSV import, follow these steps:

1. Prepare Your CSV:

   • Remove phone and email fields from the CSV OR Alternatively Uncheck the "Match Contacts By: Email and Phone" fields in your import profile.

   • Ensure all rows include valid ExternalIDs.

   • Leave the default match and merge conditions unchanged in the import settings page.

2. Upload and import the CSV File:

   • This will create new curated contacts, each with an ExternalID.

3. Update Your CSV:

   • Add the phone and email fields back to the CSV, ensuring that ExternalID fields remain the same.

   • Leave the default match and merge conditions unchanged in the import settings page.

4. Upload the Updated CSV:

   • This step will merge the autogenerated contacts (with phone/email data) into the curated contacts created in step 1.

Future Enhancement:
In an upcoming release, we plan to address this user experience issue. Genesys Cloud Admins will be able to ensure that identified contacts (with phone or email data autogenerated by the platform) that match the CSV records are enriched and always transformed to curated contacts and merged.

For more information about the the new CSV Bulk Import feature for External Contacts, checkout the enhancement announcement and the video.