automated reminder to customer ticket will be closed in 4 days
ART-3068_KNOWLEDGE_NODE-24
[Documentation](/docs)\n3. [Snap-ins](/docs/snapins)\n[Automate](/docs/automate)\n[Conversation reminder](/docs/automations/conversation-reminder)\n\nConversation reminder\n=====================\n\nThe Conversation Reminder Snap-in is designed to automatically send a\nnotification to the customer who initiated the conversation if it remains in\n"Waiting on User" stage for an extended period, as defined in the configured\ntime settings. The notification message sent to the customer can be
Conversation reminder | Automate | Snap-ins | DevRev
ART-3068_KNOWLEDGE_NODE-25
customized\nduring the installation of the Snap-in, allowing for tailored communication\naccording to specific requirements.\n\n![]()\n\nFor more information, refer to the\n[Conversation Reminder snap-in](https://marketplace.devrev.ai/conversation-reminder)\non the DevRev marketplace.\n\nInstalling the auto parts to conversation snap-in\n-------------------------------------------------\n\n1. In DevRev, go to **Settings** > **Snap-ins** and click **Explore\n   Marketplace** in the top-right
Conversation reminder | Automate | Snap-ins | DevRev
ART-1284_KNOWLEDGE_NODE-16
false |\n| 20 | end |\n| 21 | else false |\n| 22 | end |\n```\n\nScheduled events\n----------------\n\n`flow-events` are an event source that snap-ins can use to publish or schedule events directly. This event source can then be used to trigger another automation. This capability makes it ideal for building snap-ins that need to act later. For example, sending reminders to issues still in the *Triage* stage.\n\nYou create an event source of type `flow-events`, and from your snap-in, you call
Event sources | DevRev | Docs