Approvals and answers where your team already works

Supported actions

Intake, ticket-question answering, approval decision cards and notifications inside your workspace.

Approvals & visibility

Internal, operator-facing surface. Chat approvals require a verified, elevated Slack identity.

Plan

All plans

Limitations

Not a customer-visible reply channel — customer replies go out via your helpdesk.

Supported actions

Intake, ticket-question answering, approval cards (Adaptive Cards) and gate decisions.

Approvals & visibility

Internal, operator-facing surface. Chat approvals require a verified, elevated Teams identity.

Plan

Team and above

Limitations

Mirroring run progress back into Teams threads is planned; some surfaces are newer than their Slack equivalents.

Supported actions

Two-way ticket sync, AI-drafted replies, status and priority updates, progress notes.

Approvals & visibility

Customer-visible. Every reply passes reply-safety checks and a recorded human approval before send.

Plan

Starter (as your one helpdesk) or Team and above

Limitations

Replies send from your own support address through the governed outbox — retry and dead-letter included.

Supported actions

Issue sync, internal comments, transitions, and an inbound status-sync webhook.

Approvals & visibility

Internal-only: FixControl posts internal comments, never customer-visible content, on Jira Software issues.

Plan

Starter (as your one tracker) or Team and above

Limitations

Customer-visible replies require Jira Service Management (separate row).

Supported actions

Customer-visible replies on Jira Service Management customer requests.

Approvals & visibility

Four gates, all required: a configured request type, a healthy customer-reply capability, a reply-safety pass, and a recorded human approval.

Plan

Team and above

Limitations

Only where configured; when any gate fails the reply falls back to an internal comment.

Supported actions

Ticket create and link, two-way status sync, AI-drafted replies, internal progress notes, and an inbound webhook; resolved Odoo tickets serve as evidence for support answers.

Approvals & visibility

Customer-visible. Every reply passes reply-safety checks and a recorded human approval before send.

Plan

Starter (as your one helpdesk) or Team and above

Limitations

Customer replies land in the ticket's conversation through the governed outbox — retry and dead-letter included; internal notes stay internal.

Supported actions

Incident create and link, status read-back, AI-drafted replies, internal progress notes with pull-request links, and an inbound webhook; the caller on the incident links the customer, and resolved TOPdesk incidents serve as evidence for support answers.

Approvals & visibility

Customer-visible. Every reply passes reply-safety checks and a recorded human approval before send; internal notes stay invisible to the caller.

Plan

Starter (as your one helpdesk) or Team and above

Limitations

Inbound updates come from an Events & Actions HTTP action you configure in TOPdesk, and FixControl reads the incident back over the API before acting on it. Progress-note sync, status push on resolve and the customer reply are separate opt-in toggles, off by default. Attachments are not synced.

Supported actions

Read-only HR data for governed answers: remaining leave hours with an as-of date and a payroll explanation code, read from GetConnector views you define with prescribed field ids.

Approvals & visibility

Nothing is written back. An answer about an employee's own situation is a draft until an assigned reviewer and a second approver decide on it.

Plan

Confirmed during onboarding

Limitations

Every call filters on one person and projects onto the named fields — never a salary amount or a payslip document. One connection check per connection; a missing employee record routes that one question to a person instead of colouring the connection red. Credentials and the projects that may use them are set up with us; there is no self-service connection form yet.

Supported actions

Read-only HR data for governed answers: remaining leave hours with an as-of date and a payroll explanation code, read from the Youforce domain-API endpoints you expose.

Approvals & visibility

Nothing is written back. An answer about an employee's own situation is a draft until an assigned reviewer and a second approver decide on it.

Plan

Confirmed during onboarding

Limitations

Endpoint templates must stay on the base URL's host over https, or the request is refused before it is made. The connection check forces a token refresh, so it proves the credential and not that every endpoint template resolves. Credentials and the projects that may use them are set up with us; there is no self-service connection form yet.

Supported actions

Repository analysis, pull-request delivery of approved changes, PR comments, webhook events.

Approvals & visibility

Pull-request-only delivery — merging stays a human action in your review flow.

Plan

Pro and above

Limitations

Never pushes to a default branch.

Supported actions

Repository analysis, merge-request delivery of approved changes, MR comments, webhook events.

Approvals & visibility

Merge-request-only delivery — merging stays a human action in your review flow.

Plan

Pro and above

Limitations

Never pushes to a default branch.

Supported actions

Cloud and Server/Data Center: repository analysis, pull-request delivery, comments, webhook events.

Approvals & visibility

Pull-request-only delivery, behind the same approval gates as GitHub and GitLab.

Plan

Confirmed during onboarding

Limitations

No dedicated marketing page yet, and health probing is more basic than for GitHub/GitLab.

Supported actions

Issue sync, internal comments and transitions (GraphQL; OAuth or API key).

Approvals & visibility

Internal comments only — no customer-visible replies. Writes go through the outbox and approval flow.

Plan

Confirmed during onboarding

Limitations

Inbound webhook sync is on the roadmap.

Supported actions

Inbound mailboxes (Gmail, Office 365) become Inbox items; governed outbound notifications and portable approval emails.

Approvals & visibility

Customer-facing email replies follow comms governance; an optional low-risk auto-send mode is opt-in, policy-bounded and audit-logged.

Plan

Confirmed during onboarding

Limitations

Mailbox connections are per-tenant OAuth; re-consent is surfaced on the settings tile.

Supported actions

Public intake widget: lead capture, answers from public knowledge, and project-scoped ticket status in customer-safe form.

Approvals & visibility

Every outgoing message passes a public reply-safety wall; origin allowlist and rate limits are fail-closed.

Plan

All plans

Limitations

It cannot reach internal notes, internal ticket data or any other organization's data — it sees only the bound project's customer-safe view.

Supported actions

Deployment visibility plus Argo Rollouts promotion gates: an approval resumes a paused rollout; abort and read-status where configured.

Approvals & visibility

Nothing promotes without a recorded human decision.

Plan

Pro (where configured) / Enterprise

Limitations

No general cluster write access — gated promotion is the only execution path.

Supported actions

Read-only diagnostics against your PostgreSQL database, with sensitive column names redacted before results reach the AI.

Approvals & visibility

Every query shape is allowlisted and approval-gated; read-only access is verified before first use.

Plan

Confirmed during onboarding

Limitations

PostgreSQL only. Queries can inspect data but cannot change it.

Supported actions

Public REST API (issues, patches, webhooks, integration status) with a published OpenAPI spec; signed outbound webhooks.

Approvals & visibility

Tenant-scoped API keys; outbound webhooks carry timestamped HMAC-SHA256 signatures.

Plan

Confirmed during onboarding

Limitations

Rate-limited per key.

Supported actions

Observe-and-govern preview: pipeline and deployment event ingest (GitHub Actions, GitLab CI, Jenkins, Azure DevOps, Vercel, Terraform Cloud, Kubernetes) with compliance export.

Approvals & visibility

Observe-only — it scores and records deployments; it does not execute them.

Plan

Preview — scoped during pilot

Limitations

Labelled preview: coverage and surfaces are still maturing.

On the roadmap — WhatsApp intake is not available yet. Not connected or configurable today; tell us if it matters for your evaluation.

On the roadmap — SAML SSO is not shipped; OIDC SSO and SCIM 2.0 are the shipped identity integrations. SAML stays on the roadmap for now — ask us about timelines if it is a hard requirement.