Choose support spaces
Start with product help, troubleshooting and approved policies rather than the entire company wiki.
Integrations Confluence
ConfluencePlanned
ConfluencePlannedConfluence knowledge. Customer-ready answers.
Plan a Confluence knowledge connection that selects useful support pages while keeping internal spaces and restricted notes private.
Planned connector. Native setup is not available yet. The workflows below describe the intended scope; release depends on provider access and testing.
Knowledge
What we’re planning to connect.
- 01Confluence
- 02Planned connection
- 03Message support
Review before reuse
Proposed ingestion would let owners separate material for agents from material safe for customer answers.
Follow source changes
The planned workflow needs to handle revised pages, removed access and deleted articles so old advice does not persist.
The right context
Be precise about what connects.
Define the data, permissions and destination before putting the workflow in front of customers.
Selected spaces and pages
Page versions
Access and deletion state
Prepare for the connection
Define your first workflow.
- 01
Choose the first workflow
Identify a small support space and mark pages that are safe to use with customers.
- 02
Agree on data and permissions
Decide which fields may be read, which people may use them and whether any separate write action is needed. Native setup is not available yet.
- 03
Define the acceptance test
Remove permission from a test page and verify it stops being used in customer-facing retrieval.
Before you connect
Confluence integration questions
Can I connect Confluence to Message today?
The native connector is planned. The workflows on this page describe the proposed design; there is no native installation to activate yet.
What should we test before using it with customers?
Remove permission from a test page and verify it stops being used in customer-facing retrieval.