[WhatsApp](/products/whatsapp) # From your ad to a conversation. Connect an ad’s promise to a conversation that helps the customer act. Qualify the request, answer the question and carry the source through to the lead, booking or order. [Plan your WhatsApp ad journey](/demo?product=whatsapp-click-to-chat) [Read the attribution guide](/docs/guides/whatsapp/click-to-whatsapp-attribution) ## Set up with your agent [Read the agent setup guide](/docs/ai/set-up-your-agent) Copy this prompt into your coding agent: ```text Bird connects customer communications, data and automation. Help me build with Bird using my coding agent. 1. Read https://bird.com/docs/ai/set-up-your-agent.md and follow its setup workflow for this client. Use an existing connected Bird MCP server or signed-in CLI when available. 2. Read the product guide for the task I want to complete and inspect my existing integration. Identify the workspace, available operations and required setup. 3. Help me complete a first example for the product and destination I choose. Follow the operation through to its actual result, explain any uncertainty, and help me choose the next step. First task: Prepare a click-to-WhatsApp journey from ad promise to first reply and business outcome. Inspect documented referral fields and consent requirements; do not change or publish ads. Use this Bird page as the starting context: https://bird.com/products/whatsapp/click-to-whatsapp Read its Markdown alternative and linked guides. Keep the first example relevant to this page and the customer outcome I choose. Preserve the supplied campaign context when following Bird signup or sales links. ``` Keep the promise from ad to answer An ad with a useful invitation Find the right collection for your space. Open the conversation The customer asks about the collection. Qualify the request Understand the product and service needs. Complete the next step Record the real appointment or order. Ad referral From the connected ad integration Conversation Matched by supported identity Lead Qualified by business rules Outcome Confirmed by owning system Preserve the source Keep ad click identity, website UTMs and internal campaign IDs distinct. Example ad journey. Available referral data depends on your ad integration. ## Deliver on the reason someone clicked. Keep the offer, creative and opening conversation aligned. Start with the question or choice the customer expects from the ad. ## Reduce the first-step effort Use a useful opening prompt and a small number of relevant options. Avoid asking the customer to restate everything the ad already established. ## Make the response available Prepare the AI or team that receives the conversation. An unanswered chat wastes the intent the campaign worked to create. **One promise, from ad to conversation Example** Mora Studio Example ad Ceramics collection featured in the example ad Find the right piece for your space. Message us about the new collection. I saw your collection. Which vase works for a small table? ## Help the customer reach a meaningful next step. Connect the request to the relevant knowledge, product or service workflow. Ask only for the details that change qualification or fulfillment. ## Choose the useful path Use a short native form, a product choice, an appointment or a human conversation according to the customer’s task. ## Keep the outcome honest Mark a lead qualified only when it meets your business definition. Record bookings and purchases from their owning systems. ## Carry attribution through the whole journey. Preserve the ad referral or click identity when the connected ad integration supplies it. Join it to the conversation and the confirmed business event without assuming every inbound message exposes the same referral fields. ## Separate the identities An ad click identifier, a website UTM and your campaign ID are different data. Keep their provenance and use the supported join rather than manufacturing a click ID. ## Review quality as well as volume Compare spend, opened conversations, qualified leads and completed outcomes. Deduplicate repeated events and account for the chosen attribution window. ## Click-to-WhatsApp ads questions ### Is a click-to-WhatsApp ad the same as a WhatsApp campaign? No. An ad brings a customer into a conversation from an advertising placement. A WhatsApp campaign sends eligible messages to an audience that already has the required permission. ### Can we measure purchases after the conversation? Join the conversation and available ad source to a confirmed order or payment event. Define the attribution window and deduplication rules for that integration. ### Does every inbound API message include an ad click ID? Do not assume that. Preserve referral data when the connected ad integration provides it and follow the published fields of the actual integration. ### Should an AI agent greet every ad visitor? Use AI when it can answer the expected request and complete a useful next step. Keep a clear human route for complex or ambiguous enquiries. ## Connect the complete journey - [Click-to-WhatsApp ads guide](/docs/guides/whatsapp/click-to-whatsapp-attribution): Follow the setup, operating decisions and verification steps. - [WhatsApp marketing](/products/whatsapp/marketing): Create relevant campaigns and help customers respond. - [WhatsApp AI agents](/products/whatsapp/ai-agents): Answer questions, take action and hand over to your team. - [WhatsApp analytics](/products/whatsapp/analytics): Follow delivery, customer response and business results. - [WhatsApp resource library](/products/whatsapp/resources): Explore implementation guides, explained answers and comparisons. - [WhatsApp platform](/products/whatsapp): Explore the connected product and choose the next capability. ## Make the conversation ready before the ad runs. Align the offer, first reply and qualified next action. Plan source capture and outcome measurement with the team handling the conversation.