client not receiving messages sent via DevRev but ticket shows delivered
ART-2027_KNOWLEDGE_NODE-33
Transit*: This email is now queued for outbound. DevRev is attempting to send this email, and the process is currently in progress.\n* *Sent*: DevRev has successfully sent this email. At this point, the email is *on its way* to the intended recipient.\n* *Delivered*: DevRev has successfully delivered this email to the recipient's email server.\n\n  ![]()\n\n  Even if DevRev delivers the email, the recipient's email server may quarantine the email, or it may end up in the recipient's junk or
Email | Integrate | Snap-ins | DevRev
ART-3207_KNOWLEDGE_NODE-55
test email to your configured address from the deliverability tool and confirm that a conversation or ticket is created.\n2. Respond from the test conversation or ticket in DevRev to the address mentioned in the deliverability check tool.\n\nYou need to add the address as a contact, which can be done in the email composer page.\n\n1. Check the status of the email sent by coming back to the chosen tool.\n\nIf the **DMARC Compliance checks** on the tool pass, then DevRev email is
Email snap-in configuration | Email | Integrate | Snap-ins | DevRev
ART-2027_KNOWLEDGE_NODE-34
spam folder. Despite this, DevRev still registers a *Delivered* event, as the email has reached the intended recipient's server.\n* *Bounce*: The recipient's email server rejects the message, which can happen for several reasons. These may include the email address no longer existing, a typo in the address, or the email failing to meet the recipient server's security policies. The specific reason for the bounce is detailed in the Bounced event. The sender is notified whenever their email
Email | Integrate | Snap-ins | DevRev
ART-2027_KNOWLEDGE_NODE-29
your communication requirements.\n\nThe visibility and interaction capabilities with a ticket in DevRev are determined by the user's role and how they were added to the email thread.\n\nEnd users\n\n* Original sender\n\n  *Added to:* **Reported by** or **Email members** field.\n\n  *Is able to:* View the ticket on the portal and reply via email.\n* An end user in the same organization\n\n  *Added to:* **To** or **CC** fields in the email thread; **Reported by** field, **Email members** field,
Email | Integrate | Snap-ins | DevRev
ART-15515_KNOWLEDGE_NODE-43
configure your app to receive push notifications from the DevRev SDK. The SDK is designed to handle push notifications and execute actions based on the notification\xe2\x80\x99s content.\n\nThe DevRev backend sends push notifications to your app to notify users about new messages in the Plug support chat.\n\n### Configuration\n\nTo receive push notifications, you need to configure your DevRev organization by following the instructions in the [push notifications](/sdks/push-notifications)
Features | DevRev | Docs
ART-12460_KNOWLEDGE_NODE-27
12| const messageJson = notificationPayload["message"];  \n    13|   \n    14| DevRev.processPushNotification(messageJson, function() {  \n    15| \tconsole.log("Push notification processed successfully.");  \n    16| }, function(error) {  \n    17| \tconsole.error("Failed to process push notification:", error);  \n    18| });\n[/code]  \n  \n#### iOS\n\nOn iOS devices, you must pass the received push notification payload to the DevRev SDK for processing. The SDK will then handle the
Features — DevRev | Docs
ART-1471_KNOWLEDGE_NODE-1
timeline of an object by using the `timeline-entries-create` API. These messages are only visible to the specific users you give access to.\n\nThe [timeline entries](/public/api-reference/timeline-entries/create) API is used to create discussions (comments) on the timeline of an object such as a ticket or issue. These messages can be sent by users or by a bot. You can use this to send any information about a customer like their last logged in date and time, the last page they visited, or an
Restricted messages on a timeline — DevRev | Docs
ART-1265_KNOWLEDGE_NODE-8
"don:core:dvrv-us-1:devo/<dev-org-id>:conversation/172:comment/xqsvvdwvt6hjw", |\n| 17 | "object": "don:core:dvrv-us-1:devo/<dev-org-id>:conversation/172", |\n| 18 | "object_type": "conversation", |\n| 19 | "visibility": "private" |\n| 20 | } |\n| 21 | } |\n```\n\nYou can check the object to which you sent a message in the UI. It\xe2\x80\x99s visible to the creator and the users you added in `private_to`.\n![]()\n\nSummary\n-------\n\nIn this tutorial, you learned how to post a comment on the
Restricted messages on a timeline | DevRev | Docs
ART-12460_KNOWLEDGE_NODE-23
require SDK configuration and user identification, whether unverified or anonymous, to ensure delivery to the correct user.\n\nThe DevRev SDK offers a method to register your device for receiving push notifications. You can register for push notifications using the following method:\n\n[code]\n\n    1| DevRev.registerDeviceToken(deviceToken, deviceID, successCallback, errorCallback)  \n    ---|---\n[/code]  \n  \nOn Android devices, the `deviceToken` should be the Firebase Cloud Messaging (FCM)
Features — DevRev | Docs