Welcome Message Link Code Generation

Summary

Link codes are the operational handshake for channel binding. This article explains secure generation and usage practices. 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

• Generate reliable link codes.
• Reduce failed linking attempts.
• Keep code lifecycle controlled.

Before you start

• Select correct bot id.
• Ensure channel admin has action access.
• Prepare to copy code immediately after generation.

Step-by-step workflow

1. Open Welcome Message for target bot.
2. Trigger new link code generation.
3. Confirm success toast appears.
4. Copy code to clipboard and share securely.
5. Complete channel linking flow using the code.
6. Invalidate stale code by generating a new one if needed.

Key states and error handling

• Success message: 'New link code generated'.
• Failure message: 'Failed to generate link code'.
• Clipboard success: 'Copied to clipboard'.

Best practices

• Generate code right before linking action.
• Avoid reusing old codes across sessions.
• Store only short-lived references internally.

Troubleshooting

• If generation fails, verify selectedBotId exists.
• If copy fails, copy manually from displayed code value.
• If code seems expired, generate a fresh one and retry linking.
• 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.