Everyone your team talks to on WhatsApp, in one list

There are two sources, and both land in the same list.

1. Synced from your connected WhatsApp numbers. When you link a WhatsApp or WhatsApp Business app number by scanning a QR code, whatsappx.si becomes a linked device, like WhatsApp Web (WhatsApp Help Center), and recent chat history syncs in. Each person in that history becomes a contact. Numbers connected through Meta’s official WhatsApp Business Platform work the same way: when someone messages your business number, a contact is created from the sender’s details. From then on, every new conversation adds the sender automatically.

2. Added by your team. Anyone in the workspace can add a contact from the Contacts page, and developers can create contacts through the REST API. This suits people you already have permission to message but who have not written to you yet, for example a customer who ticked "contact me on WhatsApp" on your order form.

A contact record is deliberately small: a name, a phone number stored as digits with the country code, and, for contacts you add, one tag and an opt-in flag. whatsappx.si is not a full CRM. If you keep customer records elsewhere, the REST API can list and create contacts, and outbound webhooks forward incoming messages to your own system.

A contact is the person; a conversation is the thread with that person on one of your connected numbers.

• The inbox reads from contacts. The name and tag shown on each conversation come from the matching contact, so teammates can see who they are talking to.
• Assignment lives on the conversation. Owners and admins assign a thread to a teammate from the chat view, and the inbox can be filtered to "mine", "unassigned" or a specific colleague. Agents see only the chats assigned to them. Assignment is about who answers right now, so it belongs to the thread, not the contact.
• Unread counts follow the conversation. A new message raises the unread count, and marking the conversation as read clears it for the team.
• Contacts are shared, not personal. Every workspace member sees the same list. When a colleague is on leave, the context is still there.

For example, a small clinic could let patient conversations sync in from its number, add suppliers by hand with the tag "Supplier", assign new patient conversations to whoever is on duty and keep supplier chats with the manager.

Yes. The REST API exposes the same contacts your team sees: GET /api/v1/contacts lists them, POST /api/v1/contacts creates one (phone as 8–15 digits with the country code, no leading zero) and DELETE /api/v1/contacts/{id} removes one. Requests carry an API key as a Bearer token, and each key belongs to one workspace. Read-only keys can list contacts; full-access keys can also create and delete them. Outbound webhooks forward incoming messages to your own system. Examples are in the in-app API docs and on the API and webhooks page.