First-time setup
A checklist, in order, to get your first platform investigating real tickets.
This checklist takes you from an empty organisation to your first investigated ticket. You need to be an owner or admin for every step.
The Queue keeps track for you
Until the basics are done, an amber Finish setting up card sits at the top of the platform's Queue. It shows which steps are left, in the order they can be done, with a link to each. Step by step opens the Get started guide, where you can do most steps on one page.
The checklist#
- 1
Add your keys. Go to Organisation › Keys and add a Claude API key, so the agent can think. If the agent should read code, add a GitHub or GitLab key too. Exact steps for each are in Keys.
- 2
Create a platform. A new organisation already has its first platform. For another one, go to the Overview and click Add platform. Give it the name your team uses for the system, then click Create. You land on its Get started page. See Platforms.
- 3
Choose the agent's key. In Settings › Agent, in the AI key row, pick your Claude key. While you're there, fill in About your system and How replies sound. Then click Save. See Agent settings.
- 4
Connect what the agent can look at. Any one is enough, and many platforms have no code at all. For code: in Settings › Code, click Add repository for each repository the agent should read, choose GitHub or GitLab, and pick the key it reads with. The Status column shows whether the key can read it. To check again, use Check access in the repository's ⋯ menu. See Repositories.
- 5
Instead of code, or as well: in Settings › Live system, connect your Kubernetes cluster and Loki logs; in Settings › Databases, add read-only database logins; in Settings › Microsoft 365 and Google, connect the client's Microsoft 365 or Google Workspace; in Settings › Domains and websites, connect GoDaddy or Cloudflare. The more it can look at, the better its answers. See Kubernetes access, Loki logs and Databases.
- 6
Decide where tickets come from. Connect HaloPSA or your own ticket system under Settings › Ticket system, or switch on the Log watcher to turn errors in your logs into tickets. You can use both. See Ticket system and Log watcher.
- 7
Set up notifications (optional). Add a Telegram chat or Slack channel under Organisation › Notifications. Then switch on what this platform sends to it under Settings › Notifications. See Notification channels and Platform notifications.
- 8
Invite your team. Click Invite under Your account › Team for each person who'll review replies. Give them the Approver role. See Members and roles.
- 9
Send a test ticket. Send a real ticket from your ticket system, or wait for the log watcher's first check (within 5 minutes). Watch it appear under The agent is working on in the Queue, then under Waiting for you.
Things that are off until you choose them#
You don't need these to start. Each one stays off until an owner or admin switches it on.
- Automatic replies. Every reply waits for a person by default. See Automatic replies.
- Code fixes, database changes and cluster changes. See Changes and terms and Allowing changes.
- Chatbots. See Chatbots overview.
If the test ticket fails
Open the ticket. At the top, Now says The agent couldn't finish, and explains why in plain words, with Technical details underneath. The most common causes are a missing Claude key or a repository the key can't read. See Common problems.