Purpose

Conversation hub brings durable, structured conversation onto Confluence pages so decisions and follow-ups survive meetings, scroll back, and employee turnover.

Not Just Another Messaging App

The Conversation Hub is not "another forum" or just a simple messaging tool. It is traceable intent: what was decided, what must be done, what risk was raised, who should execute the intent, and—on higher version tiers— connects that to your project's Jira space. It signals and records for your team the when and where of thinking. You can create and schedule the work tickets right in the conversation, not afterwards.

Problems it solves

  • Comments are ephemeral — hard to scan, weak for long threads, and easy to lose in UI churn.

  • Chat disappears — great for speed, poor as a system of record for commitments.

  • Confluence is where context lives — specs, runbooks, leadership updates; discussion should live next to that context.

  • Delivery tools need a bridge — Jira holds tickets; Confluence holds narrative. This app links the two without replacing either.

Where work happens

Conversation hub -- Converse Home is a forum hub macro on a Confluence page that becomes the home for conversations (topic threads). Each conversation can have an optional child Confluence page so content is discoverable in global search and in the editor. Participants use the in-page experience to read, reply, like, subscribe, and—where licensed—mark structured signals (like lighting a watch tower) to work with Jira.

Traceability

Converse Hub automatically saves all conversations and each reply to the conversation's Confluence page. That traceability includes tying confluence and Jira together. We are introducing the concept of signals (decision, action, question, risk). They capture structured items on a topic or reply, support status, and can connect to Jira where your workflow requires it. It provides the framework and link to tract activity between the narrative and the execution. That keeps “we agreed in the thread” aligned with “we track it in Jira”—without forcing every comment to become an issue.

What it is not

  • Not a replacement for Jira reporting or full project management.

  • Not automatic NLP that guesses commitments without user intent (the product is declare-first).

  • Not a bypass of Confluence or Jira permissions: access follows the host products.

  • Conversation Hub is not meant to replace Slack, Teams, Mattermost, or whatever you use for quick chats about meeting times. It is meant for those conversations you should be archiving and used to further the work.

Use Cases

  1. Onboarding and the documentation is outdated. The new employee currently would reach out via slack/teams/etc and ask for the new updated documents. Existing team member responds with what is needed and thinks, "Yea, I need to fix that documentation," but gets distracted before opening up a new tab, application to do so. And the need is forgotten.
    With Converse, they communicate in the space that hosts the documentation. They can use Signal to create a task to document what needs to be updated. Now its trackable, and can fit into the work flow. And the Signal dashboard provides easy visibility into important chat discovered tasks.

  2. The VP of Sales needs information from accounting, marketing and the production teams about a new product. Currently, they send out emails to the different teams asking for information. Once they have it, they use it to finish their task. The information is there, in their email. But nobody else can see it.
    With Converse, They can in the appropriate space create a page documenting their needs and insert the Conversation Hub--home macro and invite the appropriate co workers to help provide the information. And now, when someone else needs that info, it is searchable and available. And through Signals, they can see decisions made from the info.

  3. Today, coworkers have a multiday conversation about a task, or a product, or issue. They figure out a resolution, but before they could implement it, another priority pulled them away. Someone else is assigned the task but they don't have access to that conversation and have to re invent the wheel or spend an inordinate amount of time tracking down the others to figure out what had already been decided.
    With Converse they can access the page and the conversation. They can see right away what was going on, but even better, when the inspiration strikes in the conversation, the original employee can create a signal, create a ticket and document what needs to happen and place it into your workflow. Thus preserving what needs to happen.