What should I verify before I mark a channel as live?

Confirm the connection status is healthy, send a real test message through the channel, and check that the conversation lands in Inbox with the expected agent assignment.

Why are there no conversations in Inbox after setup?

The usual causes are a disconnected channel, no real test traffic, or a route mismatch between the live channel and the intended agent. Check channel health first, then send a real message.

Why does Analytics still look empty?

Analytics is usage-driven. You need actual conversations or token activity before the baseline becomes useful. If Inbox is active, give the charts a short time to populate and then refresh.

Where do I manage who can operate the workspace?

Use Settings and your workspace user-management flow to confirm tenant membership, role scope, and the organization details that affect rollout ownership.

GuideFix blockers

Common launch blockers

Diagnose the first rollout failures quickly: connection not live, knowledge not indexed, no responses, no conversations, or access confusion across the team.

Aploai7 min readUpdated Jun 20, 2026

Open Connections Open Knowledge Open Inbox Open Settings

The connection shows configured but is not truly live

Connection status is healthy, not just configured.
A real inbound message reaches Inbox.
The conversation attaches to the correct workspace or agent route.

Knowledge exists but the answers still feel generic

This usually means the source is noisy, incomplete, or not the actual customer source of truth. In Knowledge, review extracted FAQ items or documents and remove stale or irrelevant content before uploading more.

No responses or no conversations show up

1Verify connection delivery first in Connections.
2Send a fresh real-world test message.
3Check whether the agent is assigned and whether the workspace health surfaces reflect live activity.

Operators cannot reach the right setup surfaces

Access confusion slows down every fix. Confirm the rollout owner can reach Settings, every Agent Builder section (including Connections and Knowledge), Inbox, and Analytics before trying to debug behavior downstream.

Escalate access early

Do not work around missing access with screenshots and handoffs if the operator is meant to own the launch.