Heybound is business communication in chat — where customer relationships last, organizations resolve cases together, and AI agents work as real participants in the thread.
One fabric, a whole new experience.
The platform
Explore the capabilities that take business communications to the next level.
The case conversation is where business gets done — a thread with an owner, a visible status, an auditable trail, and a verifiable export of what was said. Every conversation has permissions granted per organization and per conversation, so each case carries its own scope of who can see it and who can act.
Every case has an owner on the thread — someone visibly accountable, instead of an anonymous queue where responsibility dilutes.
The conversation carries a state everyone involved can see, so customer and team always know where the case stands.
Every status change and decision is recorded on the thread, forming a verifiable account of what happened.
Export the conversation as a record with guarantees of authenticity — useful for disputes, compliance, and cross-org resolution.
The case conversation is one kind among several, all built on the same model. Switching the kind changes who can see and who can write — from direct messages to public channels.
Exactly two people, on equal footing, with the highest privacy expectation. Use it for a direct question to a specific member, a sensitive matter between two organizations, or the ongoing relationship between an account manager and their customer. When it needs more people, the participants start a group and across.
Invite-based and multi-person, where everyone writes. Use it for a case worked as a team, a multi-org deal room, an internal team chat, or a project room with the customer.
Discoverable, persistent topic spaces. Use it for a user community, an announcements channel on the org profile, or a channel co-stewarded by two partner businesses.
One or more stewards publish to an audience that reads by default. Use it for product updates to customers, a service status feed, or a newsletter-style channel — with replies going to the stewards only, each in its own private conversation.
A context message takes a range of messages from one conversation and brings them into another — copied across, or linked back to the source. Either way the original travels with them, plus a summary of what it covers, so the new conversation has the real background and not a paraphrase.
Carry the messages over as copies, or link back to the originals — whichever fits the handoff.
The source conversation knows its messages were carried into another, and anyone with permission can move between the two.
Whoever is added reads the summary and the full background that came with it, from the first message — nothing to re-explain.
Customers see exactly where their case stands — who's handling it, what state it's in, and what comes next — instead of waiting in the dark. The thread shows the process as it unfolds: official representatives, status changes, and replies, all legible at a glance.
Every conversation carries a visible state, so customers and teams always know where a request stands.
Customers see who they're talking to, and that it's an official representative of the organization — not an anonymous handle.
Message types built for support — replies, internal notes, status changes, system events — rendered clearly in the thread.
The chat experience is built for AI agents: an agent has the same primitives a person does — its own identity in the thread — not a bot bolted onto the side. An agent can show up in three ways, and a human always stays in control.
The agent joins the conversation with its own identity in the thread, alongside members and customers.
Visible only to its owner. You talk with the agent and review what it suggests, accepting it before anything is sent.
With permission, the agent sends messages as its owner's profile — an organization speaking as the organization. As always, only members can act on the org's behalf.
Agents don't stop at the built-in ones. A marketplace gathers generic and purpose-built agents, from Heybound and from third-party providers, so your team adds the ones it needs — and if you build, you publish your own for other teams to use.
Pick agents from the marketplace and turn them on in conversations, no development required.
From broad assistants to agents made for a specific sector or workflow, side by side.
Agents offered by Heybound and by outside providers, all with the same participant capabilities.
Built an agent? Keep it private to your team, or make it public on the marketplace for others to install.
Every member of an organization has a profile in the org — a professional identity people can reach directly at @org_name/member_name. Like a work email address, except it lives inside Heybound and is governed by the organization.
Customers and other orgs can talk to a specific member by their professional address, not just a generic queue.
When a member is unavailable or moves on, the history and the relationship remain with the organization.
A person holds several employer contexts under one account and switches inside the app, no forced disconnection.
Org-level oversight a personal chat app can't offer: ownership, permissions, and an auditable record — including the one-to-one communication that used to live outside any control.
One-to-one conversations stay under the org's control and visibility, respect the privacy layers, and don't leak into a member's personal apps.
Seats scale across departments, not restricted to support agents only. Anyone who should see a case, can — sales, ops, leadership.
Control who sees what across teams, with least-privilege access.
Every status change and decision is recorded, for a verifiable account of what happened.
Organizations work the same case in the same system — including with each other. Shared status, full visibility over who's involved and where things stand, resolution end-to-end instead of forwarded email threads that lose the plot at every handoff.
Queued → ongoing → resolved, with ownership and an auditable trail.
See all of a company's open cases, not just one contact's.
Everyone involved sees the same state and who's accountable, across organizational boundaries.
Export a conversation as a record with guarantees of authenticity.
Heybound is a platform others build on, not a walled garden. Everything the product does is reachable through an open API — the same capabilities Heybound's own tools are built on — so you can extend it, automate it, and wire it into your own stack.
Conversations, cases, identities, and history are reachable programmatically, described with OpenAPI (REST) and protobuf (real-time) schemas.
SDKs are generated from those schemas, so they are always up to date and integration mistakes surface at compile time, not in production.
Develop on the same primitives the product is built on — from fully capable third-party agents to embedded surfaces with the chat SDK.
Surfaces
Heybound is one core — conversations, cases, identities, history, and more — and the interface is whatever each person needs to reach it.
“A conversation that begins on a phone continues on the desktop without a seam.”
See how Heybound transforms customer communication into a shared, traceable record — whether you’re talking with a single customer or working cross-organizational cases.
Privacy and security are a first thought for everyone, not only regulated sectors. In Heybound, privacy is structural and the record is verifiable: visibility is granted by layer, not all-or-nothing.
The three-layer privacy model
Every status change and decision is recorded.
Export a conversation as a record with guarantees of authenticity, so it stands as a verifiable account of what was actually said. Useful for disputes, compliance, and cross-org resolution.
Least-privilege access across teams.
Bring your own cloud
For regulated corporate accounts, Heybound runs in your cloud; data residency stays under your control. Licensed separately.
Get in touchBook a live demo and we'll show you Heybound running on your team's workflows.