Welcome Message Overview and Prerequisites

Summary

Welcome Message depends on bot connectivity and plan access. This article defines minimum readiness before setup. 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

• Clarify feature prerequisites.
• Prevent setup attempts in blocked state.
• Define expected page outcomes.

Before you start

• At least one bot connected.
• Starter access enabled for selected bot.
• Operator has the correct bot selected.

Step-by-step workflow

1. Open /dashboard/welcome-message.
2. If multiple bots exist, select target bot.
3. Check cards and linking area load correctly.
4. Generate link code only after confirming bot context.
5. Link channel using generated workflow.
6. Monitor stats for first outcomes.

Key states and error handling

• No bot panel: 'Connect a bot to enable welcome messages.'
• Starter gate can block configuration.
• Settings list filters out pending_detection channels for active view.

Best practices

• Assign one owner per bot welcome setup.
• Avoid switching bot mid-setup.
• Document linked channel list externally for audits.

Troubleshooting

• If page blocked, verify bot and plan prerequisites.
• If wrong bot data shows, update botId query context.
• If stats stay zero, verify real join activity exists.
• 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.