💬Conversation Mode

Group messages from the same user and translate them together for better context and improved efficiency — a Pro exclusive feature.

Conversation Mode is a Pro exclusive feature. Learn more about Pro.

What is Conversation Mode?

Conversation Mode makes iTranslator smarter when users send multiple messages in quick succession. Instead of translating each message individually the moment it arrives, the bot waits for a configurable delay and groups all messages sent by the same user in the same channel during that window. All batched messages are then translated together as a single unit.

This gives the translation engine more context, producing more natural and coherent results, while also reducing the number of translation calls made on your server.

How does it work?

1. A user sends a message in a channel where iTranslator is active.

2. Instead of translating immediately, iTranslator starts a timer (your configured delay).

3. Any additional message sent by the same user in the same channel before the timer expires is added to the batch.

4. Once the timer fires, all batched messages are translated together.

Messages that contain embeds are translated immediately and are not added to the batch — they always bypass the delay.

Commands

All Conversation Mode commands require the Manage Server permission and an active Pro subscription.

Command	Description
/conversation-mode delay <delay>	Sets the batch delay in seconds (0–10). Setting 0 disables Conversation Mode.
/conversation-mode help	Displays a summary of the feature and the current batch delay configured on your server.

Example — set a 3-second batch delay:

/conversation-mode delay 3

After this, any user who sends several messages within 3 seconds will have all of them translated together.

Set the delay to 0 to disable Conversation Mode and return to standard per-message translation.

Conversation Mode vs Standard Translation

	Conversation Mode	Standard Translation
Availability	Pro only	All users
Processing	Batched after delay	Immediate per message
API efficiency	Higher (fewer calls)	Lower (one call/message)
Translation context	Grouped messages	Each message independent
Embed messages	Processed immediately	Processed immediately

Tips

• Start with a short delay (2–3 s). It's long enough to catch rapid follow-up messages while still feeling responsive to your users.

• Use 0 to disable. Running /conversation-mode delay 0 disables the feature without any other changes needed.

• Best for active communities. The feature shines in busy channels where members often send multiple short messages in a row.