E-commerce
June 30, 2026
A custom-made product is not sold in the same way as a standard product. The customer has an idea, sometimes very precise, sometimes still vague. They want to know if the brand can do it, how long it will take, and what information to provide.
The chatbot can qualify the request without replacing human expertise. It must understand the need, gather key constraints, and hand over an actionable brief to the sales or production team.
This guide explains how an AI chatbot can help qualify a custom project without frustrating the customer.
Summary
Why does custom manufacturing require progressive qualification?
The customer does not always have all the details at the beginning. They may know the use, but not the dimensions. They may have an inspiration, but not the material. They may want a short turnaround time without knowing if the manufacturing allows it.
The chatbot must ask the right questions in the right order. It must not turn the conversation into a long form from the very first message.
A good custom chatbot helps the customer formulate their project before talking about price.

Convert over 2,000 customers on average per month with Qstomy.
The world’s 1st Shopify AI dedicated to customer conversion



Empowering 200+ e-commerce merchants
What information should be collected?
The bot must collect the usage, dimensions, quantities, materials, preferences, technical constraints, indicative budget, desired timeframe, and files or inspirations if the process allows.
It must also ask if the project is personal, professional, event-related, or recurring. This information changes the priority and the level of detail expected.
How to talk about feasibility?
The bot can explain that an initial qualification does not equal final validation. It can say: "Based on your information, the project seems worth studying. The team will need to confirm the feasibility and the timeframe."
This caution prevents promising impossible manufacturing or an unrealistic deadline.
How to manage deadlines?
The lead time often depends on the validation of the brief, production, materials, quantities, and delivery. The bot must explain these steps rather than giving a date too quickly.
If the client has a deadline, the chatbot must collect it early. A project for an event is not handled the same way as a desire without urgency.
This information also helps avoid unnecessary exchanges. If the requested deadline is impossible, the team can propose an alternative or politely decline before preparing a detailed quote.
What to do with the budget?
Budget can be a sensitive topic, but it helps guide the request. The bot can ask for an indicative range and explain that it is used to propose a realistic solution.
It must not give a final price if the quote depends on human validation. It can prepare the necessary elements for the costing.
Which flow to follow?
The flow must transform an idea into an actionable brief.
Understand the use and the objective of the project.
Collect dimensions, quantity, preferences, and constraints.
Identify deadline, indicative budget, and level of urgency.
Explain what remains to be validated by the team.
Transfer a clear summary for quote or feasibility.
Which messages should be used?
To start: "I can help you prepare the request. What use do you want to make of the custom product?"
For the deadline: "Do you have a deadline? This will allow the team to check if manufacturing is realistic."
For the quote: "I am forwarding this information so that the team can confirm feasibility, deadline, and price."
When to transfer?
The transfer is necessary as soon as the project requires a quote, technical feasibility, an exception, a professional volume, or production validation.
The bot must transmit the brief, constraints, any files, budget, deadline, and client contact details.
Which KPIs should be monitored?
Track qualified requests, complete briefs, created quotes, projects rejected due to feasibility, deadlines that are too short, and post-quote conversions.
This data indicates whether the chatbot is collecting the right information or if the team still has to follow up too often.
Which mistakes should be avoided?
Avoid promising a price, a deadline, or feasibility without validation. Also, avoid asking for too much information before understanding the objective.
The chatbot should facilitate the brief, not decide on the project by itself.
How can Qstomy help?
Qstomy can use the customer, cart, and order context to answer clearly, then hand over sensitive cases with an actionable summary.
The chatbot simplifies complex questions without creating promises that the brand cannot keep.
Explore AI support, the AI sales agent, or request a demo.

Enzo
June 30, 2026


