Set up Noci AI by talking to your AI assistant
You can set up Noci in a chat. Tell your AI assistant about your team. It asks Noci what is left, then does the work step by step. You stay in charge: nothing changes in Noci until you confirm it.
Paste this into your AI assistant
Help me set up my Noci AI workspace. Read the setup guide at https://noci.ai/skills.md and follow it. Start by asking Noci what is left to set up.
What you need first
Section titled “What you need first”- A Noci workspace, and an admin. An admin does the steps that change who has access and when real alerts page people.
- Your AI assistant connected to Noci. In Noci, open Docs, then AI assistants (MCP). It has the address to add and the steps for Claude, ChatGPT, Cursor and Claude Code. You sign in to Noci once.
- Read and write turned on. Until then your assistant can read your setup, preview changes and hand you links, but it cannot ask for a change. Your assistant gives you a link to turn it on. It is the first step of the list below.
What your assistant does
Section titled “What your assistant does”- Looks at what is left. It asks Noci with
setup_status. Noci answers from your workspace as it is now, so the list is always true. Nothing is remembered between chats. - Gives you a link when a step needs you. Installing Slack, connecting a tool, adding an alert source and inviting people all need a browser or a key.
setup_handoffreturns a link that works for 30 minutes. See Connect your tools. - Prepares one change for the rest. Teams, schedules, escalation policies and routing rules are prepared with
config_planandconfig_propose. You review the whole change at once. See Teams, schedules and escalation. - Proves it works. It sends a test alert and a test page. See Go live.
What you do in Noci
Section titled “What you do in Noci”- Open the links your assistant gives you.
- Read each change and confirm it. Changes with many parts are confirmed in the Noci console, not in the chat.
- Choose the role of each person you invite.
What never goes through the chat
Section titled “What never goes through the chat”- Keys, tokens and passwords. Your assistant never asks for one. The key goes into the secure page your assistant links to, and from there into the connection. It does not pass through the chat, and it is not shown again.
- Phone numbers. Your assistant does not ask for them and does not repeat them.
- Your confirmation. Your assistant cannot confirm a change for you. It gives you a link to the change.
The steps
Section titled “The steps”Noci tracks these steps in order. Each is done, to do, or blocked until an earlier step is done.
| Step | Done when |
|---|---|
assistant_access | AI assistants are set to Read and write. |
slack | Noci is installed in your Slack. |
people | At least two people can sign in. |
teams | There is at least one team. |
schedules | There is at least one on-call schedule. |
escalation | There is at least one escalation policy. |
alert_sources | At least one alert source is on. |
routing | At least one routing rule is active. |
agents | At least one agent has a connection to a tool. |
verify | A test alert has reached a team. |
go_live | Real alerts page people for at least one team. |
If you use another on-call tool today, you do not have to start from nothing. See Convert from PagerDuty.