Messaging Connections: Setup, Testing and Recovery

Open Dashboard > Messaging Channels. The add-connection list shows platforms available for your plan and account. This is separate from commerce Connections and Accounting Sales Channels.

Before you start

Use an authorized business account for the platform. Review plan availability and tenant currency: Bale, Eitaa and Rubika setup is tied to the Iranian currency region, not the dashboard display language. Changing currency does not itself create or authenticate a channel.

Prepare Business Profile, Knowledge Base and a small test conversation before routing real customers to AI. Keep tokens and secrets only in the designated connection fields.

Token-based bots

1. Choose the desired Telegram, Bale, Eitaa or Rubika bot connection offered by the panel.
2. Follow the provider-specific bot-creation instructions shown in the dialog.
3. Enter the connection name and bot token in its designated field.
4. Save/connect and wait for the returned status.
5. Use the saved-connection Test action where offered.
6. Send a message from your own customer-side account and confirm it arrives in DirectSale Conversations and receives the intended reply.

Use the correct provider token; a Telegram token cannot configure Bale. If a bot requires the customer to start a conversation first, do so from the customer-side account. Do not assume a Connected badge proves end-to-end delivery.

Meta authorization

1. Choose the available Meta platform and start its official authorization flow.
2. Sign into an account allowed to manage the relevant business/page/Instagram asset.
3. Review permissions and select the intended asset.
4. Return to DirectSale and verify the saved connection and diagnostics.
5. Configure reply modes, then test from a different customer-side account.
6. If webhook/subscription diagnostics report an issue, use the offered resubscribe/reconnect action after correcting permissions.

See Instagram Reply Settings and Meta Approval and Account Safety. Meta approval does not authorize spam or bypass account rules.

LINE and other available platforms

For LINE, use the dedicated dialog and supply the channel credentials requested there; these are not a Telegram-style bot token. Follow the displayed webhook/verification instructions and test an incoming event plus an outgoing reply.

For any additional platform, use only the connection method and fields actually offered by the panel. Availability can be restricted by plan or provider readiness; a disabled card is not an active integration. Consult Support rather than entering credentials for an unsupported platform into a different provider's form.

Manage an existing connection

Review its name, platform, Connected/Disconnected/error state and diagnostics. Test verifies the saved configuration; it does not necessarily prove every event type works. Disconnect stops the connection without meaning all remote permissions or historical conversations were deleted. Delete removes the configured connection through the offered confirmation; review operational effects first.

Verification and troubleshooting

Check one incoming message, its conversation record and outgoing response. For Instagram, test DM, story and comment separately. If no event arrives, inspect account/asset selection, token validity, webhook diagnostics and provider permissions. If an event arrives without a reply, inspect reply mode, Auto Reply trigger, handoff status and allowances.

After a timeout, inspect the existing connection before creating a duplicate. Do not disable TLS checks, publish tokens or repeatedly reconnect an account restriction. Report the provider, status and sanitized error to Support.