Tags are labels your team puts on a lead or on a contact — «vip», «corporate», «repeat». Type one, or several separated by commas, in the Tags block on the card; the field suggests the labels your account already uses, so one label is not spelled three ways. Up to 20 per card, kept in lower case. A tag on a card is a link to every lead or contact that carries it.

Filter, label in bulk, export. On Leads (board and list), pick a tag next to the owner filter: the board, its counters, the list and the CSV export all follow it. On Contacts the tag filter narrows the list; the contacts CSV export always has everyone, with each person's tags in a column. In the list view, tick several leads and use Add tag or Remove tag at the bottom to label them at once. A contacts CSV import reads a tags column (several tags separated by commas), and the API returns tags with every lead and contact.

Two cards of one person. When the same customer ends up with two contact cards that share a phone number or an e-mail, managers and admins see a hint on the card, and Contacts → Duplicates lists every such pair — a shared name alone never counts. Open a pair to see the card as it will be before anything changes: the card that stays keeps its name, fields and responsible colleague, takes the other card's phones, e-mails and tags, and every call, chat, lead, task, appointment and note moves onto it; then the other card is removed. The older card stays by default, and you can keep the other one instead. A merge cannot be undone, which is why the preview comes first.

Two leads about one need. On a lead card, Other open leads of this person lists the same customer's other open leads. Take into this lead shows what will happen, then merges: the lead you are on keeps its stage, pipeline and owner, the other lead's message is added below with its date, and its tasks, notes and comments move over. Only two open leads of the same person can be merged — not a closed one, and not one still waiting in Unsorted. Anyone who works leads can do it; an operator who sees only their own leads can merge only leads they can open.

If another system mirrors your data through the API, subscribe it to the contact.merged and lead.merged events: each names the record that stays and the one that is gone, so the other system can fold its copy.