Stop losing decisions in the team chat

What this module does

An operator on a production order asks a question about a part dimension on a Tuesday: a 2mm clearance versus a 3mm clearance, which one is right. The question goes to the team channel; the planner answers an hour later; the Project Manager weighs in on Wednesday morning; the answer ends up in a thread the operator on the next shift cannot find because nobody knows the channel exists. With the message attached to the production order, the operator on the next shift opens the order and reads the decision and the reasoning underneath, the same place the order lives.

Key pages

A message is a threaded comment that stays with the thing it is about: an item, project, production order, routing line, purchase order or line, sales order or line, or a budget revision. Each is marked internal or external, keeping the team conversation separate from exchanges with a customer or supplier. One message can carry several tags, down to a single routing line within an order, so a discussion about one line does not crowd the whole order's history. Posting from inside a record fills the tag automatically, so the comment lands on the right record without a manual linking step.

Decisions stop disappearing into inboxes. The next operator on the part opens the production order and sees the dimension question and its resolution there, with the time and the author intact. A planner picking the order up sees the customer's clarification at the top of the order, not in a thread someone has to search the team channel for. And the audit question “when was that change to the spec agreed, and by whom” answers itself from the order's own page, not from a person's memory of a conversation in Teams.