In electronics the customer's question is not "do you have it?" but "will it work for me?" The graphics card sits in the basket, but will the power supply handle it, will it fit the case, will it work with the motherboard — and the only person who can answer that is the most technical person in the shop, who is also dealing with suppliers, service and the warehouse. Every answer already sits in the product description and the comparison guide; the problem is time to information.
The compatibility question and the lost sale
- "Will these headphones work with an iPhone?"
- "I have an RTX 4060 — will this monitor struggle at QHD?"
- "What's in the box, is the cable included?"
- "How long is the warranty, and is the panel covered separately?"
- "Will I have it tomorrow, how many are in stock?"
- "If it arrives faulty, what do I need to do?"
One compatibility question, a three-day decision
The higher the basket in electronics, the longer the decision takes. Nobody buys an eight-thousand-lira monitor in the first minute they see it; tabs stay open, forums get read, two models sit side by side for days. At every step of that process a single unanswered technical detail pushes the decision one more day out — and within that day another shop lists the same product at the same price.
After the sale a second and entirely separate workload begins: warranty scope, routing to technical service, fault reports. Those messages come from people who have already bought, and they land in the same inbox as pre-sale questions. Which one gets answered first is a decision made again every day.
When the technical question stops drifting
- Compatibility and box-contents questions are answered from the product record while the customer is still on the page, so the decision does not spread over days
- The difference between two models is read from the comparison text you wrote, not explained again to everyone who asks
- On a technical point it is unsure about, the agent does not guess: it will not say what the record does not say, and brings the conversation to your technical team
- Warranty and fault messages do not pile up in the same inbox as pre-sale questions; they become a request record and land with your team
- You make the call: exchanges, service and exceptions stay with you
What the agent does in technical sales
- Pulls suitable models from the catalogue when a customer describes their need
- Relays specifications, box contents, stock and price from the product record
- Explains the difference between two models from the comparison text you wrote
- Answers warranty length and shipping terms from your knowledge base
- Opens a request record when a customer reports a fault or asks for a return; the record lands with your team and you make the decision
- Hands the conversation to you when it cannot decide
A customer comparing models
Thursday, 11:30, on-site chat.
Customer: I'm after a 27" monitor for gaming. Do you have anything at 165 Hz?
Agent: There are two models in the catalogue: a 27" QHD 165 Hz IPS (8,750 TL) and a 27" FHD 180 Hz VA (6,290 TL). The first is 2560×1440, the second 1920×1080. Both are in stock.
Customer: I have an RTX 4060 — will it struggle at QHD?
Agent: Our product descriptions don't include performance information, so I can't say for certain. Our comparison guide lists the recommended use case for the QHD 165 Hz model as "mid-to-high tier graphics card". I can pass this to our technical team if you'd like them to come back to you.
Customer: Yes please. And how long is the warranty?
Agent: Both models carry a 3-year manufacturer warranty, with 2 years on the panel. Orders placed before 16:00 ship the same day.
The two questions the record could answer closed on the spot; the one it could not was handed on rather than invented.
Where the specifications come from
The agent does not search by keyword but by meaning, so a description like "quiet case fan without RGB" still reaches the right record. For that to work, the products have to be in the Giizo catalogue.
The catalogue is fed by hand in the panel or with Giizo's own Excel template.
Compatibility tables, installation guides and comparison articles go into the knowledge base, not the product record. The split is simple: the product itself lives in the catalogue; the rules and tables about the product live in the knowledge base.
Orders from the system, not a guess
Most post-sale traffic is a single question: where is my order.
If your store runs on CS-Cart, the agent pulls the order detail and the shipments from the system. It asks for a one-time code so the customer only sees their own order.
If you sell on Trendyol, you query orders, return claims and financial records through the Giizo AI Business Assistant in the panel.
The technical question asked on the product page
Technical questions are usually asked while the customer is still on the product page, through the website chat widget — that is where reading the specifications gets stuck. Post-purchase messages drift to**WhatsApp**, which in Turkey is the working address for shipping, invoice and fault conversations. The same agent works on Instagram and Messenger with the same comparison texts.
Setup for an electronics store
The ready-made digital employees behind this work: Ecommerce Sales Agent and**Customer Support Agent**.
How product data is handled is on Smart Catalogue; where compatibility tables belong is on knowledge base.
To try it with your own catalogue, start free.