Conversations: every customer thread in one place
A conversation is one customer's thread with you, whatever channel it came from. Website chat, email, WhatsApp, Instagram, Viber and Slack all appear in the same list, and the support assistant answers in all of them. Open Conversations from the sidebar.
threads list
The list
Each row shows the customer (anonymous visitors get a number until they identify themselves), the last message, when it arrived and who replied last. A green Starko replied chip means the assistant handled the latest message. Rows without it are waiting on your team.
Filter narrows by channel, status, assignee, tags and whether the assistant is handling the thread.
Search finds text inside messages.
Views saves a filter so you can come back to it. Views can be private or shared with the team.
Broadcast sends one message to many customers at once.
Start New Thread opens a conversation from your side, for example a follow-up by email.
threads filter
Inside a conversation
Open a row to read the whole thread. The customer's messages, the assistant's replies and your team's replies are in one timeline, with the channel shown on each message.
thread detail
From here you can:
Reply as a person. The assistant steps back while a human is handling the thread.
Assign the thread to a teammate or a team.
Tag it, or change its status to closed when it is done.
Create a ticket from the thread. The ticket keeps a link back to the conversation, and the customer gets updates when it changes.
Open the client record on the right to see the company, tenant, other conversations and tickets.
Human and assistant hand-offs
The assistant answers from your Knowledge Hub and the procedures you gave it. When it cannot answer, when the customer asks for a person, or when a procedure says so, it hands over: it alerts your team, or opens a ticket and tells the customer, depending on how you configured Settings → AI assistant → Behaviour. You can also take over any thread at any time by replying.
Summaries and sentiment
Closed conversations get a summary of what was asked, what was done and how the customer felt. Summaries feed Reporting and Topic Gaps, so recurring questions turn into articles and product fixes instead of repeat work.
Did this answer your question?