Skip to main content
Ninety runs your business on EOS: each Team’s To-Dos, Issues, Rocks and weekly Scorecard, worked in the Level 10 Meeting. Connect Ninety once with a Personal Access Token, and Neo agents can read and update it next to your PSA.

​
What Neo can do with Ninety

  • Close the loop on To-Dos. Complete a To-Do once the PSA ticket it tracks closes, and comment on a To-Do whose ticket is still open past its due date.
  • Turn recurring ticket pain into Issues. Group the tickets that share one cause, and raise one Issue per group on the Team you name, or comment on the Issue that already covers it.
  • Make PSA tickets and projects from Issues and Rocks. Open one PSA ticket for each Issue you select, or one project for a Rock, and write the ticket or project number back on the Issue or Rock.
  • Fill in the weekly Scorecard. Count the week’s numbers in your PSA, such as tickets closed, and write the scores for the Measurables you map.
  • Answer questions about your Rocks, Issues, Headlines and Meetings in a chat agent.

​
How the jobs run

Each job above is a scheduled agent with the Ninety IT Admin profile (or Helpdesk, to approve each change) and your PSA’s ticket permissions. Its instructions say which Teams it works on and how it counts, for example:
Neo ties each Ninety item to its PSA record with a short line on both sides (PSA ticket <number> in Ninety, Ninety Issue <id> in the PSA), so a later run finds the tie and never makes a second record. The quickest way to set one up is to ask the Neo Support Agent: “Set up a weekly agent that fills in our Ninety Scorecard from Autotask.” See Ninety API for the permission groups.

​
Next steps

Connect Ninety

Make a Ninety Personal Access Token and save it in Neo.