What Is Postback Manager in ZazzyAgent?
A customer can start a conversation by typing a message.
But they can also interact by clicking a button, quick reply or other interactive element.
What happens when they click it?
That's where Postback comes in.
ZazzyAgent's Postback Manager lets you create reusable responses/actions that can be triggered by customer interactions.
What is a postback?
A postback is an event generated when a customer interacts with a supported interactive element.
For example:
Customer taps Book Demo.
The interaction can trigger a predefined postback.
That postback can then start the configured response or flow.
Why use postbacks?
Suppose you have several places where you want a:
Book Demo
button.
Instead of creating completely separate logic for every button, you can create a reusable postback that represents:
Start Demo Booking.
Then multiple interactive elements can call the same postback.
Postback vs Bot Reply
These solve different problems.
Bot Reply
Usually starts from a message/keyword trigger.
Postback
Starts from a customer interaction with an interactive element.
Example
Customer receives:
What would you like to do?
Book Demo
Pricing
Support
Each button can be connected to a corresponding postback.
Book Demo
↓
Demo Postback
↓
Demo Flow
Pricing
↓
Pricing Postback
↓
Pricing Flow
Support
↓
Support Postback
↓
Support Flow
Why make postbacks reusable?
Imagine your bot has:
Main Menu
Welcome Message
Pricing Message
Sales Message
Follow-up Message
You may want all of them to contain:
Talk to Sales
A reusable postback means you can connect that action to the same underlying response.
Open Postback Manager
For supported connected channels, open the bot's Postback Manager.
The exact navigation depends on the channel configuration.
Create a postback
Create a new postback.
Give it a descriptive name.
For example:
book_demo
or:
contact_sales
Avoid:
postback1
The name becomes important when many interactive actions exist.
Configure the response
A postback can lead into a configured response/flow.
Depending on the supported channel and configuration, this can involve:
Text
Buttons
Images
Galleries
Flows
Other supported responses
Connect a button to the postback
Once the postback exists, configure your button or supported interactive element to use that postback.
The customer doesn't see the internal postback name.
They see:
Book Demo
When they tap it, the associated action runs.
Example: Main menu
Main Menu
↓
[Services]
[Pricing]
[Book Demo]
[Support]
Each option can use a different postback.
Postbacks and Flows
A postback can launch a larger Flow.
Example:
Book Demo
→ postback
→ Demo Flow
The Demo Flow can then collect:
Name
Email
Company
Preferred date
This keeps the button logic separate from the larger conversation.
Postbacks and User Input
A postback can also lead into a User Input process.
Example:
Customer taps:
Get Quote
↓
Postback
↓
User Input
↓
What's your name?
This is a useful combination for lead-generation workflows.
Postbacks and sequences
A button interaction can also become the beginning of a follow-up journey where supported.
For example:
Get Updates
→ Postback
→ Start sequence.
Postback names should describe intent
Good:
book_demo
request_quote
talk_support
Poor:
action1
button2
Useful naming helps you manage the system later.
Postbacks vs direct flow connections
You don't need a postback simply because you have a button.
Use one when a reusable interaction is useful or when the channel's interactive element architecture calls for it.
For a simple one-off flow, a direct connection may be enough.
Channel differences
This is important.
Postback behavior isn't identical across every ZazzyAgent channel.
Postback Manager is for Facebook, Instagram and WebChat, while WhatsApp and Telegram do not have the same Postback Manager setup.
So don't assume that a Postback article applies identically to every channel.
Test the interaction
Test:
Customer receives button.
Customer taps button.
Postback fires.
Correct response starts.
Correct flow continues.
Common problems
Button does nothing
Check the button's postback assignment.
Wrong flow starts
Check which postback the button is connected to.
Postback works in one place but not another
Check whether the second button is actually using the same postback.
Postback isn't available
Check whether the connected channel supports the Postback Manager feature.
Reusable interaction architecture
Interactive Element
↓
Postback
↓
Reusable Response
↓
Flow / Action
Postbacks are most useful when you want to separate:
what the customer clicks
from:
what your automation should do.
That separation makes complex interactive bots easier to organize and reuse.