Message labelling
How each message is typed, and when a reply puts work back in the queue.
Two judgements, often mixed up:
| Judgement | Question | Effect |
|---|---|---|
| Type | What is this commercially? | Enquiry, purchase order, order acknowledgement, revision, other |
| Technical impact | Does this change what we would quote? | Whether the conversation goes back in the processing queue |
A thread titled “RE: Enquiry” whose body is a debit note is not an enquiry (R5). The newest message sets the conversation’s type until a person corrects it; that correction is never overwritten (R6).
Type does not decide whether a conversation is processed. A customer revising a requirement on a thread that has already become a quotation or an order must not vanish from the queue.
Technical impact (R10): “please send the flow curve” leaves the reading alone. A revised size, pressure, material, quantity or model re-processes. When the judgement cannot be made, it is processed — missing a real requirement is worse than re-reading.
When the labelling service cannot be reached, the message is treated as an enquiry (R7) so an RFQ is never hidden by an outage.
Related: Inbox · Business rules.