Arcus documentation

Install the desk, sign in, and get a cited root cause on a real ticket. No connector needed to start.

What connects today, how to connect it, and what is not there yet.

Each org picks the one AI provider that receives its data. Optional: use your own API key.

Create the Zendesk OAuth client (or API token), paste it into Arcus, sign in, and see your Cases queue.

Connect Jira for the queue and for File bug. Email + API token works today; org OAuth is optional.

Connect a ServiceNow instance for incidents, work notes and first response.

Connect Salesforce cases for the queue, first response and Insights.

Index a local checkout and optionally connect GitHub so answers cite real files and lines.

Add Grafana, Loki, Prometheus, Datadog or other MCP tools so investigations can query real telemetry.

Counts, queue, checklist and the search box that starts every investigation.

The Cases sidebar lists tickets assigned to you across connected helpdesks, with refresh and ticket cards.

What Arcus reads, how it reaches a root cause, and how to check its work.

Open the exact file and line Arcus cited, without leaving the case.

Draft a reply, run the reply check (verifier), and only then post when external posts are on.

Turn the investigation into a bug draft. Copy puts it on the clipboard. Created means the tracker accepted it.

Turn a resolved case into a help-center draft, review it, and publish only after you approve.

Transcribe the customer call you are already on and investigate while you talk.

Your team’s confirmed fixes come back the next time the same symptom shows up.

How Arcus checks for new desktop builds and what to do when an update is available.

Fixes for the problems people hit most.

Short answers to common questions.

Where to find the security overview, the DPA and the subprocessor list.

Install Arcus and get past Gatekeeper on unsigned Mac builds.

Sign in on the website, then open the desktop app with the same account.

What you need to run the desktop desk.

An internal note on every new Zendesk or ServiceNow ticket within seconds, and a guarded public reply draft.

Find related Jira issues and Slack threads, link them both ways, and escalate with approval.

Time to breach from your Zendesk and ServiceNow SLA policies, with warnings before a breach.

Leave keeps a draft. Finish & save writes the finished session you can open again.

The ticket list from Jira or Zendesk. Public Jira Service Management portals are not supported.

Send the case to engineering on Slack, Linear, GitHub, Jira, or email. Arcus does not page anyone by itself.

Microphone and Screen Recording on Mac.

Names and roles for each speaker, with a confidence and a review flag.

You stay in Zoom, Meet, or Teams. Arcus listens on this desk.

Local folders in Settings → Indexing. Snippets leave when you Ask.

Ask in natural language against the local index.

Whatever is in the local folder you allow — common source and config.

Local paths and tokens you control. Least privilege.

Ask Arcus is a panel in Investigate and Live Call.

Exact Atlassian developer console fields so Sign in with Jira uses your org’s 3LO app.

Copy these Zendesk Admin Center fields into the three Arcus boxes.

Exact redirect URLs. No trailing slash. arcus:// is only the desktop handoff.

Search threads you can see, link them to tickets, and ping owners with approval.

Optional Google Calendar briefs on Home.

Exactly how each team and personal Insights number is calculated.

MCP servers live in desktop Settings → Tools & MCP.

macOS banners and case alerts. Dev builds may show as Electron.

Desktop Settings: Integrations, Security, Indexing, Tools & MCP.

See Settings → About in the app for the live list.

History, drafts, and index live on the machine.

The repository index stays on your machine. A snippet is sent only when you ask.

You remain in control of customer-visible text.

How sign-in works today, and where SSO stands.

Review connectors and retention with your security team. No badge sold here.