Send Catalog Inbox Campaigns Without Leaving the Chat

In this series — Part 3 of 6 (Catalog & Commerce). · Previous: How to Connect and Sync Your Catalog with Wapil… · Next: Catalog Orders: Status Updates and Fulfillment… · Series start

Before you start: If you skipped earlier steps, read How to Connect and Sync Your Catalog with Wapil… first so nothing here feels confusing.

A synced catalog that nobody sends is a museum. When you send catalog inbox campaigns, shoppers see products where the conversation already is.

Agents paste website URLs, campaigns ignore catalog templates, and browse interest never becomes an order thread.

In this guide, you'll discover inbox sends, campaign patterns, when not to blast, and how recommendations stay human — without leaving WhatsApp. As a WAPilot team that reviews commerce chats weekly, we see live SKU cards beat generic “shop now” links.

Soft goal: agents can attach catalog from inbox, campaigns use approved catalog paths only with opt-in, and orders are ready for status follow-up next.

Operators who rush this step usually rebuild templates twice after Meta rejects lazy copy.

Keep the path short enough that a new agent can send a product card in one minute.

Operators who skip this step usually rebuild the same journey twice after customers complain.

Keep the path short enough that a new teammate can explain the habit in one standup minute.

How do you send catalog inbox campaigns from real conversations?

Sources: Meta's sell products and services guide and Cloud API get-started docs. From inbox, open the chat, pick catalog items that match what the customer asked, send the card, and continue the thread with size, color, or shipping answers. Campaigns use approved catalog/template paths only to opted-in audiences.

Sync first: connect sync catalog wapilot. Campaign discipline: campaign compliance checklist.

When should campaigns use catalog versus a plain link?

Use catalog when products are visual and SKUs are current. Use a plain link for deep custom configurators. Never broadcast stale prices. Prefer segments with clear browse or purchase intent.

Attributed example, from a WAPilot beauty brand (2026): a generic shop link campaign underperformed. Switching to catalog cards on an opted-in engaged segment lifted replies asking for shade matches within one send cycle.

1. Confirm sync health before any send.
2. Send 2–3 relevant SKUs from inbox.
3. Use approved campaign paths only to opted-in.
4. Answer variants live size, color, ship.
5. Hand off to order status when they buy.

Rule sources: Meta commerce and Cloud API get-started docs. Wapilot surfaces catalog and order tools; Meta still hosts catalog commerce on WhatsApp.

How do agents recommend without sounding robotic?

Ask one clarifying question, send two to three relevant SKUs, confirm preference, then move toward order or payment. Do not dump the whole catalog into one message.

A forty-to-sixty word answer: send catalog means inbox cards for live help and compliant broadcasts for reach—always on synced prices, always with a human path when the shopper is unsure. Next guide covers order status and fulfillment.

How we know: WAPilot operators review this workflow weekly against Meta’s public Cloud API docs — not unofficial blast shortcuts.

What mistakes waste catalog sends?

Sending before sync is healthy, blasting cold lists, dumping twenty SKUs, and ignoring opt-out. Quality rating still applies to commerce traffic.

Inbox home: shared WhatsApp inbox.

Treat this guide as an operations checklist, not a one-time read. Print the ordered steps and assign an owner for each gate before you flip traffic live.

When something fails in production, capture the customer wording, the node that fired, and the Meta-facing symptom before you redesign the whole canvas.

Keep internal links few and intentional — adjacent series posts and the hub beat random keyword stuffing across twenty URLs.

Respect quiet hours and staffing plans. Automation that earns replies without inbox coverage creates the same unread spikes as careless campaigns.

Version names, changelogs, and a fifteen-minute post-publish review prevent mystery drafts from becoming the source of truth.

If quality rating slides after a launch, pause broad triggers first, fix consent and relevance, then warm traffic again on official Cloud API.

Keep these phrases in your team glossary so search and training stay aligned: product cards; agent recommendations; broadcast catalog; browse interest; opt-in sends.

Treat this guide as an operations checklist, not a one-time read. Print the ordered steps and assign an owner for each gate before you flip traffic live.

When something fails in production, capture the customer wording, the node that fired, and the Meta-facing symptom before you redesign the whole canvas.

Keep internal links few and intentional — adjacent series posts and the hub beat random keyword stuffing across twenty URLs.

Direct answer for operators: ship one clear habit, keep a human exit for exceptions, measure what customers actually do, and retest after every material change. Prefer official Cloud API paths over unofficial shortcuts, and staff the shared inbox whenever automation earns replies that need a person.

FAQs

Can I send catalog outside the service window?

Use approved template/catalog message types Meta allows for your use case.

Should every campaign include catalog?

Only when SKUs are visual and current—otherwise relevance suffers.

Who owns pricing mistakes in chat?

The sync owner plus the agent who should spot-check before send.

Does a bot-to-agent handoff reset the window on a shared number?

No. One customer thread, one service window. Two brands on one Cloud API line share that clock — split numbers before you scale support and promos on the same line.

Recap: send catalog with synced cards, opt-in discipline, and human recommendations. When you are ready, start a free trial and grow on official Cloud API.