FAQ

Login and seats

Q: Can the console password sign in to the desktop client?
A: No. The desktop client uses a seat activation code.

Q: Activation code invalid?
A: Confirm all 12 characters, that the seat is enabled, and that plan ports are sufficient.

Ports and sessions

Q: Cannot create more sessions?
A: Check whether the seat’s ports are full, or whether the plan has enough ports.

Q: WhatsApp / Telegram won’t connect after scanning?
A: Check network, proxy config, and whether the session needs a restart; try another network if needed.

Translation

Q: Translation not working?
A: Check plan quota, whether the selected route is available, and whether session-level translation is on.

Dispatch and tickets

Q: Dispatch short link won’t open or fans stay at 0?
A: See the troubleshooting table in Dispatch links; confirm accounts are online and filters are not too strict.

Q: Ticket data doesn’t match expectations?
A: Confirm whether it was just reset, whether the platform tab is correct, and whether accounts in detail are in scope.

Still stuck

See Glossary or Contact us.