Limits and Troubleshooting
What's kept. Live support keeps conversations while they're active; it isn't a ticket history. The questions and answers stay in Analytics, and form submissions in your leads.
| Problem | What to check |
|---|---|
| Couldn't connect to live support. Retrying… | Your connection to Seekdown. The console reconnects by itself |
| A conversation you expect isn't in the list | Check that you attend its assistant, and the assistant selector in the toolbar. Visitors who haven't written are under Browsing |
| Another agent is already handling this conversation. | Someone else holds it. Wait until they hand it back |
| The visitor is offline: forms need their chat open | Website visitors need their chat open to receive a form. Write a message instead; it's delivered if they come back |
| No desktop notifications | Allow notifications for the dashboard in the browser, and check that your system's focus mode isn't hiding them |
| The visitor has no name | Your website doesn't pass userInformation. See See Who You're Talking To |
Can a website visitor ask for a person?
On the website, you choose when to step in from the console. If you want visitors to leave their details for a person, add a contact form with an activation trigger (see Surface a Form Automatically). On WhatsApp, customers can ask for a person directly.
Does the assistant learn from my replies?
No. Your messages go to the visitor as they are. The assistant keeps answering from its own content when you hand the conversation back.