Troubleshoot cases where MagicType does not show what a visitor is typing before they send a message.

MagicType depends on visitor privacy settings, network quality, and enough typed content to stream a useful preview. If one of those conditions is not met, the typing preview may stay disabled.

Check Do Not Track settings

Crisp respects the Do Not Track browser signal. If the visitor enabled Do Not Track, Crisp disables MagicType for that visitor to respect their privacy choice.

This behavior cannot be overridden from the operator side.

Check network quality

MagicType streams typing updates before the message is sent, which requires additional network activity. On slow or unstable connections, Crisp may disable MagicType to avoid degrading the visitor experience.

Common cases:

• Slow mobile networks → Edge, unstable 3G/4G, or weak Wi-Fi
• High latency → long delays between the visitor browser and Crisp servers
• Temporary instability → dropped packets or frequent reconnects

Check message length

MagicType does not stream every character immediately. To reduce unnecessary network usage, Crisp starts streaming after enough content is typed, usually when the visitor has entered a meaningful phrase.

Examples:

• Hello → may not enable MagicType yet
• Hello, how are you → is more likely to enable MagicType

If MagicType works for longer messages but not short ones, the feature is behaving as expected.

Updated on: 03/05/2026