Skip to main content
Support teams don’t usually lose customers over hard problems. They lose them over slow answers: the urgent ticket buried under routine ones, the reply that sat in a shared inbox over the weekend. Hive reads your support tools and inboxes, flags what’s urgent or waiting, and drafts the response. In Ask and Signals, a person on your team approves it before it is sent; an agent or a workflow you set up sends it by itself, and waits for approval only when where it sends did not come from you.

The problems Hive solves

  • Urgent tickets hide among routine ones until a customer escalates.
  • Replies wait in shared inboxes because everyone assumes someone else has it.
  • Tagging and routing take time that should go on answering customers.
  • Context is scattered across the helpdesk, email, CRM and Slack.

What Hive catches

Hive reads open Intercom conversations (their priority, state and age) in the background, and Zendesk tickets when you ask, so it can answer questions about them and use them in workflows. Background reads cover Intercom workspaces in the US, EU and Australia regions, connected from this Hive workspace. If an account can’t be read in the background, its owner sees why in the Intercom tile’s Accounts panel. To be told when something specific happens, such as a ticket from a key account, ask Hive to keep an eye on it.

Ticket triage every hour

The Ticket Triage template runs hourly: Change the agent step’s prompt to match your definition of urgent. Add a second condition for VIP accounts. The internal notification stays inside Hive — it records an entry in the audit log and reaches nobody — so swap it for a Slack message to your on-call channel if the team should actually hear about it (a step that posts to a channel you picked runs by itself, with no card). See Workflow templates and Workflow steps.

Draft replies, reviewed by people

In Ask and Signals, with a helpdesk or mailbox account set to Draft or Act, Hive can propose:
  • Intercom: reply to the customer, add an internal note, assign, close or reopen a conversation;
  • Zendesk: reply to the customer, add an internal note, create a ticket, assign, update its status, or add tags. A reply stays on the ticket or conversation it answers: see Replies and notes;
  • Gmail and Outlook: draft or send a reply.
Each proposal shows the exact message and the evidence behind it in the review panel. Nothing is sent until someone chooses Approve & run now: a reply cannot be undone, so it waits for approval even on Act. An agent or a workflow is different: on an Act account it carries out the actions selected for it by itself (on Draft each waits for approval). A reply on the ticket or conversation it answers is not held, but an email to an address it found in what it read waits for your approval (see What agents and workflows do by themselves). The Email Keeper template keeps a person in the loop for a shared Outlook inbox: it drafts replies as Outlook drafts for a person to send, and leaves anything unusual unanswered, recording it on the run rather than notifying anyone.

Build a support agent

In Agent Studio, create an agent grounded in your help articles, refund policy and tone-of-voice guide from the Library. Give it a form input for the ticket ID, attach Zendesk or Intercom under Integrations so it can read the ticket, and switch none of its actions on, or set What it may do to Only reads and answers under Advanced in step 3, so it reads but takes no actions. An action you do switch on runs by itself, unless where it sends did not come from the agent’s instructions or words you typed in Hive: then it waits for your approval. Your team gets consistent, on-policy first drafts, and you can use evaluations to check answer quality after every change.

Ask Hive during a shift

  • What are the five oldest open tickets in Zendesk, and who are they assigned to?
  • Summarise this customer’s last three Intercom conversations.
  • Is anyone else reporting login problems today?
  • Draft a reply to ticket 4821 using our refund policy.
You can also ask Hive from Slack or Microsoft Teams: mention @Hive or send it a DM. Signals and approvals stay in Hive. See Slack and Teams.

Guardrails

  • Ask and Signals follow each account’s level. The account’s owner chooses Read, Draft or Act, and new accounts start on Act. On Read, Hive only tells you what it found. A reply cannot be undone, so on Draft and Act alike it comes to you as an approval card; on Act, Hive carries out an action it can undo, such as adding tags or closing a conversation, and tells you, unless a safety check holds it for approval. Act on this on a signal always brings its plan back as an approval card. An Owner or Admin can cap a provider, such as Zendesk, at Up to Draft in Policy & autonomy.
  • Agents and workflows follow the level too. On Act they carry out the actions selected for them by themselves, unless where an action sends did not come from you: then it waits for your approval. On Draft, or under an Up to Draft ceiling, each action waits for approval; on Read they take none. To pause a workflow for sign-off on every run, add an Approval step.
  • Destructive actions such as deleting a ticket are irreversible, so in Ask and Signals they always need approval, even on Act. An agent or workflow you select one for carries it out by itself.
  • Receipts. Every reply Hive sends is recorded in the audit log.

CRM and support integrations

Zendesk and Intercom in detail.

Triage signals

Act on, snooze or dismiss what Hive raises.

Try Ticket Triage on your helpdesk

Start a 7-day trial with no card required. Connect Zendesk and start the Ticket Triage template: it tags each new ticket with its urgency every hour.