What it supports
Send payment details only when the seller has enabled a valid payment method.
Use Case
Payment & Delivery Follow-up
Move customers from product interest to payment confirmation and delivery details with a cleaner flow that supports the seller selected payment method and order status updates.
1
Interest captured
2
Order reserved
3
Payment checked
4
Delivery collected
Cleaner than sending manual account details repeatedly
Sellers can reduce payment mistakes by configuring payment settings once and letting ZoliBot share the correct amount and active payment flow when the customer is ready.
What it supports
Confirm paid orders from webhook information and update the order status.
What it supports
Ask for name, phone number, and delivery address after payment is confirmed.
Order status still belongs to the seller
The AI can mark paid, pending, and confirmed statuses based on the supported flow. Later fulfillment statuses like processing, shipped, delivered, cancelled, and refunded remain manual seller actions.
1
Customer asks for a product or payment details.
2
ZoliBot shares the enabled payment method and creates the order context.
3
After payment confirmation, ZoliBot requests delivery details and updates the chat.
What sellers should expect
This page is written for live businesses using ZoliBot with real customers, real stock, payment decisions, and support conversations that sometimes need a human handover.
Accurate context
The bot should use products, settings, payment choices, and order state from the seller dashboard before suggesting an answer.
Human escalation
Refunds, paid cancellations, fulfillment disputes, and sensitive issues should move to store review instead of unsafe automatic action.
Customer language
Replies should follow the language or informal style the customer is using while keeping prices, links, product names, and order IDs exact.
