Keep a customer exception where it will be found
Use the Wiki to preserve a customer promise with its source, scope, and owner.
Outcome
Sales, dispatch, and customer service can find the same current promise before acting.
Main feature: Wiki
The situation
Acme Retail’s warehouse accepts deliveries only on Tuesdays. A salesperson promised that dispatch would call Anita two hours before arrival. The promise was made on a call and does not belong in an invoice line.
Before you start
Confirm the customer, site, person, and dates. Decide whether the exception is permanent, temporary, or tied to one order.
Create or update the page
- Open Skills > Wiki and search for Acme Retail.
- Open the existing customer page or choose New page.
- Add a section called Delivery exception.
- Write: “Deliver only on Tuesdays to the Peenya warehouse. Dispatch calls Anita two hours before arrival. Owner: South region account manager. Confirmed on 18 July 2026 from the customer call note.”
- Set the scope so the roles that need the fact can see it.
- Add the source and a review date.
- Save, then search again as a normal user to confirm it can be found.
Keep it trustworthy
If a later note says Thursday deliveries are now allowed, do not leave two competing instructions. Resolve the conflict, keep the newer source, and preserve the history appropriately.
Archive the page when the relationship ends but the history may matter. Delete only when the knowledge must be removed permanently.
Done when
The page names the exact exception, location, responsible person, source, and review date. Jarvis can cite it, and the teams who act on it can find it.
Write the exception so a person outside the original conversation can act correctly. “Special delivery rule” is not enough.
Use it again
Use Business Notes to capture facts quickly, then use the Wiki to check and maintain the shared version.