## TL;DR
An unpublished collection is invisible no matter how polished its articles are: collections have their own publish state separate from article states. Publish the collection, confirm its visibility settings for help center versus messenger, and trigger a sync. Then check that the articles inside are themselves published, because a published collection of draft articles is still empty.

## The query

```text
intercom "article collection not published" help center sync error
```

## Use this when

- Collections show as not published
- Articles exist but the help center is empty
- Help center and messenger show different content
- You are managing Intercom help-center content

## Not for

- Writing help articles
- Customizing help-center appearance
- Tuning article search ranking
- Setting up the messenger

## Steps

### 1. Check the collection's publish state

Open the collection and confirm it is published. Collections can sit in draft while their articles are published, which produces exactly this error. Publish the collection itself.

Expected output: collection confirmed published.

### 2. Check visibility: help center, messenger, or both

Collections target surfaces independently. A collection published to messenger only will not appear in the help center. Set each collection's surfaces deliberately.

Expected output: surfaces set correctly per collection.

### 3. Verify the articles inside are published

A published collection containing draft articles shows as empty. Check each article's state and publish the ones that should be live. Bulk-publish after review, not before.

Expected output: articles published, collection non-empty.

### 4. Trigger a sync and verify

After publishing, trigger the help-center sync and check the live site. Sync is not always instant; confirm the content appears before announcing the fix.

Expected output: live help center shows the collection and articles.

### 5. Set a publishing checklist for new collections

New collections should go through: articles published, collection published, surfaces set, sync verified. Make it a checklist so the next collection does not repeat the error.

Expected output: a written publishing checklist.

## Template: the checklist

```text
Collection not published:
[ ] Collection itself published (not just its articles)
[ ] Surfaces set: help center and/or messenger as intended
[ ] Articles inside published
[ ] Sync triggered and live site verified
[ ] Publishing checklist written for next time
```

## Variant phrasings

### intercom help center empty but articles exist

Steps 1 and 3. Collection state, then article states.

### intercom collection draft vs published

Step 1 as the core distinction.

### messenger shows articles help center does not

Step 2. Surface targeting differs.

## Why it happens

Intercom separates three publish decisions: article state, collection state, and surface targeting. Teams publish articles and assume the collection follows, or publish the collection to one surface and expect it everywhere. Each layer is a deliberate gate, and skipping any one produces an empty or missing help center.

## Edge cases

- Audience targeting: collections can target specific user segments. An empty-looking help center may be correct for that viewer.
- Archived articles: archiving removes from all surfaces instantly. Unarchive rather than republishing from scratch.
- Multi-language collections: each language needs its own publish pass. One language live does not imply the others.
- Staged rollouts: publish to a test segment first, verify, then open to everyone.

## Provenance

Resolved from the public thread: https://vectle.com/posts/pst_hDfXtw1HMnbqMSllgLrfjw