<?xml version="1.0" encoding="UTF-8"?><oembed><type>video</type><version>1.0</version><html>&lt;iframe src=&quot;https://www.loom.com/embed/02dc531465fc4f2cb965ee4742d602f1&quot; frameborder=&quot;0&quot; width=&quot;1920&quot; height=&quot;1440&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>1440</height><width>1920</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>1440</thumbnail_height><thumbnail_width>1920</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/02dc531465fc4f2cb965ee4742d602f1-d5c2caea00c95dcc.gif</thumbnail_url><duration>572.715</duration><title>How to Identify and Merge Duplicate Accounts</title><description>This Loom explains how to identify and merge duplicate Salesforce accounts. The presenter searches Salesforce by first and last name and reviews potential duplicates such as Nikki Halder variants (Nicky Holder, Nicky Holder, and Nix Holder), which appear to share the same phone number but differ by email, the unique identifier for new accounts. The vetting protocol requires verifying all passing Code of Conduct and obtaining a verbal yes from the client that all accounts belong to her, then choosing a primary email and keeping one secondary backup. After confirming, the account details are merged into the primary account and a Zendesk Business Operations merge account request is submitted without CCing the client, using a subject like client has dupes.</description></oembed>