Bulk actions & merging

Your People list isn't only for browsing. Select several people and act on them in one go, or fold two records of the same person into a single one.

Select people

On /app/people, every row has a checkbox, and the header checkbox selects everyone on the current page. Your selection sticks as you page through the table, so you can gather people across several pages before acting. The moment one person is selected, a bulk-action bar appears.

Act on the selection

With people selected, the bar offers:

• Merge — combine two or more records of the same person into one (needs at least two selected). See below.
• Add to company — attach everyone to a company at once; pick an existing one or create it inline.
• Change relationship — relabel how the selected people relate to a company — studied at, worked at, interned at, board member of, and so on. Only the label changes; nobody moves companies. See Relabel relationships in bulk below.
• Tag — add or remove a tag across the whole selection.
• Star / Unstar — flag or unflag people for your Saved list.
• Not a person / Is a person — settle in one go whether the selection is people or address-book clutter ("Ola Support", "Vegetable Vendor"). Marking a row Not a person keeps it off suggestions only; it stays listed in People, in search and in every export, and nothing is deleted. Your ruling sticks — Dhaga's nightly check never overrides it. See your daily briefing for what suppression does and doesn't touch.
• Delete — forget the selected people. This cascades — their notes, facts, edges, and embeddings go too — exactly like "forget this person" on a single profile.

Relabel relationships in bulk

Phone and address-book imports often land everyone at a place as "works at" — including the classmates you studied with and the professors who taught you. Change relationship fixes a whole batch in one pass:

1. Select the people and click Change relationship.
2. Choose which company the label applies to — their current company (each person's own), or a specific company you pick.
3. Choose the new relationship — studied at, worked at, interned at, board member of, and so on, or create your own type.
4. Apply.

Only the affiliation label changes — nobody is moved to a different company. So students relabelled to "studied at" and the professors left as "works at" still cluster on the same university node in your graph.

Merge duplicate contacts

Met the same person twice — a card scan and a LinkedIn import, say — and now they're two records? Merge folds them into one:

1. Select the records and click Merge (or start from Find duplicates, below).
2. Pick the survivor — the record everything else folds into.
3. Resolve conflicts. Where records disagree on a single-value field — name, nickname, or location — you choose which value wins. Fields where they already agree don't ask.
4. Everything that can hold more than one value is combined onto the survivor: emails, phones, links, addresses, important dates, custom fields, tags, jobs, notes, facts, and relationship edges. Nothing is dropped.

The other records are then permanently deleted. It all happens in a single step — either the whole merge lands or nothing changes.

Find duplicates

You don't have to spot duplicates yourself. The Find duplicates link in the People page header opens /app/people/duplicates, which groups likely duplicates it notices — by a shared email, a shared phone, or the same name — into clusters.

Each signal gets its own collapsible section, strongest first, and the first one starts open. Long lists are paged rather than dumped on the screen: a section shows ten groups at a time, a group shows six people at a time, and a Show more button reveals the rest. One more section sits at the bottom, collapsed and counted in sets — Dismissed, the sets you've told Dhaga aren't duplicates. See Not a duplicate below.

You choose who actually gets merged. Every person in a group has a checkbox, and the button reads Merge selected — it stays disabled until you've ticked at least two. What's ticked by default depends on how strong the match is:

• Same email and same phone are exact matches, so everyone in the group starts ticked — untick anyone who doesn't belong.
• Same name starts with nothing ticked. Two people really can share a name, so Dhaga won't assume. If it offers you five Amit Singhs and only three are the same person, tick those three and merge them; the other two are left exactly as they were — and if that pair keeps coming back, you can tell Dhaga they aren't duplicates at all.

Not a duplicate

Next to the merge button, every group carries Not a duplicate. Press it and the group drops off the list, with a toast confirming it: Not a duplicate. Dhaga won't offer this set again.

Nothing is deleted and nothing is edited. The people are untouched — still in People, still in search, still in every export. The only thing that changes is that Dhaga stops offering them to you as one person.

Your answer is keyed on the exact set of people in that group — not on the name, email, or phone that gathered them. So if a contact you add later matches that same name, it's a different set, and Dhaga will offer the group again. That's deliberate: an answer you gave six months ago should never quietly hide a duplicate that's genuinely new.

You can change your mind two ways. The toast carries Undo, for the moment you press the wrong button. And the collapsed Dismissed section at the bottom of the page lists every set you've suppressed, each with Restore to put it back in the list above — Back in the list. Restoring a set doesn't merge anything; it just puts the question in front of you again.

Companies have the same tools — view, merge, dedupe, and dismiss them on the Companies page.