Curate a support collection
Choose files that answer recurring support questions while excluding contracts and personnel records.
Integrations Box
BoxPlanned
BoxPlannedBox documents, with the right boundaries.
Plan a Box knowledge connector for selected customer-support files, with clear ownership, access checks and approval before AI use.
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.
- 01Box
- 02Planned connection
- 03Message support
Separate audiences
An employee’s permission to read a Box file is not permission to publish its contents to customers.
Track document changes
The proposed sync must retire deleted or inaccessible material and record the source of every imported document.
The right context
Be precise about what connects.
Define the data, permissions and destination before putting the workflow in front of customers.
Selected file identifiers
Approved text
Source access state
Prepare for the connection
Define your first workflow.
- 01
Choose the first workflow
Have a content owner select the initial support files and define which are public-safe.
- 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
Use one restricted file and one approved document to test that only approved information reaches customers.
Before you connect
Box integration questions
Can I connect Box 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?
Use one restricted file and one approved document to test that only approved information reaches customers.