problem resume conversation with built in bot
ART-4256_KNOWLEDGE_NODE-10
following method:\n\n[code]\n\n    1| DevRev.showSupport()  \n    ---|---\n[/code]  \n  \n### Creating a new support conversation\n\nYou can initiate a new support conversation directly from your app. This method displays the support chat screen and simultaneously creates a new conversation.\n\n[code]\n\n    1| DevRev.createSupportConversation()  \n    ---|---\n[/code]  \n  \n### In-app link handling\n\nIn certain cases, tapping links in the support chat opens them in the app instead of a
DevRev SDK for React Native — DevRev | Docs
ART-4206_KNOWLEDGE_NODE-8
"event": { |\n| > | "input_message": { |\n| > | "message": "Your query to the agent" |\n| > | } |\n| > | }, |\n| > | "session_object": "unique_conversation_identifier", |\n| > | "webhook_target": { |\n| > | "webhook": "don:integration:dvrv-us-1:devo/0:webhook/auCJ7By8" |\n| > | }, |\n| > | "client_metadata": { |\n| > | "user_id": "12345", |\n| > | "conversation_id": "conv-789" |\n| > | } |\n| > | }\' |\n```\n\n##### \n\nThe session\\_object parameter is critical for maintaining conversation
Agents async API | DevRev | Docs
ART-2895_KNOWLEDGE_NODE-2
view their past conversations. Identifying your users also enables more personalized engagement.\n\nIn this flow, you have to generate a session token for every user who visits your website. The session token identifies the customer when they interact with the widget. The session token is generated using the application access token and customer information. It should be generated on your website\xe2\x80\x99s back end since the app token needs to be kept hidden.\n\nTo identify logged-in users,
Identify your users with PLuG — DevRev | Docs
ART-2035_KNOWLEDGE_NODE-34
minutes after a conversation is created.\n* Any new message sent directly in the channel within this time frame is appended to the existing conversation.\n* A new direct message from the customer resets the roll window timer.\n* Any message sent from DevRev will be synced to the thread of the first message that initiated the conversation.\n* Only messages within the thread of the originating message of the conversation are synced.\n* Messages within Slack threads of follow-ups sent directly to
Slack | Integrate | Snap-ins | DevRev
ART-6174_KNOWLEDGE_NODE-27
happens automatically:\n\n* The original conversation moves to *Archived* stage and cannot be reopened.\n* A new ticket is created with:\n  + All internal discussions and customer messages copied from the conversation\n  + Equivalent metadata as the conversation, including source channel, customer account information, and external members added as **reported by** on the ticket\n  + An AI-generated ticket title and description based on customer messages\n\nConvert conversations to
Conversation to ticket conversion | Conversations | Computer for Support Teams | DevRev
ART-1974_KNOWLEDGE_NODE-33
have been addressed.\n\n  A conversation set to *resolved* still shows in the end-user's widget. If they respond again, it reopens the conversation and set the status to *needs response*.\n* *Archived*\n\n  The final stage for conversation.\n\n[PreviousTicket-Team Performance](/docs/dashboards/ticket-team-performance)[NextConversation to ticket conversion](/docs/product/conversation-ticket)\n\n#### On this page\n\n* [Stages](#stages)\n\n[Enterprise grade security to protect customer
Conversations | Computer for Support Teams | DevRev
ART-2035_KNOWLEDGE_NODE-33
DevRev app.\n\nIf a message is sent to a Slack thread belonging to an archived conversation, the Slack snap-in creates a new follow-up conversation, and all messages sync to this new conversation.\n\n![]()\n\nA Slack channel can be linked to only one DevRev account workspace, and vice versa.\n\nConversation roll window\n------------------------\n\nTo avoid multiple conversations for related customer messages, a **conversation roll window** is used.\n\n* The roll window remains active for five
Slack | Integrate | Snap-ins | DevRev