Where conversations come from
The inbox is one list. What differs is how a reply gets back to the person.
The widget
Somebody writing on your website. Replies appear in their chat within a few seconds. If they leave and come back on the same browser, they see the conversation again, and they can start a new one alongside it.
Mail sent to your support address becomes a conversation, and a reply goes back as an email in the same thread. Replies from the customer land on the same conversation rather than starting another one.
Slack
A message in a channel you take intake from becomes a conversation, and your reply is posted back into that Slack thread under your name. Messages from your own team are ignored, as are bots and edits, so ordinary channel chatter does not become a queue.
Not every channel is an intake channel. One you only escalate into is send-only, which is the setting to check first if a channel is filling your inbox with replies to your own messages.
Crisp
Conversations imported from a connected Crisp, and new ones as they arrive if you have added the web hook. They read like any other conversation once they are here.