--- title: "How to Find Mixed-Up Client Cards" description: "Run a scan of the client database and read the case list: problem classes, filters, self-healing cases." --- # How to Find Mixed-Up Client Cards Until someone looks, mixed-up cards do not announce themselves — they quietly spoil the history in the chat and the numbers in reports. A scan collects them into one list where each row is a specific place with a specific problem. This guide helps you run the check and understand what the list shows. --- ## When You Need It - An operator reported seeing someone else's conversation in a client card. - You have just imported a client database or merged cards in bulk and want to check the result. - You run a regular quality check of the database — weekly or monthly. --- ## What You Should Know - **Case** — one place found where data got tangled. It has a problem class, cards, a channel, and a dialog count. - **Problem class** — the type of situation. There are three: **Multiple accounts on a card**, **Foreign contact**, **Stray dialogs**. - **Self-healing** — cases that will disappear on their own after the client's next message. Hidden by default. - **Status** — **Open** (the case is waiting) or **Resolved** (an operation has already been applied). --- ## Before You Start - [x] You are signed in as **root**. For now card untangling is available to **root only** — it cannot be granted to any other role. - [x] You have navigated to the **Clients** module via `Menu -> Clients`. - [x] In the module's side menu you have opened the **Client deduplication** tab — that is the case list. If you cannot see the tab, you are not root — contact the instance owner. --- ## Step-by-Step Instructions ### 1. Run the check Click **Scan** in the top right corner. While the check runs, the button reads **Scanning…** — the list refreshes by itself once it finishes. Next to it you can see when the database was last checked: **Last scan** with the date and time. If no check has ever run, it says **No scan has run yet**. ### 2. Judge the scale from the tiles Five tiles sit above the list. Three of them are the three **problem classes**: **Multiple accounts on a card**, **Foreign contact**, **Stray dialogs**. The fourth is **painful**, labelled **need action** — those are the cases disrupting the work. The fifth is **Self-healing**, labelled **hidden** or **shown**. The three class tiles work as filters: click any of them to keep only its cases in the list; clicking again clears the filter. The **painful** tile returns the list to everything that needs a decision. The **Self-healing** tile filters nothing — it turns the display of self-healing cases on and off, like the **show self-healing** switch. If the **painful** tile shows zero, there is nothing to untangle. ### 3. Narrow the list with filters - **Problem class** — keep one type so you work through similar cases in a row. - **Card ID** — enter a card number to see only the cases around it. Handy when an operator complained about one specific card. - **show self-healing** — turn it on only when you want the full picture, including what will pass on its own. Below the list you can see the total number of cases and the page number. ### 4. Read a case row Each row reads left to right: - **Class** — the type of problem; - **Cards** — the numbers of the cards that got tangled; - **Channel** — the channel and bot the case lives in; - **Dialogs** — how many conversations the operation will touch; - **Last activity** — when these cards were last active; - **Status** — **Open** or **Resolved**. Start with cases that have recent last activity: those are the ones disrupting operators right now. ### 5. Open a case Click the row — the untangling wizard opens for that case. Continue with [How to work through a case and apply an operation](/en/broadcastusers/how-to/untangle-client-card-case.md). --- ## What Happens After A scan changes nothing in the database — it only assembles a list of findings. You get a list of cases ordered so that what disrupts the work is visible first, rather than everything at once. --- ## How to Verify Everything Worked - **Last scan** shows the time that just finished. - The **painful** tile labelled **need action** shows a number matching the list below. - If the database is clean, the list says **No cases — nothing to untangle under the current filters**. Check that the filters have not narrowed the selection to zero. --- ## Alternative Ways If you are already looking at a specific client in OperatorLine, you do not need to search the list: in the client card click **Explore links** — the same case list opens, already filtered by that card. --- ## Related Materials - [Why do client cards get mixed up?](/en/broadcastusers/explanation/mixed-client-cards.md) - [How to work through a case and apply an operation](/en/broadcastusers/how-to/untangle-client-card-case.md) - [How to check the operations journal](/en/broadcastusers/how-to/check-card-operations-journal.md) - [View client card](/en/broadcastusers/how-to/view-client-card.md)