Customer email notifications

At DevRev, our commitment is to streamline collaboration and ensure that the teams and their customers are always in the loop. To help achieve this, we've established specific email notification rules. This section describes when and how email notifications are triggered within the DevRev platform.

The email senders and subject lines are subject to change based on organizational settings and preferences.

White-label customer email notifications

Organizations can personalize their email notifications by choosing a customized sender address and by incorporating their own logo, creating a more branded and professional appearance. Moreover, if customers reply to these notification emails, their responses will automatically be added to the relevant ticket or conversation, ensuring seamless and continuous communication.

By default, notifications are sent from notifications@devrev.ai. However, this setting can be overridden to use the organization’s primary email address as the sender, or notifications can be turned off entirely.

To configure the notifications setting, go to Settings > Snap-ins > Email Integration > Configure > Notification Sender Email Address and select the required option.

Reply to the customer on a conversation

Trigger: When a reply is made to a customer on a conversation and they are not online anymore.
Action: The system sends out a notification to the customer with the recent messages while highlighting the latest message that triggered the email.
Sender: {Sender_Name} support@yourdomain.com
Subject: "You are missing messages from <Org Name>"

Reply to the customer on a ticket

Trigger: When a reply is made to a customer on a ticket.
Action: The system sends out a notification to the customer with the reply message.
Sender: {Company_Name} support@yourdomain.com
Subject: "[{Company_Name}] Update on TKT-XXX"

Ticket linked to a conversation

Trigger: A ticket is linked to an existing conversation.
Action: The system sends out a notification with the linked ticket number.
Sender: {Company_Name} support@yourdomain.com
Subject: "<customer email subject from Conversation>"

This email is only sent to the organizations with Convergence snap-in

Change of stage of a ticket/conversation

Trigger: When there's a change of stage in a ticket or conversation.
Action: The system sends out a notification detailing the Ticket/Conversation number and stage change.
Sender: {Company_Name} support@yourdomain.com
Subject:
- For ticket: "[{Company_Name}] Update on TKT-XXX - Ticket Title""<customer email subject>"
- For conversations: “Update on your Conversation with {Company_Name}"

This email is only sent to organizations that have installed Convergence snap-in.

CSAT survey for conversation/ticket

Trigger: A CSAT survey is sent for a conversation or ticket.
Action: The system sends out a notification with the ticket/conversation number and CSAT form.
Sender: DevRev no-reply@devrev.ai
Subject: "CSAT for TKT-XXX"

This email is only sent to organizations that have installed CSAT snap-in.

Auto customer reply

Trigger: A new conversation is initiated from a customer.
Action: An automated reply is sent.
Sender: {Company_Name} support@yourdomain.com
Subject: "<customer email subject>"

This email is only sent to organizations that have installed Auto-reply snap-in.

Auto reply on email

Trigger: A new email is received from a customer.
Action: An automated reply is sent.
Sender: {Company_Name} support@yourdomain.com
Subject: "<customer email subject>"