Integration Suggestion

Bank transaction reconciliation is a common scenario in a back/middle office. In this scenario, a service agent needs to match bank statement transactions with a master file and identify any mismatched or unmatched transactions. These unreconciled transactions require further processing and approval. However, reconciliation work is often tedious and time-consuming when done manually. This makes it a perfect task to be automated with Enate AI. This is one example but we should be able to use Enate AI to solve other problems with this feature.

This container shall act as a primary middleware to communicate with underlying systems through APIs. Also flexibility to install and use different library packages of python shall be an added advantage.

As we have Enate AI which ignores Thank You email for resolved work items, it will be helpful to have same for OOO mails that comes after resolving ticket while its still in feedback window. Also, if there is no feedback window, and we send an email and close the work item, any OOO mail will create new item, this should also be catered.

As a System Administrator and BOT Implementer, I want to have a separate BOT password Sync policy, so that the password from UI Path Orchestrator can be synchronised with Enate immediately in case of any changes, currently the sync happens every 30 days.

For an integration, I want to utilise the schedules setup in Builder, instead of replicating the same data or manually adding or removing, a notification should be shared for any modification so that the systems remain in sync. This will include:  Removal of the schedule (soft delete) to include the data column for retired or not

For an integration, I would like to know which processes have been modified and or set live so this can be automatically be updated to use the latest template upon

Hi there New feature, not raised before - when you create a linked ticket within your own service line there should be an option when creating it to ‘Keep with me’ currently team have to catch the ticket number and assign it to themselves thanks

We have capability to create the contact automatically, but for some emails Enate is not getting the first name and because of that while sending the email to that email id(if tagged as requestor, cc etc.) Enate gives validation error that “Please specify the first name for the X email.” As an Ops user, I would like to have the feature to auto capture the email first name for all emails to avoid the additional clicks/work. Like when Enate is not able to capture the first name it should put the email id before “@” as the first name.

We would like to decouple the relationship between the agent account and the app credentials so that when the agent account password expires or is changed that we do not then have to reauthorise the application credentials. Currently if the agent password is changed then the application credential will stop working also as the secret key expires

Requesting enate to support outgoing emails using the MS Graph API connector. Currently, enate MS Graph connector only supports incoming emails.