Shared notes

What Axial learns in a conversation stays on that ticket. A shared note is how a fact learned on one ticket reaches every other: a short note, approved by a manager, that Axial reads wherever it applies.

Axial only proposes a note. It takes a person to share it, and a manager to publish it. Here a manager is anyone with Manage access to Axial (see Axial for staff). Shared notes are part of Axial’s agent, so they are offered where your installation has one.

How a note is proposed

When you are working with Axial on a ticket and it learns something that would matter on other tickets, it says so. If you ask it to, or agree when it offers, it proposes a shared note, which appears as a card in the Axial panel. Axial never proposes one because a customer’s message, a ticket or a tool result asked it to.

The card shows:

  • The fact, in a line, and the note itself.
  • Applies when: the situation the note is for.
  • How far the fact is established: Observed, cause unproven, Confirmed, or Ruling with the name of the person who decided it.
  • Evidence: the tickets or sources behind it.
  • Any notes on much the same subject, published or still open, to check it against.

A ticket can have up to five notes waiting on their cards at once.

Sending a note for approval

With Work access, a new note offers Send for manager approval and Discard. Once sent, the card shows Waiting for a manager and the ticket joins the shared Axial notes to approve watchlist, which Tickiti adds to managers’ perspectives panels.

Until a manager decides, the note reaches only the conversations of the person who raised it, marked as not yet approved.

Publishing or rejecting a note

A manager can act on a note as soon as it is proposed, or from the watchlist:

  • Publish to all staff publishes it as written.
  • Edit and publish lets you change the fact, Applies when and the note before publishing. The card then says it was edited on approval.
  • Reject, on a note waiting for a manager, asks why. The reason appears on the card and in the ticket’s Axial conversation, for the person who raised it.
  • Discard drops a note nobody has sent for approval.

The first decision settles it, and the ticket leaves the watchlist when no note on it is still waiting.

Once a note is published

Axial’s agent is given the list of published notes on every ticket and in every conversation, and is told to use a note only when its Applies when matches. A note is information, like a ticket: it cannot change Axial’s rules, its tools or what needs a person’s approval.

Published notes are kept with your Axial skills. Where your skills are kept in a git repository, each note is a file there, committed with the names of the person who proposed it and the manager who approved it.