A real contact database for WhatsApp — unlimited fields, unlimited tags , groups that power your broadcasts.

A label (we call them tags) is a single membership flag — `vip`, `mumbai-metro`. A custom field is a typed property with a value — `lifetime_value = 18420`, `birthday = 1974-02-11`, `loyalty_tier = silver`. WhatsMark gives you both, unlimited on every plan. Meta's free WhatsApp Business app gives you 20 labels and zero fields — that's the floor most buyers are escaping.

Thirteen: Text, Text Area, Number, Date, Email, URL, Phone, Dropdown, Radio, Checkbox, Toggle, Color, and Time. Dropdown, Radio, and Checkbox let you define a fixed set of options; Toggle is a simple on/off flag for things like marketing consent. It's the kind of typed field taxonomy a HubSpot or a Salesforce gives you, applied to your WhatsApp contact list.

You can't inside Meta's free Business app — it caps at 20 custom labels. To go past that you move to a Cloud-API platform like WhatsMark, where tags are unlimited on every plan. Most BSPs also cap by plan: AiSensy allows 5 attributes on Basic, 20 on Pro; Wanotifier allows 10 tags+attributes on Essentials, 25 on Advanced. WhatsMark doesn't ladder fields or tags by plan — they're unlimited on every tier, including Free.

Two truthful ways today. Organise contacts into a named group and target that group when you launch a broadcast — the cleanest reusable option. Or, in the campaign wizard, filter the contact list by status, source, lifecycle stage, or owner (and search), then select the matches. Rule-based self-updating "segments" — the Mailchimp/Klaviyo style where a saved rule re-evaluates at send time — aren't part of the product today; groups and filters are the honest, shipped way to build an audience.

Filter the contact list to the people you want — say all Mumbai men's-shoes contacts — or select them individually, then choose Bulk Edit. You can add or remove tags, change the lifecycle stage, add to or remove from a group, assign an owner, or activate/deactivate — on the whole selection in one action. Large batches run in the background so the UI stays responsive, and every bulk change is written to an audit log with the acting user and timestamp. (Bulk-setting a *custom* field value across many contacts isn't supported yet — custom fields are edited per contact or via the API.)

Upload a CSV or XLSX, run the field-mapping wizard — point each column at the phone key, a standard field, or an existing custom field — and the file is processed in the background with a downloadable error report for any rows that fail. Duplicates are handled by skipping: if a phone number already exists in your account, that row is skipped and noted in the report rather than creating a second contact. Import doesn't overwrite existing contact data — it adds new contacts and leaves the ones you already have untouched.

The phone number is the unique key, so the importer won't create a duplicate on its own. For duplicates you inherited from elsewhere, merge is a deliberate action you run on two records: you pick which one to keep, and the other's labels and groups are unioned onto it while any blank fields on the record you keep are filled in from the other. Notes follow the merge and conversation history is preserved for both identities — nothing is deleted. It's a safe, reviewable merge, not an automatic guess.

Yes, per contact — the REST API lets you create or update a contact with its custom fields, tags (labels), and groups, and there's a batch-create endpoint for up to 100 at a time. API access is a paid-plan capability (it's off on Free) and is metered by a monthly request quota. Note there's no bulk "set this field on 4,000 contacts" API call today — bulk field changes are done per contact or through the in-app bulk actions for tags, groups, and lifecycle.

Every WhatsMark workspace has its own fully isolated contact database, fields, tags, and groups — so an agency running each client as its own workspace already gets clean per-client separation with nothing shared between them. A single master account that provisions and switches between client sub-accounts from one dashboard is on our B2B roadmap, not shipped yet — so today the honest setup is one workspace per client. Ask us where the reseller/sub-account work stands if that's central to you.