What Is WhatsApp Catalog in ZazzyAgent? Complete Guide
A WhatsApp Catalog lets your business present products directly inside a WhatsApp conversation.
Instead of manually sending:
Product photo
Product name
Price
Description
one message at a time, you can connect a Meta/WhatsApp catalog to ZazzyAgent and use it inside your automated conversations.
Customers can browse products and interact with them directly from WhatsApp.
What is the Catalog?
A catalog is a collection of products managed through Meta's commerce tools and associated with your WhatsApp business setup.
A product can contain information such as:
Product name
Product image
Description
Price
Product identifier
Other catalogue information
ZazzyAgent can use the connected catalog inside supported WhatsApp automation.
Why connect a catalog to ZazzyAgent?
The catalog gives your chatbot access to a structured product presentation.
For example:
Customer:
Show me your products.
Your flow can display:
Product A
Product B
Product C
The customer doesn't have to ask for each product separately.
Catalog vs images
You could simply send product images.
But an image is just an image.
A catalog product contains structured product information that can be presented through WhatsApp's commerce experience.
That's useful when customers want to browse actual products rather than look at a collection of unrelated images.
Catalog vs Carousel
These are different features.
Carousel
You manually configure cards in the flow.
Each card can contain content and an action.
Catalog
Products come from your connected WhatsApp catalog.
This makes catalog particularly useful when your products are already maintained in Meta's commerce environment.
Where does the catalog come from?
The catalog is managed through Meta's commerce infrastructure.
ZazzyAgent connects to the appropriate WhatsApp/Meta business setup and can then use the catalog in supported flows.
You don't normally create every product again inside every bot flow.
What does ZazzyAgent do?
ZazzyAgent gives your automation a way to use the catalog inside a customer conversation.
For example:
Customer
↓
ZazzyAgent Flow
↓
Catalog
↓
Products
↓
Customer selects product
When should I use a catalog?
A catalog works well when customers need to browse products.
Examples:
Clothing
Electronics
Furniture
Food products
Beauty products
Accessories
Consumer goods
It can also be useful for services or offerings that can be represented as catalog items, depending on your business setup.
Do I need a catalog before using the Catalog component?
Yes.
The Catalog component needs a connected catalog to display products.
You should first make sure your WhatsApp catalog exists and contains the products you want to show.
The current setup documentation requires the catalog to be created before connecting and using it in a flow.
Can I show every product?
You can configure the catalogue experience to show the products or product sections appropriate for the flow.
You don't have to send your entire product catalogue every time.
For example:
Customer asks about shoes.
Your flow can present the relevant products rather than unrelated items.
Single product vs multiple products
The Catalog component supports selecting individual products as well as using a multiple-products configuration.
Single product
Useful when:
Customer asks about one specific product.
Multiple products
Useful when:
Customer wants to browse several options.
The current flow configuration supports both individual and multiple-product selections.
Example: Product enquiry
Customer:
Do you have running shoes?
Your flow can display relevant products from the connected catalog.
The customer can then explore the available product information.
Example: Product menu
Your flow could begin:
What are you looking for?
Shoes
Clothing
Accessories
Customer selects:
Shoes
↓
Show relevant catalog products.
This keeps the initial conversation simple.
Catalog and AI
The catalog can also work alongside an AI Agent.
For example:
Customer:
I'm looking for a black running shoe under ₹5,000.
The AI can understand the customer's request.
Your workflow can then guide the customer toward relevant product information or catalog content where your configured setup supports it.
The catalog provides the structured product data; the AI provides conversational understanding.
Catalog and Flow Builder
A common architecture is:
Trigger
↓
Interactive Message
↓
E-commerce / Catalog
↓
Products
The current Flow Builder reference uses an Interactive Template and then connects its ecommerce socket to the Catalog component.
Catalog information should stay in the catalog
Don't manually copy every product's:
Name
Price
Image
Description
into dozens of different bot flows.
Whenever possible, maintain the product information in its proper catalog source and use the catalog inside the flow.
This makes product management much easier.
What happens when a product changes?
For example:
Product price changes from ₹999 to ₹1,099.
The correct place to maintain that product information is the catalog.
You shouldn't need to rebuild every flow that references the product simply because the product information changed.
Catalog is not the same as a flow
Remember:
Catalog
= product data.
Flow
= conversation logic.
Catalog component
= the point where your flow presents catalog content.
This separation is important.
Catalog is not the same as the AI
The AI decides how to converse.
The catalog contains structured product information.
They can work together, but they serve different purposes.
A useful architecture
Product Information
↓
Meta Catalog
↓
ZazzyAgent
↓
Flow Builder
↓
Customer
Once you understand that relationship, configuring catalogue-based automation becomes much easier.