Forward Signature Service Notification with airSlate SignNow

Forward signature service notification

This video introduces the features for communicating with users through email and notifications. Linked time codes for these topics appear in the YouTube description for this video. The system can take action in response to email messages from users… …and send notifications, such as email or text messages, to users. First let’s look at inbound email actions... ... actions that the system takes in response to messages from users. When the system receives a message from a user... ... it can respond based on the contents of the message. This lets users perform system functions by email... ... like creating or updating an incident or change request. The system can take two types of actions in response to a user’s message. It can make changes to a system table… …or it can send the user an email message in reply. Let’s look at an example. Suppose Beth is having trouble running a report she needs. She sends a brief email message to the system describing the problem. It’s just an ordinary message; she doesn’t have to follow any special format. In response, the system creates a new incident. The system uses information in the message to populate fields in the new incident. The sender’s name goes in the Caller field… …and the subject line becomes the Short description. As system administrator... ... you control what the system looks for in each message and the actions that the system takes in response. The base system comes with predefined actions for creating or updating an incident or change request... ... replying on a live feed, and many more. You can modify these actions and create new ones of your own. For more information on configuring inbound email actions, refer to ServiceNow product documentation. Now let’s look at notifications, such as email and text messages... ... that the system sends to users to inform them of system events. Notifications are triggered by system events, such as changes to tables. Whenever a record is created or updated, the system can send an email or text message to certain users to inform them of the change. For example, if a user closes an incident... ... the system can send a message to the user who opened the incident to let her know it's been closed. Remember Beth, who was having trouble running that report earlier? When she created the incident, the system sent her a notification that the incident had been opened. As system administrator, you control the changes that trigger notifications, as well as their content. To see the notifications currently defined in the system, navigate to System Notification > Notifications. The base system comes with a variety of notifications, and you can create new ones of your own. To create a new one, click New. To view or edit an existing one, click the name in the list. Here’s the name of the notification… …and the table it applies to. The When to send tab shows the conditions that trigger the notification. In...