> ## Documentation Index
> Fetch the complete documentation index at: https://docs.get-hive.ai/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Hive is an AI operations layer for small and mid-sized business teams. It reads the tools a team already runs, raises what needs attention, and acts with the approvals the team configures.
> Answer only from these pages. If a page does not cover something, say so and link the closest page rather than inferring behaviour.
> The supported programmatic entry points are incoming webhooks, public workflow forms and the remote MCP server, each documented under Developers.
> Each connected account has a level: Read, Draft or Act. New accounts start on Act. Agents and workflows take only the actions selected for them, whatever the account level.
> Describe security, sign-on and data handling only as the Security pages and the FAQ describe them, and add no certification, compliance, single sign-on or model-training claim they do not make.
> Prices and credit allowances are in GBP. Quote them only as a page states them, without converting.
> Use UK English and the product's exact UI labels. Link to pages as https://docs.get-hive.ai/<path>.

# Matters: what Signals finds going on across your accounts

> How Signals reads your accounts each hour and keeps your matters — deals, invoices, applications — linked across your tools, and follows what you asked it to keep an eye on.

A **matter** is something you have going on: a property deal, a visa application, an invoice a client
still owes, a supplier dispute. Signals keeps a list of your matters by reading the accounts you
connected, and links what belongs together across them. An email that quotes invoice INV-104, the
INV-104 invoice in your accounting tool and the call you booked with that client become one matter.

Open them from **Signals → Matters** (`/signals?tab=matters`). The line under the tabs reads "Each piece
of client work Hive is tracking, and what it is waiting on". Most matters Signals finds on its own;
you can also [ask Hive to keep an eye on something](#ask-hive-to-keep-an-eye-on-something), and it
follows that as a matter too.

> [!NOTE]
>
> On Business, Signals reads matters for every seated member, and reading them uses the AI
> credits of the member whose accounts it reads, at cost. On an
> [earlier plan](https://docs.get-hive.ai/admin/earlier-plans.md), Signals reads matters for each member with a Max seat,
> and reading them is part of the seat: within its Signals fair use it never draws on your workspace's credit pool, and a newly
> connected account's first read is part of the seat up to its account allowance in any 90 days
> (beyond it, the first read uses credits at measured cost, said before you connect the account).
> Above fair use, each new item uses
> about 1 credit from the pool, up to the member's limit for Signals above fair use (2,000 credits
> a month by default; Owners and Admins can lower it, to 0 if they like). See
> [Fair use and credits](https://docs.get-hive.ai/signals/overview.md#fair-use-and-credits). Hive support can switch matters
> off for a workspace on request.

## Only you see your matters

Your matters are built from your own connected accounts and are visible only to you. Owners and
Admins do not see other members' matters, and nobody else's accounts are read into yours. The same
applies to the notifications and signals Hive raises from them.

## How Signals reads your accounts

There is nothing to start: Signals reads in its regular hourly cycle, right after Hive collects
from your tools.

* **First read.** The first time Signals sees a connected account — or an account you reconnect —
  it looks back at most 4 weeks (28 days), for every kind of account: mail, calendar events, files,
  payments, and finance, CRM and other records (14 days of mail during the free trial). It goes by
  each item's own date — when a message was sent, when a meeting takes place, when a record or file
  last changed — never by when Hive synced it. A mail thread whose newest message is inside the
  4 weeks is read whole, with its earlier messages as context. An open record that has not changed
  in 4 weeks, or carries no date at all, starts no matter; if it changes later, Signals reads it
  then. One exception: an invoice your customer still owes and that is overdue now — past its due
  date, with an amount still due, and not paid, voided or a draft — counts whatever its age, so it
  can start a matter and raise a signal on that first read. This covers Xero, QuickBooks, Stripe,
  FreeAgent and other accounts that hold invoices, up to the 200 most overdue invoices per account;
  bills you owe are not included. An account you connected before matters existed gets its first
  read on the next cycle.
* **After that.** Each cycle reads only what changed since the last one, and never further back
  than 4 weeks, even after a long gap. A record that comes back unchanged is not read again. Mail,
  meetings and files stay within the same 4 weeks: a thread whose last message is older is not read,
  even if Hive only received it now, so older mail never starts or updates a matter. A file Hive
  syncs again without a change is not read again. When an account has more new files than one cycle
  reads, the next cycle continues from where it stopped.

Hive still keeps older mail and files it syncs for Ask, the Library and the Business Brain; Signals
just does not raise matters or signals from them.

* **No notification for a read.** A read never sends you a notification. The Signals page no
  longer shows each account's read status.

Signals skips what nobody owes anything on before it reasons: newsletters and automated mail you
never answered, notes to yourself, system files, and records closed more than 30 days ago.
Automated mail includes no-reply and notification senders, shop and account updates such as
`auto-confirm@`, `shipment-tracking@` and `order-update@`, service desks such as `support@`, and
mail with an unsubscribe address in its headers. Mail from `info@`, `team@` or `hello@` is still
read as a person. Mail you sent from any of your own connected mailboxes, or from an alias your
mailbox filed as sent, counts as yours, so it never makes you owe yourself a reply. See
[Email signals](https://docs.get-hive.ai/integrations/email-and-calendar.md#email-signals).

## What Signals reads

| Kind of account | What is read |
| - | - |
| Mail (Gmail, Outlook) | Your stored mail, grouped into threads. |
| Files (Google Drive, Docs, Sheets, OneDrive, SharePoint, Word, Excel, Dropbox) | Your stored documents that changed, from accounts you connected, when you own or can edit them. A new account is read once Hive has stored its files; if its first file sync has not finished a day after you connected it, Signals reads the files already stored and picks up the rest as they arrive. A file that two of your accounts both store, such as a Word document in your OneDrive with both OneDrive and Word connected, is read once, from OneDrive (or Google Drive, beside Docs and Sheets). |
| Calendars (Google Calendar, Outlook) | Your events, from the window above to a month ahead, with the organiser's and attendees' email addresses and whether an event repeats. |
| Finance and CRM (Xero, QuickBooks, FreeAgent, HubSpot) | Open and recent invoices and the bills you owe suppliers (Xero, QuickBooks; open ones earliest due first), read live and read-only. In HubSpot, only the deals you own: up to 100 open deals, soonest close date first, plus your deals that changed since the last read. See [Deals you own](#deals-you-own). |
| Payments (Stripe) | Every open card dispute or inquiry still waiting on your evidence, on every read. |
| Work tracking (Jira) | Your open issues due within 14 days or overdue by up to 30 days, plus your issues Jira moved to done since the last read. A done issue closes the **Deadline due** raised from it alone. See [Jira](https://docs.get-hive.ai/integrations/work-and-engineering.md#jira). |
| Other systems of record | The records Hive's source pulls collect for them, where your workspace has them. |

### Invoices, bills and disputes

* **Each invoice is its own item.** Hive tracks each Xero, QuickBooks and FreeAgent invoice by the provider's own
  invoice id, so two unnumbered invoices to one customer stay two items. Matters you already had carry over,
  with no duplicates. An older matter titled "Invoice for" a customer stays with the one invoice of theirs still
  owed.
* **When an invoice counts as overdue.** An invoice still owed counts as overdue once its due date has ended
  everywhere: from 12:00 UTC the day after it falls due. That is never early, and up to a day late against your
  own time zone. Hive then knows how many days overdue it is. A QuickBooks invoice has no status of its own, so
  Hive works out whether it is still owed from its balance. Paid, voided, draft and zero-balance invoices are
  never overdue, and neither are Stripe invoices charged automatically.
* **Overdue invoices are picked up even when nothing changed.** An open invoice Hive already read is read again
  within about a day of becoming overdue, and Hive decides whether to raise an **Invoice to chase** on its
  matter. Xero sales invoices are read oldest due first, up to about 200 per read. In a ledger with more open
  invoices than one read covers, the furthest-off ones wait for a later read, and an account with more than 50
  open invoices in QuickBooks or FreeAgent may not have its oldest ones re-read.
* **Bills.** A bill you owe a supplier is tracked as a matter too, earliest due first, and an open bill wakes its
  matter once it is past due. Hive never pays a bill.
* **Card disputes.** Hive files each open Stripe dispute on the matter it is linked to or exactly matches, or
  opens a matter titled `Card dispute — <customer>`. Only the Stripe connector you connected through Hive's
  sign-in is read, not an API-key connection.

## How matters are built

**1. Your Brain and matters first**

Signals starts from the people and organisations in your Brain and the matters you already have,
so a new item joins an existing matter instead of starting a duplicate. A new matter whose title
matches one of your open matters, ignoring capitals, punctuation and spacing, joins that matter
too: "Acme x Globex dinner" and "Acme × Globex Dinner." are one matter.

**2. Exact links**

Items that share an identifier are joined without any AI: a reference code such as `INV-104`
quoted in an email and on an invoice, an invoice, bill or reference number named as one (such as
"invoice ACME0042"), or an email address that is the contact on a record in another tool or an
attendee of a meeting. A bare number such as "invoice 1043" is not used, because a supplier's
invoice 1043 is not your own invoice 1043.

**3. Reasoning over the rest**

Hive's AI groups the remaining items into matters, writes each matter's state — what you want,
what the other side is asking, the next step and when it is due — and decides whether something
needs you.

**4. Dates, not 'tomorrow'**

A matter and its signals are written with actual dates, such as "Thu 12 Nov", counted on your
own calendar: in the time zone you chose under
[Language and region](https://docs.get-hive.ai/get-started/language-and-region.md), or UK time if you have not chosen one.
They
never say "today", "tomorrow", "this week" or "in 3 days", which would be wrong when you read
them on a later day. If the AI writes such a word anyway, Hive replaces it with the date before
saving: for a deadline, payment, meeting or renewal, the date it is due. This applies to text
written in English; in another language Hive asks the AI for dates but does not rewrite them.

**5. Where it shows**

A signal shows under the department its matter belongs to. Payments and invoices show under
Finance and deals under Sales, whatever the matter. Travel, applications such as a visa or a
licence, and legal deadlines show under People, never IT & Security.

**6. Your Brain learns the people**

The people a matter involves are added to your own Brain, found again by their email address
the next time any of your accounts mentions them. Only you see them: your Brain is never shared
with other members, admins included.

Signals runs on your workspace's Efficient background model. On Business, it uses the AI credits
of the member whose accounts it reads, at cost. On an earlier plan, within each Max seat's
fair use it does not draw on the credit pool. Above fair use, each new item analysed uses about 1
credit from the pool, each prepared action about 11 and each client reply about 12, up to the
member's limit for Signals above fair use (see
[Fair use and credits](https://docs.get-hive.ai/signals/overview.md#fair-use-and-credits)). Each read records the model and
tokens it used.

### How meetings, deals and invoices join matters

A matter is one piece of work with the people it involves. Signals never collects items into a
catch-all matter such as "Other", "Meetings" or "Deals".

* **Meetings.** A meeting with someone outside your company joins the open matter of that person or
  their organisation. Hive matches it by the attendees' email addresses, so a call with a client
  joins that client's email matter. Only when no matter fits does a meeting start one of its own.
  Internal meetings (only you and people on your own company's email domain) and recurring internal
  meetings such as stand-ups and one-to-ones are skipped.
* **Deals, invoices and bills.** Each open deal, and each invoice or bill still owed, is its own
  matter or joins the open matter of the same client. Deals and invoices of different clients are
  never put in one matter. A HubSpot deal in a **Closed won** or **Closed lost** stage counts as
  closed.
* **A deal and its contacts' email.** Hive reads the email addresses of each HubSpot deal's
  contacts, so a deal joins the matter of your email with those people by exact address, with no
  AI involved.
* **Filed by the AI alone.** A meeting, deal or invoice is added to an existing matter only through
  an exact link above, or because Hive's AI judged that it belongs there. When the AI placed it
  without an exact link, it shows on the matter but does not change the matter's status or next
  step, and does not raise a signal.

Matters Signals built before October 2026 stay as they are.

### Deals you own

Signals reads only the HubSpot deals you own. Once a day it looks up your HubSpot user by the email
address of each mailbox you connected, and it reads the deals whose owner is that user. If no
HubSpot user has one of your addresses, or HubSpot refuses the lookup, Hive reads none of your
HubSpot deals: it never reads the whole portal. Deals where you are only a collaborator are not
read. Connect the mailbox whose address you sign in to HubSpot with, so Hive can find your deals.

When a deal one of your matters links is reassigned to someone else in HubSpot, it drops out of
those reads. Hive reads that deal back by its id (up to 20 a read), sees it is no longer yours, and
closes its [Deal slipping](#deal-slipping) card with a line on the matter's timeline. Hive's AI
does not read a deal someone else owns.

## Lanes and detail

Matters sit in four lanes: **Waiting on you**, **Waiting on them**, **Active** and **Done** (a
matter Signals judged dormant shows under **Done**). Each card shows the next step, the people
involved, the accounts it came from, its due date and any open signals. A matter past its due date
is marked **Overdue**.

To move a matter to another lane, drag its card into that lane, for example from **Waiting on
them** to **Done**. It is the same change as choosing the lane under **Status** when you
[edit the matter](#correct-a-matter). The card shows in its new lane at once; if Hive can't save
the move, the card goes back and Hive says so. From the keyboard, focus a card and press **Space**
to pick it up, **←** and **→** to choose the lane, and **Space** or **Enter** to drop it there.
**Esc** cancels. **Enter** on a card you have not picked up opens it.

Select a matter to open it full page. On a phone it fills the screen. The header stays in view as
you scroll, with the matter's title, its status, your [controls](#correct-a-matter) and **×** to
close it. **Esc**, a click outside it, or your browser's **Back** button close it too (while you
are [editing](#correct-a-matter) with unsaved changes, Hive asks first). The address
ends in `?matter=` and the matter's id, so you can bookmark it. Only you
can open it. If the matter was merged into another or removed, the page says it could not be
opened.

The matter shows:

* **Summary**: its kind, status, due date, last activity, how confident Signals is that the items
  belong together, the accounts its items came from, and the people involved;
* **Where it stands**: what you want, what the other side is asking, and the next step;
* its [requirements](#requirements-and-playbooks) — including what you are
  [waiting for](#ask-hive-to-keep-an-eye-on-something) on it — and its
  [hand-offs](#hand-offs-to-your-agents-and-workflows);
* the signals raised on it, with when each comes due;
* [what Hive did](#what-hive-did) on each of its signals;
* **Across your accounts**: its items, each with **Open in Gmail** or **Open in Outlook** where Hive can link to
  the exact message;
* its timeline, oldest first.

A section with nothing in it is left out.

## At a glance

Above the tabs, the Signals page shows four numbers. The first three count matters; the fourth adds
up the money on your open signals, and each label says which:

| Number | Counts |
| - | - |
| **Open matters** | Your open matters. |
| **Waiting on you** | Open matters waiting on you. |
| **Overdue matters** | Open matters past their due date. |
| **Value across open signals** | The money on your own open signals, rounded to whole units. |

Done, dormant and muted matters are not counted. The three counts follow each matter's own state,
not its signals: a matter is counted until it is done, dormant or muted. Each number is a link,
marked with an arrow: select **Open matters** or **Waiting on you** to open your matters, or the
value to open the **Attention** feed it is summed from. **Overdue matters** is a filter: select it
to open your matters showing only the overdue ones (exactly the matters the number counts), each
marked **Overdue**, with an **Overdue** chip above the lanes. Select the number again, or **×** on
the chip, to show all your matters. When nothing is overdue, the page says so. On a phone the four
numbers are a row of chips you can scroll sideways. The value shows a currency symbol only when
every amount is in the same currency, and a dash when nothing is at stake. Like the feed, it counts
only your own signals, whatever your role, and leaves out chase signals (a **Chase** or an
**Invoice to chase**), which the feed does not list either.

## Open a matter in Ask

An open matter has **Open in Ask**. It opens [Ask](https://docs.get-hive.ai/ask/ask-hive.md) with the matter already written
into the message box and a **From matter** chip above it. Nothing is sent until you add your
question and send it. Hive then already knows the matter and its email threads, so it doesn't
search for them, and the chat keeps them for your follow-up questions. Remove the chip to ask
without them. In a shared chat, only your own questions use them.

## Quiet matters go dormant

Signals moves a matter to dormant (shown under **Done**) when it has been quiet for 30 days. That means
nothing new from your accounts since its last message or record (however recently Signals found the
matter), nothing you did on it, no requirement still open, no active signal and no due date still
ahead. Its timeline records why. When anything new arrives for a dormant matter, it reopens on its
own.

## Correct a matter

Signals reads your accounts, but you know your business. Open a matter and use the buttons in its
header to correct it:

* **Edit** switches the matter into edit mode. The header changes to **Editing matter** with
  **Cancel** and **Save**, and the matter's other buttons, including those on its requirements and
  hand-offs, are hidden until you finish. You can change:

  * the title;
  * **Status**, to move the matter to another lane: **Waiting on you**, **Waiting on them**,
    **Active** or **Done**;
  * **Due**, a date picker. A matter keeps the time of day it was already due; one with no due
    date gets 09:00 your time. **Clear** removes the due date;
  * the summary, what you want, what they are asking, and the next step. The next step box grows
    as you type.

  Leave a text field empty to clear it. Select **Save**, or press **Cmd+Enter** (**Ctrl+Enter** on
  Windows), to save. Hive confirms with *Saved. Hive keeps your wording* and leaves edit mode.
  Kind, people and accounts come from the matter's linked items, so they can't be edited. To move
  items to another matter, use **⋯** → **Split…**.
* **Mark done** moves the matter to **Done**; **Reopen** brings a done one back to **Active**.
* **Mute** stops Signals raising signals on the matter. It stays in your lanes and keeps
  collecting items from your accounts. **Unmute** turns signals back on.

Your edits are never lost by accident. With nothing changed, **Esc** just leaves edit mode. With
unsaved changes, **Esc**, **×**, a click outside the matter, your browser's **Back** button or
going to another page first asks **Discard changes?**. **Keep editing** takes you back to your
changes; **Discard** throws them away. **Cancel** leaves edit mode without saving.

On a phone, the header has **Open in Ask**, **Edit** and **⋯**, which holds **Mute**, **Merge
into…**, **Split…** and **Mark done**. The matter's summary facts and its items across your
accounts are folded into **Details**, after **Where it stands**. **Edit** opens the form full
screen, with **Cancel** and **Save** at the bottom.

While a change is saving, the header says **Saving…** and the buttons wait. If a change fails, the
reason shows under the header and your edit stays open.

The **⋯** (**More actions**) menu holds the two changes that reshape your matters:

* **Merge into…** opens a list of your other matters, with a search box. Pick the one this matter
  belongs to. Hive explains what happens before you select **Merge**: its items, timeline and
  signals move to the other matter, and this one is removed. A merge cannot be undone. When it is
  done, the matter it went into opens.
* **Split…** lists the matter's items. Tick the ones that belong to something else, give the new
  matter a title, then select **Split into new matter**. The button stays off until you have
  picked at least one item and given a title. The new matter opens when it is done. Items split
  out of a muted matter stay muted.

If a merge or split fails, the reason shows in its dialog, so you can try again or cancel.

Your timeline also records what you did with a signal on the matter: approved or declined the action Hive
prepared, dismissed it (with the reason you picked), snoozed it (with the date it comes back), or asked Hive to
remind you. Only your own explicit actions are recorded. Nothing is recorded when you do nothing, when an approval
expires or is replaced, when a signal clears itself, or when a snooze ends. The entries are fixed wording plus a
reason or a date, never the text of a draft.

Hive also writes on the timeline what it reads for itself, without claiming it caused it:

* **Paid**, for example "Invoice INV-104 reads paid in Xero (paid 2 Oct)", when Hive reads the invoice paid in
  Xero with money received and nothing credited. FreeAgent and QuickBooks invoices never show Paid, and Stripe
  invoices on a matter do not show it either.
* **Replied**, for example "Jane Doe replied on “Re: Contract”", when the newest message on a linked thread comes
  from someone you wrote to and answers you. Auto-replies, out-of-office notices, mailings, people only copied
  in, colleagues on your own company's domain, and your own messages (including anything Hive sent for you) never
  count.
* **Voided, credited or closed**, for example "Invoice INV-104 voided in Xero (read 3 Oct)". A Xero invoice cleared
  by a credit note reads credited in Xero. A FreeAgent invoice marked Paid, or a paid Xero invoice whose amounts
  Hive cannot read in full, reads closed in FreeAgent (or Xero). These end the chase but are never shown as
  Paid.
* **Dispute settled**: when Stripe shows a dispute under review (evidence submitted), won, lost, closed or
  refunded, once.

An outcome is recorded only on an item the matter already links. When the matter links exactly one invoice (or
one thread), the matching **Invoice to chase** (or **Follow-up due**) signal closes, any card waiting on it is
withdrawn, and **What Hive did** shows the outcome. A send already in progress still completes. Chasing what the
client owes on a voided, credited or closed invoice stops too, each with a "Chasing … stopped" entry, and you can
turn chasing back on. Hive re-checks the invoices your matters link by their own Xero id, so an invoice voided
before Hive's last read is still picked up, and it never chases again on an invoice it read as closed.

Every change appears on the matter's timeline as yours, for example *You changed the next step
to "Ask for the multi-year price" (was "Sign the order form")*. Signals reads your latest
corrections each hour before it updates a matter. It keeps your wording unless something new in
your accounts changes the situation, and never raises a signal on a muted matter. What Hive wrote
from your mail — a matter's title, next step and summary — reaches that reasoning quoted, apart
from your corrections and the muted mark, so a sender cannot pass off a correction or a mute by
writing one into an email.

Only you can change your matters. Owners and Admins cannot change, merge or mute another member's
matters, and cannot see them.

## What Hive did

The **What Hive did** section of a matter lists, under each of its signals, the actions Hive took, step by step,
with when each happened:

* **Drafted**, **Saved as a draft in Gmail** (or another tool), **Waiting for your approval**, **Sending**, **Sent
  (Gmail accepted it)** and **Delivered**. Only steps Hive has evidence for are shown, and nothing is shown for a
  signal with none: the section never claims Hive did nothing.
* **Waiting for your approval** appears only while a card waits for you, never for an action your account's
  **Act** setting ran by itself.
* A note under an action says when it failed (with the reason), "Hive cannot confirm this went out. Check before
  sending it again." for a stuck send, "Recorded in Hive only; nothing was sent." for an internal record, and
  **Undone**.
* The outcome Hive read for itself, for example **Paid · 2 Oct** or **Resolved — they replied**.

Only you see it; Owners and Admins do not. An earlier occurrence of a signal that came back stays in the
[audit log](https://docs.get-hive.ai/approvals/audit-log.md).

## Ask about a matter

In [Ask Hive](https://docs.get-hive.ai/ask/ask-hive.md#where-answers-come-from), ask "What's happening with the Vanta
purchase?" and Hive answers from that matter: its state, both positions, the next step, its
timeline and the signals on it. The items it links, such as the email thread or the deal, are
cited as the answer's sources.

## In your Brain

The page of a person or company in your [Business Brain](https://docs.get-hive.ai/brain/business-brain.md) lists the matters
they are part of. Select one to open it here.

When a person is erased from your Brain, your matters stay, but the person leaves them: their links
go, and their full name and email addresses in your matters, matter timelines and matter Signals
read **a removed person**. See
[Erasing someone from the Business Brain](https://docs.get-hive.ai/security/data-protection.md#erasing-someone-from-the-business-brain).

## Requirements and playbooks

Each matter of a kind your company handles often — a property purchase, a visa application, a
supplier onboarding — follows a standard path. Signals tracks that path on the matter as
**requirements**: what is needed, who owes it (**Us**, **The client**, **The other side** or **A
third party**), its status, when it is due, and what shows it is done.

* **Playbooks come from your company.** The path is a [playbook skill](https://docs.get-hive.ai/skills/skills.md). Signals
  follows the approved playbook that fits the matter. When none fits, it proposes one, learned from
  your Library's own procedures, how your past matters of that kind went, and the matter itself, and
  only then general knowledge. It proposes one only once you have handled that kind of matter at
  least 3 times on 2 or more days within 14 days, and at most one a day and three a week; see
  [How often Hive suggests a skill](https://docs.get-hive.ai/skills/skills.md#how-often-hive-suggests-a-skill). The proposal
  waits on the **Suggested** tab of **Skills** until an admin approves or rejects it. Hive ships no
  playbooks of its own.
* **Kept current.** Each hourly cycle, Signals checks a few of your matters that are new or have
  changed since it last looked, adds steps that apply and marks a step done when the evidence
  arrives, such as a reply with the document or an invoice paid.
* **Your word wins.** In the matter's **Requirements**, use **Mark done**, **Not needed** or
  **Reopen** on any step, and **Stop chasing** on a step someone else owes. Signals never overrides
  a change you made, and a merged matter's requirements, your changes included, move to the matter
  it joins. Every change appears on the matter's timeline. Signals does not track a muted matter.

A playbook a matter follows is named above its requirements. If Signals proposed it, it is marked
**waiting for approval in Skills** until an admin reviews it.

## Hand-offs to your agents and workflows

When one of your own [agents](https://docs.get-hive.ai/agents/agent-studio.md) or [workflows](https://docs.get-hive.ai/workflows/build-a-workflow.md) would move
a matter on, such as an intake agent that collects documents or a workflow that files something,
Signals hands the matter to it. The account the matter's mail is on decides:

* **Act**: Signals starts it for you, as you. The agent or workflow gets only a reference to the
  matter and reads the matter itself, so nothing written in someone else's email becomes its
  instructions. It is your own run, as if you had started it, and is billed like any other run of
  that agent or workflow: it uses credits from your workspace's shared pool, within that agent's or
  workflow's own limits, including its monthly credit limit.
* **Draft** or **Read**: Signals suggests it under **Hand-offs** in the matter, with what it would
  ask for. Select **Start** to run it as you, or **Dismiss**. Whichever way it starts, the agent or
  workflow gets the same request: Hive's own fixed words, which point it at the matter and tell it to
  read the matter before it acts — never the text Signals wrote from someone's email. Hand-offs
  suggested before this change start the same way. An app connected through MCP can start one only
  if you also let it run agents or workflows.

Signals offers only your deployed agents and the deployed workflows you start by hand, and never
suggests the same one twice on a matter. A started agent or workflow keeps its own actions, approvals
and limits. Every hand-off appears on the matter's timeline.

## Ask Hive to keep an eye on something

Tell [Ask](https://docs.get-hive.ai/ask/ask-hive.md) what you are waiting for — "keep an eye on INV-104 being paid", "tell me
when the signed lease comes back from Jane", "let me know if Vanta emails" — and Hive follows it as a
matter. There is nothing separate to set up or look after: it sits with the rest of your matters.

**1. Ask shows one card**

Ask answers with a **Follow this as a matter** card. It shows what Hive is waiting for, in your
words, and which of your accounts Signals reads, so you know where Hive will look. If one of your
own open matters clearly fits — the same invoice, deal, person or thread — the card is titled
**Add to** and that matter's name instead, and offers to add **Waiting for: …** (set by you) to it.
Nothing is created until you press **Follow** (or **Add to matter**).

**2. It becomes a matter of yours**

On a new matter, Hive titles it from your words, puts it under **Waiting on them**, and adds what
you are waiting for as its first requirement. On a matter you already have, it is added to the
matter's requirements. Either way the requirement reads **Waiting for:** and your words, marked
**set by you**, and the matter's timeline says you asked Hive to keep an eye on it.

**3. Signals follows it every hour**

A matter you started is followed exactly like one Signals found. Each hourly read links new mail,
files, meetings and app records that belong to it, as for any matter, and checks what you are
waiting for against everything that arrived since you asked. Only something that clearly shows it
happened counts. Automated notices count too, so "tell me when Vanta's report arrives" works for a
notification email.

**4. It tells you when it happened**

When it happens, the requirement is marked done with what met it, the matter's timeline records
it, and Hive raises a **Waiting for met** signal on the matter. What happens next follows the
[Read, Draft or Act setting](https://docs.get-hive.ai/integrations/accounts-and-autonomy.md) of the account the item came
from, as for any signal. It is met once, and is not checked again.

You can be waiting for up to 20 things at once, and Signals checks every one of them each hour.
Hive never chases anyone for something you are only waiting for; **Mark done** or **Not needed** on
the requirement stops Hive checking it. To ask for something to happen every time ("every time HMRC
emails, summarise and file it"), see [Something that happens every time](#something-that-happens-every-time).

Keeping an eye on something needs the **Operator** role or higher, and Signals reading your
workspace's accounts into matters. Starting one of your agents or workflows when something happens
is not available from this card.

### Who sees it

What you asked Hive to keep an eye on is yours alone, like your matters and signals. Signals checks
it against your own connected accounts only, and nobody else in the workspace, an Owner or Admin
included, sees it or is told about it. In a [shared chat](https://docs.get-hive.ai/ask/ask-hive.md), only the person who asked
can press the card.

An AI client connected through the [Hive MCP server](https://docs.get-hive.ai/developers/mcp-server.md) can do the same with
`matters_follow`, with the `signals` scope: the condition, and a `matterId` to add it to one of your
matters.

### Something that happens every time

Words such as "every time", "whenever", "always", "from now on", or a cadence ("every Monday") ask
for something repeating: "every time HMRC emails, summarise and file it". That is a
[workflow](https://docs.get-hive.ai/workflows/workflow-builder.md) with a
[Connected app event](https://docs.get-hive.ai/workflows/workflow-steps.md#connected-app-event) trigger, drafted from your words
by the [Workflow & schedule builder](https://docs.get-hive.ai/ask/build-from-chat.md). Ask shows a **New workflow** card, and
**Create** saves it as a draft: deploy it in **Workflows** to turn it on.

It lives in **Workflows**, not on the Signals page. The workflow shows **From Signals:** and your
words, and **Started from Ask** in the Workflows filters lists only these workflows. Pause or edit
it there like any other workflow.

### Watches from before

Hive used to set up separate **watches** for this. It no longer does: the **Watching for** lists on
the Matters tab and in a matter are gone, and so is the Ask **New watch** card. Watches you set up
before keep working as they were, and their **Watch met** signals still arrive. AI clients can list
them (`watches_list`) and stop one (`watches_cancel`); creating a watch now answers that keeping an
eye on something is `matters_follow`. Older links to the Watches tab (`/signals?tab=watches`,
`/signals?tab=watching` and `/monitoring`) open the **Matters** tab.

> [!NOTE]
>
> Signals no longer watches companies on Companies House, your own or your clients'. Watches you set
> up before are kept but no longer checked, and Hive raises no more filing reminders from them. Ask
> Hive about a company and it still looks it up on Companies House. See
> [Companies House](https://docs.get-hive.ai/integrations/companies-house.md).

## Hive learns from your own replies

When you reply in a matter's thread yourself, the reply appears on the matter's timeline. If Hive's
draft was still waiting for you, the timeline says you replied yourself instead. When you
[edit Hive's drafted reply](https://docs.get-hive.ai/approvals/review-and-approve.md#edit-a-drafted-email-reply) and approve it, the
timeline says you edited the draft, and the reply you sent is read as your own. Signals updates what
you want on the matter from what you wrote. It also keeps a few short notes on how you write, such as
your sign-off, tone and length, in your own [Business Brain](https://docs.get-hive.ai/brain/business-brain.md), where only you
can see them. Later replies it drafts follow that tone. The notes never hold names, numbers,
addresses or links, and never decide what a reply says or who it goes to. Mail Hive sent from your Gmail for a
signal, including a draft you edited and approved, is Hive's wording rather than yours, so a Gmail thread that holds
it does not add to these notes.

## Matters in agents, workflows and Ask

Agents and workflow agent steps given **Connected systems** under **The person's own data** can find and
read the invoking member's own matters, with their requirements and timeline. To update a
requirement, use the matter's **Requirements** or ask Hive in Ask, which can mark one done, asked
for or not needed, add a note, or stop or resume chasing for you.
This changes only Hive's record of the matter and sends nothing to anyone. Nobody else's matters
are reachable this way, admins included.

## Signals raised on a matter

When something needs you — a reply owed, an invoice to chase, a renewal coming, a document waiting
on you, a deadline to meet, a payment you owe, a follow-up with someone who has gone quiet, or two
sources that disagree — Signals raises a signal on the matter with a proposed next action.

* **Invoice to chase** is money owed to you or your side: your fee, an invoice you issued, a refund or
  a deposit that is overdue.
* **Payment due** is money you owe: a bill, council tax, a fine or penalty notice, a fee, or a supplier
  invoice to approve or pay. Hive never pays anything: paying is yours. A **Payment due** is never
  raised when every bill it names already reads paid or voided in your accounting system.
* **Deadline due** is a dated task you must meet that isn't a reply to someone: a court or tribunal
  response, a filing, a completion, a form or portal task, booking an MOT.
* **Follow-up due** is chasing the other side for information, an approval or a reply that has gone
  quiet.

Signals reads a meeting when it first appears or changes, and may raise meeting preparation
then, but does not check it again as the meeting gets close, so don't rely on it to remind you to
prepare for a meeting. Deals are checked every hour by Hive's own rule: see
[Deal slipping](#deal-slipping).

Each signal has a **when**:

* **Now** — it appears in your **Attention** feed straight away and is prepared like any other
  signal (see [Triage signals](https://docs.get-hive.ai/signals/triage-signals.md)).
* **Later** — it is listed on the matter with its due time, and notifies you when it comes due. Due signals are
  raised on Hive's hourly pass, so one can arrive up to an hour after it falls due. If it stays held (snoozed, in
  cooldown, or being worked on) through five hourly passes, the reminder is dropped rather than sent late.

**One live card per matter and kind.** When a new reply is owed (or a status update is asked for) on a matter
whose earlier card you already handled, Hive closes the earlier card and opens a fresh one. Other kinds, such as
an invoice to chase, a payment due, a deadline due, a follow-up, meeting preparation, a quiet deal or a renewal,
keep one card per matter and refresh it, and requirement chases repeat on their own, at most twice before one
reminder that the requirement is still outstanding (see [Chasing what others owe](#chasing-what-others-owe)). A message dated in the future never opens a new card.

**The amount at stake.** A signal on a matter shows the largest amount the records it names carry, such as an
invoice's amount due, in that record's own currency. The amount is read from the record in the connected account,
never from Hive's AI. It ranks the signal in your feed and counts toward **Value across open signals** and the Value report;
Hive never converts currencies, so when amounts are in different currencies the total shows no currency symbol.
When the signal is an **Invoice to chase** about one invoice, or a **Payment due** about one bill, its evidence also
cites that record's exact amount, pence included. A signal with no amount on its records shows none.

**Card disputes.** Each open Stripe dispute gets its own **Dispute evidence due** card on its matter, 48 hours
before Stripe's evidence deadline, or straight away when less time is left or Stripe states no deadline. It shows
the disputed amount in its own currency and says "Submit evidence in Stripe before" the deadline (in UTC); an
inquiry reads "Stripe inquiry: respond by" its date. Hive never submits evidence or moves money: submitting the
evidence is yours, and what Hive prepares follows the account's setting, as for every signal. It ends when Stripe
shows the dispute under review, won,
lost, closed or refunded, even if you have closed the matter since. Muted matters get no dispute cards.

What happens next follows the **Read**, **Draft** or **Act** setting of the account involved
(**Integrations → Connectors**), as for every signal: on **Act**, Hive acts by itself within your
workspace's limits; a reply in your own recent thread goes out by itself too, to someone already in
that thread, when Hive wrote it from that thread alone (see
[Email replies on an Act account](https://docs.get-hive.ai/approvals/autonomy-and-blast-radius.md#email-replies-on-an-act-account)),
while any other email, a new one included, comes to you as a card, because a sent email cannot be undone; on **Draft**,
it leaves a card for you to approve, edit or decline; on
**Read**, it only tells you. A signal on a matter is prepared from the matter itself: what you
want, what the other side asks, its requirements, and its email thread, read in full.

On an **Act** account, a signal on a matter — whatever amount or severity it shows — is carried out by itself, within
your workspace's limits and the kill switch, except a chase and an email: every chase, as a reply in your thread or as a new
email, waits for your approval (see [Chasing what others owe](#chasing-what-others-owe)), and any other email goes out by
itself only as a reply in your own thread written from that thread alone. Its timeline then says what Hive did, for example "Hive carried out one
step for a signal on this matter by itself, from your Act account. Why: …", and also which steps were saved as
drafts, only partly ran, did not run, or can't be confirmed. An action that moves money, such as a refund, still
waits for you. See [Routine signals on an Act account](https://docs.get-hive.ai/approvals/autonomy-and-blast-radius.md#routine-signals-on-an-act-account).

A chaser Hive drafts for an overdue invoice says how many days it is past due, never how quickly payment
"usually" arrives.

A next step that involves only your own colleagues — agreeing a price with finance, checking with
a teammate, briefing your team — is not raised as a signal. Hive adds it to the matter's
[requirements](#requirements-and-playbooks) as a to-do owed by your side, and never drafts an email
or an approval card for it. Steps that reach the client or the other side work as above.

### Deal slipping

Every hour Hive checks each of [your own HubSpot deals](#deals-you-own), with no AI involved. A deal
is slipping when it is still open and:

* its close date has passed;
* nothing has been logged on it in HubSpot for 21 days, unless a next activity is booked or you
  emailed its contacts in that time; or
* it has been in the same stage for 45 days.

Hive raises a **Deal slipping** card only when a deal crosses one of these lines: within 14 days of
its close date passing, or within a week of reaching 21 quiet days or 45 days in its stage. Deals
that slipped long before are not raised. An empty next step adds a line to the card, but never
raises one on its own. A deal is raised once per line it crosses, even if you dismiss the card. If
it later recovers and slips again (for example past a new close date), that is a new card.

The card names the deal and the dates behind it, such as its close date or last activity. Hive's AI
then drafts a short check-in email to the deal's contact, for you to approve: at most 5 new Deal
slipping cards per member a day, so at most 5 drafts. Each draft counts as a prepared action under
[Signals fair use](https://docs.get-hive.ai/signals/overview.md#fair-use-and-credits). Nothing is sent and nothing is changed in
HubSpot until you approve it, whatever your account's Read, Draft or Act setting. The card closes on
its own when the deal closes, when none of the lines holds any more, or when the deal is
[reassigned to someone else](#deals-you-own).

### Not in your CRM

When someone you are corresponding with is not a contact in your CRM, Hive raises a **Not in your
CRM** card with a ready **Create contact** action. Hive's own rule prepares it, with no AI involved:
the person's name and address come from the email.

* **Who counts.** Someone who wrote to you in a thread and whom you wrote to directly (not only
  copied), on one of your open deal, invoice or support matters. People who never replied, shared
  inboxes such as info@ or billing@, no-reply senders and people on your own company's domain are
  skipped. Hiring, travel and other matters are never checked.
* **The check.** Hive looks them up by email in your own HubSpot, and in Salesforce (contacts and
  leads) if you connected it, reading only. If a lookup fails, or finds a contact with the same name
  under another address, no card is raised.
* **Limits.** At most 5 new cards an hour and 15 open at once. Hive never asks twice about the same
  address, even after you dismiss the card. A card closes on its own once the person is in your CRM.
* **Approval.** The contact is created in HubSpot only when you approve the card, even on an account
  set to Act. HubSpot may count new contacts toward your marketing contacts.
* **Fair use.** Because no AI prepares it, the card is not a prepared action under
  [Signals fair use](https://docs.get-hive.ai/signals/overview.md#fair-use-and-credits): it never uses one of your seat's
  prepared actions or any credits, and it arrives ready to approve even when you are above fair use
  and the pool is empty. A **Deal slipping** draft, which Hive's AI writes, does count.
* **Your own workflow.** If you have a deployed workflow that already creates contacts in that CRM,
  Hive raises no Not in your CRM cards for it.

### A workflow for cards you keep getting

Once you have had 2 Deal slipping or 2 Not in your CRM cards in 30 days and approved at least 1 of
them, Hive suggests, once, the free template that handles them in bulk: **Weekly pipeline check** or
**Email contacts to CRM**. The suggestion arrives in your Inbox under **Needs you**. See
[Suggested workflows](https://docs.get-hive.ai/get-started/inbox.md#suggested-workflows).

## Mail you were only copied on

A thread your connected mailbox only received as a copy — you were on **Cc** or **Bcc**, or it
reached you through a group, shared or forwarding address — is not yours to act on. None of your
addresses wrote in it or was a direct recipient. Signals:

* never starts a matter from it, and never raises a signal, a chase or a reply from it;
* may still add it to a matter that exists from other evidence, as context: it shows on the
  matter's timeline but does not change the matter's status or next step;
* never chases in it or prepares a reply in it.

The same rule holds outside matters: such a thread never raises an **Awaiting reply** signal,
never appears in
Ask's list of threads waiting on your reply, and no agent prepares a reply in it. Ask prepares one
there only when you ask it to in your own chat.

A matter that rested only on such mail is closed, with a timeline entry saying why, and its open
signals are withdrawn. An **Awaiting reply** signal already open on such a thread closes on the
next hourly check. This applies to Gmail and Outlook alike.

You can also [ask Hive to keep an eye on something](#ask-hive-to-keep-an-eye-on-something) on a
matter ("tell me when the signed contract arrives on the Smith purchase"). When it happens, its
**Waiting for met** signal is raised on the matter.

## Chasing what others owe

For each [requirement](#requirements-and-playbooks) the client, the other side or a third party
owes, Signals asks for it. It replies in the matter's email thread with the person it asks, from
the mailbox that holds that thread — even when only you have written in it so far, as with a first
chase. Only when no thread involves them does it write to them as a new email. It never asks in
another party's thread.

**At most two chases, then one reminder that it is still outstanding.** Hive chases each
requirement at most twice, roughly two working days apart. If it is still outstanding after the
second chase, Hive raises one signal saying so, with no email drafted, so you can decide whether to
call, send a firmer chase yourself, or mark it **Not needed**. Because each chase waits for your
approval (below), the timing is approximate: Hive does not prepare the next chase while the last one
is still waiting on you, for example a draft not yet approved. After the reminder it chases nothing
more on that requirement until it changes: it is done or not needed, it gets a later due date (the
count starts again; the same day at another time, or an earlier date, does not), or a new
requirement replaces it. It also stops when you select **Stop chasing** or the matter closes. A
requirement Hive had already chased more than twice before this limit gets the one reminder too,
and nothing after it. Muted matters are never chased.

**Every chase waits for your approval.** A chase is never sent by itself, whatever the account's
level. On **Act** and **Draft** alike, Hive prepares the chase as a draft for you to approve; on
**Read** it only tells you. The same holds for an **Invoice to chase**. See
[Email replies on an Act account](https://docs.get-hive.ai/approvals/autonomy-and-blast-radius.md#email-replies-on-an-act-account).

**Chase signals stay off the Attention feed.** A chase is follow-up work Hive prepares on the
matter, not something new that needs you, so the
[Attention feed](https://docs.get-hive.ai/signals/triage-signals.md#find-what-needs-you) and its counts leave out every
**Chase** and **Invoice to chase** signal. A chase that waits for your approval stays on the feed as
its **Review chaser** row under **Needs you**, where you approve it. You also find each chase on its
matter. To list the chase signals on the feed, pick **Chase** or **Invoice to chase** under
**Type**.

Every chase appears on the matter's timeline, and a chase waiting for you shows as **Draft waiting
for your approval** under the matter's signals. Each requirement shows how many times it was chased
and, before its second chase, when the next chase is due. After the second chase it shows no next
chase date, because what comes next is the reminder, not another chase; once Hive has sent you that
reminder, it shows **Chased 2×, still outstanding** (or the real count, for a requirement chased
more often before the limit).

## When a client asks for an update

When someone already part of a matter asks how it is going ("any update?"), Signals answers from the
matter: what is done, what is still outstanding and who owes it, the next step, and where the matter
links a deal or an invoice, its current stage or payment status. It prepares a reply in the thread
they asked in for you to approve, on **Draft** and **Act** alike. A reply never shares what you
want from the matter, and a question from someone not yet part of it gets an ordinary reply instead.

If they keep asking, Signals suggests that you deploy a client-facing agent for the matter in
[Agent Studio](https://docs.get-hive.ai/agents/agent-studio.md), so they can check its status themselves. Hive never creates
an agent or shares a link on its own.

## Related

> [card] [Signals overview](https://docs.get-hive.ai/signals/overview.md)
>
> What a signal is and how Hive finds them.

> [card] [Triage signals](https://docs.get-hive.ai/signals/triage-signals.md)
>
> Act on, snooze or dismiss a signal.

> [card] [Business Brain](https://docs.get-hive.ai/brain/business-brain.md)
>
> The people and organisations Hive knows.

> [card] [Build from chat](https://docs.get-hive.ai/ask/build-from-chat.md)
>
> Follow things as matters, and set workflows and schedules, from Ask.

> [card] [Connector health](https://docs.get-hive.ai/integrations/health-and-disconnect.md)
>
> What happens when an account stops working.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.