See what is really waiting in your Hiver inbox

What does the queue look like once somebody reads it?

Different from the unread count.

A companion reads the conversations with their assignees and tags and returns what is actually waiting on you: threads with a customer message after your last reply, threads assigned to somebody who has not been online, and threads where two colleagues have both replied.

That last one is specific to shared inboxes and genuinely embarrassing. Two answers, mildly different, to a customer who now trusts neither.

Drafting with the history already in view

The reply that lands well is the one that references the thread from six weeks ago, and finding that thread is the slow part. A companion pulls the earlier conversations for the same customer and drafts with them attached.

Sending is confirmed. Where the earlier threads contradict each other, and in a shared mailbox they often do, the draft says so rather than picking whichever version it read last.

Which tags and assignments have drifted?

A companion reports the tag list with volumes, the tags used twice in a year, and the open conversations assigned to people who have moved on.

Every fix arrives as one reviewed proposal. Adjacent habits: daily inbox triage with ai and ai for support teams.

The Gmail half and the Hiver half behave differently

A companion reaches Gmail through a direct connection and the Hiver layer as a connected account. Message content, threads and drafts come from the mail side. Shared-mailbox state, tags, assignments and notes come from the Hiver side.

In practice you never think about it, until an action turns out to exist on only one of them. If a routine depends on a Hiver-specific object, check the action list first, because it follows Hiver’s public API rather than what the Gmail sidebar shows.

Frequently asked questions