Welcome Message Channel Linking Flow

Summary

Channel linking quality determines whether welcome DM automation can execute. This guide covers verification checkpoints. For operators, this page should be used as a decision surface, not only as a UI form. Always pair page actions with downstream validation in the relevant live workflow.

What this page is for

• Complete channel linkage reliably.
• Confirm channels appear in active settings.
• Avoid silent partial setup states.

Before you start

• Have fresh link code.
• Know target channel identity.
• Ensure bot permissions match channel requirements.

Step-by-step workflow

1. Generate or confirm active link code.
2. Perform channel linking action flow.
3. Return to Welcome Message settings list.
4. Verify channel appears with valid id/title state.
5. Check enabled toggle/status for the linked channel.
6. Run a live join request test when possible.

Key states and error handling

• Recently linked channel detection updates UI state.
• Pending detection entries are hidden from active list.
• Valid linked channels should surface in settings summary.

Best practices

• Link one channel at a time and validate immediately.
• Maintain clear naming conventions for channels.
• Retest after any channel migration.

Troubleshooting

• If channel not visible, verify it is not stuck in pending detection.
• If wrong channel linked, unlink/relink with fresh code.
• If setup looks correct but DM does not fire, test with fresh join request.
• If issue persists after one clean retry, capture exact toast/banner text, selected bot, and timestamp before escalation.

UI reference (what each control does)

• Bot selector scopes all welcome configuration and statistics.
• Link code generation is required for channel linking workflow.
• Copied code action should be confirmed before channel setup steps.
• Settings list excludes pending_detection placeholders from active view.
• Metric cards track request volume, sent DMs, approvals, and failures.
• Starter access gate can block configuration workflows.
• Recently linked channel detection should update state shortly after linking.
• Operational quality is measured by trend of failed DM rate over time.

Operator checklist (before shipping changes)

• Confirm selected bot before generating link code.
• Generate fresh code right before linking action.
• Verify channel appears in active settings after linking.
• Monitor failed DM trend daily during growth periods.
• Retest join-request path after any configuration update.
• Record bot/channel ownership for incident handoff.

Real-world scenario

DM failure rate rises while request volume is stable. The operator confirms bot scope, regenerates code, validates channel linkage integrity, and runs a controlled join request test to restore normal sent/approved ratios.

1. Identify the exact scope (bot, period, module) before any change.
2. Apply one targeted correction based on observed UI state and messages.
3. Validate outcome in the live operational flow linked to this page.
4. Document the final state so future incidents can be solved faster.