This page does not answer "which digital workers are available" — for that, see the digital worker lineup. What follows is more concrete: the situations that repeat in an ordinary working day, and how each one ends when an agent handles it.
All seven scenarios are limited to what the platform can actually do today. Where the agent does not do something, that is stated plainly.
The buying question that arrives at 10:30 PM
The customer already likes the product and has one question left: "Do you have this in black, in my size, and when does it ship?" Answer that the next morning and they have bought it somewhere else.
The agent handles the message the moment it arrives:
- It reads product, size, color and stock information from your real catalog. Search is semantic rather than keyword-based, so even "a thick, dark, winter sweater" returns the right products.
- Shipping terms, delivery times and store policies come from your Knowledge Base.
- The answer is generated from your data, not guessed.
Related pages: Smart Catalog, Access Channels.
"Where is my order?" asked dozens of times a day
Every answer costs the same routine: open a panel, enter the order number, read the status, copy the tracking code, paste it into the message.
The agent closes that loop inside the conversation:
- It queries order status, line items, carrier and tracking number from your order system in real time.
- If you sell on Trendyol, order list and order detail queries run directly against Trendyol; on the seller side, settlements, financial records and cargo invoice items can be queried too.
- Tools that return personal data can be placed behind one-time SMS code verification if you want.
Related pages: Integrations, E-Commerce Sales Agent.
A customer spread across three inboxes
A message waiting on WhatsApp, a question sitting in Instagram DMs, a chat window on the website nobody is watching. Same questions, three different places.
A single agent runs across six channels: WhatsApp, Instagram, Messenger, Web Widget, Web Page (Standalone) and Robot. System prompt, knowledge base, catalog and tool set are shared across channels — you do not build a separate agent per channel.
One limit stated plainly: what is shared is configuration and knowledge, not conversation history. If the same customer writes on WhatsApp and later moves to the widget, two separate conversations are created; it is the same agent, but it does not remember the previous channel's thread.
WhatsApp, Instagram and Messenger are text channels. Voice is available on Web Widget, Web Page and Robot.
Related page: Access Channels.
A return or exchange request
This one needs to be stated precisely, because the industry usually oversells it.
The agent does not start the return process. What it does:
- It turns the return or exchange request into a structured case record and routes it to the right team, so the customer does not have to explain the same thing twice.
- If you sell on Trendyol, it queries the list, status and detail of return claims that already exist and tells the customer where the process stands.
- The decision, the approval and the return itself stay with your team.
Related pages: Integrations, E-Commerce Sales Agent.
The abandoned cart and the campaign nobody heard about
Some conversations are not started by the customer — you are the one who should start them. Following up on an abandoned cart, winning back a customer who has gone quiet, announcing a limited-time campaign to the right customers.
The agent does this with ready trigger templates: cart abandonment reminder, silent customer follow-up and campaign reminder ship with the persona.
One detail matters: these templates are off by default. During setup the suggested triggers are shown to you, and you activate the ones you want with a single click. The agent does not message your customers without your knowledge.
Related page: Smart Automation.
The conversation the agent cannot resolve
Not every conversation ends with AI. The customer describes an edge case, is upset, or simply asks for a person.
- The agent transfers the conversation to a human operator in one click; conversation context is preserved and the customer does not notice the switch.
- The handoff notification reaches the operator immediately.
- You define business hours and can set up a separate flow for conversations that arrive outside them.
Related pages: Live Support, Customer Support Agent.
Which digital worker runs these scenarios?
None of this has to sit in a single agent. In Giizo AI you pick a persona that knows your vertical; behavior rules, tool set, knowledge-base templates and suggested triggers arrive pre-configured.
Which persona takes over which job — and the primary metric each one is measured by — is on the digital worker lineup page.
If your situation has no match in the catalog, you can build a custom agent from scratch on the same knowledge base, integration, multichannel and proactive trigger backbone.
Pick a persona → connect your data → open a channel. Live in 5 minutes.