Clarifications
Answer the questions Kabaido raises when information is missing, and watch the structured result update.
When a request leaves something out or reads two ways, Kabaido raises a clarification rather than guessing. This is how it stays honest about what the customer actually said.
Where clarifications appear
Missing attributes are listed against the line they belong to in the structured table. Where an answer is needed to price or configure a line, Kabaido shows a short form in the chat with just the fields it needs, such as a number, a choice or a yes or no.
Why a question rather than a silent default
A silent default is a guess wearing a uniform. If a request says "12mm end mills, 100 off" and never states a coating, filling in the most common coating gets it right most of the time, which is exactly what makes the wrong ones dangerous: the quote reads as confident, nobody re-checks it, and the mistake is found by the customer. Putting the gap where somebody will see it, before the price is committed to, is what keeps that from happening.
The same rule is why the clarification names the line it belongs to. A request with fourteen lines and one missing tolerance should not become a general question about tolerances.
What Kabaido will settle for you, and how you see it
Some gaps have a defensible answer, and leaving those open helps nobody. Where your own order history, the customer's own details or a published engineering norm settles a parameter, Kabaido fills it and marks it assumed on the line, with the basis and the source it stood on. A quantity nobody stated is settled at one off, so the line can be priced and drafted rather than stopping the whole answer on the commonest omission in industrial buying.
Nothing about this is quiet. An assumed value carries a dashed amber chip on its line, it says assumed on the draft, and every assumption the answer made is listed again in a closing note at the end of the response, so you read them as a set before you reply to the customer or press create. Change any of them in one tap, or ask the customer instead, and the line resolves again.
The line between the two is the one that matters: a specification, tolerance, price or part number is never assumed. Those are the customer's to state, and a missing one is always a question.
Answering them
- Read the question and the line it relates to.
- Fill these in on the line, or reply in the composer.
- Submit, and Kabaido resolves that line again with your answer.
The form is built from what the line is actually missing, one field per open parameter, with the ones the question asked about first. Answer what you know: anything you leave blank simply stays open.
You can also answer on the customer's behalf. Most of the time you will: the buyer said it on the phone, or it is obvious from the last order they placed. Kabaido does not need the answer to come from the person who sent the enquiry, only for the answer to be recorded rather than assumed.
When to ignore one
A clarification is not a blocker. A line held back for a missing value still appears in the structured table with everything that was stated, and you can quote around it, price it manually or leave it out. Answering the clarification is what lets Kabaido price it for you; declining to answer costs you that, and nothing else.
Your answer updates the structured result in place. A line that was held back for missing information can then be matched, configured or priced. The request history is kept, so earlier states are never overwritten.
Clarification forms are one round. If more is needed after that, the card points you to open the line in the relevant module.