/
Notifications Preferences

Notifications Preferences

EVA understands that everyone has their unique preferences. That's why we offer you the ability to fine-tune your notification experience.From EVA Bot messages to SMS notifications and even missed calls, everything is neatly housed within the comforting chimes of your bell icon. 

 

Setting the Stage: In-App and Email Notifications

EVA unfolds two exquisite types of notifications:

  • In-Application Notifications: These notifications appear directly within your EVA instance, via the bell icon in the top right corner of an instance. 

  • Email Notifications: Notifications are sent to a desired email address registered to the platform.

Best Practices :

For an optimal experience, EVA recommends setting up both in-application and email notifications. This ensures you catch every note and maintain a rhythm in your workflow.

Admin Privileges for Notifications preferences

Only system admins have access rights to manage notification preferences within EVA. Follow these steps for turning the notifications on or off for each Agent:

  • Click on ‘Organisation’ > ‘All Agents’ to access the notification management window for your team.

  • Select the team member of your choice and navigate to ‘Notifications’ in the right panel to curate their notification settings.

  • A new window opens, allowing you to edit the global notification settings within EVA. 

  • Click on the edit icon (pencil) in the top right corner of the screen and

  • Select one of the options from the dropdown: ‘on’, ‘off’ and ‘Relevant’ .

What each option in the dropdown signifies:

  • All: Choose 'All' If you want this agent to receive all notifications regarding this type of event

  • Relevant Only: Agents will receive notifications if there is a previous history of interactions with this agent if you select ‘Relevant’ option for the event

  • Off: This agent will not receive any notifications regarding this event

EVA system offers various notifications(events) to keep you in sync with candidate interactions:

  • Eva takeover: Candidate requests to speak to a human

  • Registration completed: Candidate completes registration with EVA Bot

  • Incoming-sms-candidate*: Candidate sends a message to Agent. Missed-call-candidate*: Candidate attempts to reach out via call.

  • Unrecognized intent: Notification when Eva Bot doesn’t recognize candidate utterance

  • GDPR request: GDPR-specific candidate requests

  • Interview-booked:Ask your Customer Success Manager to demo this feature

  • Interview-not-completed: Ask your Customer Success Manager to demo this feature

  • Campaign completed: EVA Bot campaign is completed

  • Incoming-sms-contact*: Contact sends a SMS  to the Agent

  • Missed-call-contact*: Contact attempts to reach out via call

  • Missed-call*: A missed call in Twilio.Phone number belongs to a user which has Candidate profile 

  • Candidate-complaint: Candidate has made a complaint

  • ​​Pipeline-state-changed**: When there is a positive pipeline transitions (Negative transitions will not be notified)

  • Job-state-changed**: When there is a positive Job state transition (Negative transitions will not be notified)

  • Placement-state-changed**: When there is a positive Placement state transition (Negative transitions will not be notified)

  • Job-request-state-changed**: When there is a positive Job-request state transition (Negative transitions will not be notified)

  • Eva-job-inquiry: When there is a job related enquiries by the candidate

*- Requires Twilio to be enabled 

** - These transitions can be configured in the EVA Business Workflow as transition actions (Utils > Business workflows > click on any of the workflow transitions).For more information on Workflow transitions, kindly refer to the article Workflow Transitions 

Once you are satisfied with the configured settings, click on the ‘Submit’ button.