# How Whatsable fits together

> How labels, ads, the away message, automations and conditional follow-ups connect in Whatsable.

One feature rarely does the whole job. These five chains are the paths a conversation actually takes. Each link goes to the page that owns that step.

## Label chain

[Labels](/features/labels) sort conversations. [Team roles](/features/team-roles) can limit a Member to the conversations that carry some of those labels. An [AI agent](/features/ai-chatbot) can apply or remove the labels you allow. A Member is [notified](/features/notifications) only for a conversation they can see. The same labels also come from keywords, from a Click-to-WhatsApp ad, from a [broadcast](/features/broadcasts) after a recipient's message is sent, and through the [API](/api-reference/v1/contacts/add-contact-label), [Zapier](/integration/zapier), [Make](/integration/make), [n8n](/integration/n8n) and the [MCP server](/mcp).

## Lead from an ad

A person taps a Click-to-WhatsApp ad and writes to your number. The inbox shows an Ad badge, and the first message can show the ad. With **Label leads from ads automatically** on, the contact gets a label named after the ad headline. Ads without a headline get no label. See [Labels](/features/labels).

The incoming webhook and the Zapier, Make and n8n triggers can include the ad's `referral` fields. See [Click-to-WhatsApp ads](/api-reference/legacy/incoming-message#click-to-whatsapp-ads).

An [AI agent](/features/ai-chatbot) on that number can answer. When it hands the conversation to a person, the people who can see the conversation get a [notification](/features/notifications).

## Away message to Needs Review

The [away message](/features/automatic-replies) answers a customer who writes while you are closed, once per closed period, and labels the contact **Needs Review**. Your team finds those conversations in the morning.

If an [AI agent](/features/ai-chatbot) is on for that number, it can answer the next message, or hand the chat to a person. A handoff notifies the people who can see the conversation. When a reply contains a figure the agent could not find in its knowledge, the inbox marks it for someone to check. See [Check a figure the agent wrote](/features/inbox-conversations#check-a-figure-the-agent-wrote).

## Automation and CRM

An incoming message can start a [webhook](/features/webhooks), a [Zapier](/integration/zapier) Zap, a [Make](/integration/make) scenario or an [n8n](/integration/n8n) workflow. That automation can add a [label](/features/labels) and send a template.

The same WhatsApp conversation can be logged in [Pipedrive](/integration/pipedrive) or on a [monday.com](/integration/monday) board, or shown on a Lead, Contact or Opportunity in [Salesforce](/integration/salesforce). Each of those connections uses the organization it was created in.

## Send only when it still makes sense

You schedule a message now. You add a [condition](/features/conditional-follow-ups): they have not replied, or their labels still match. When the send is outside the 24-hour window, the message has to be an approved [template](/features/message-templates).

Whatsable checks the condition when the message is due, not when you schedule it. If the condition fails, nothing is sent, and the scheduled message records why. A broadcast has no send condition. Broadcast labels are added after a recipient's message is sent.