Feature Requests

We’re aiming to establish a consistent ordering logic across all queue and topic selections within INVO. For example, when creating text threads, we want the options to default to alphabetical order. This same ordering behavior should apply uniformly across all queue and topic configurations to ensure a predictable and user-friendly experience.

Access to view the previous day notes that were entered when call was placed.

Client Request: We would like to put in a feature enhancement request. We would like to request that when the caller is calling in to start a video banking call, we would like for the system to be updated to where it is not required for the caller to turn on their webcam. If needed, the agent can request the caller to turn on the webcam once the intent of the call has been established.

we have a situation where we want to keep a web channel open for later hours than other channels for certain queues. The enhancement request would be to allow granular control of a channel's hours for each queue.

given an agent assigns a Member from the lobby to a queue When it is past the queue open hours then an alert should notify the agent that the queue is closed.

when a third person joins the call through our platform, that person basically has no rights to the call and is in a "view only" kind of status. They cannot participate in co-browsing, docusign, etc. this enhancement would be to make a third party able to participate in those actions.

As a user of the Invo Text Platform and utilizing multiple Text Numbers when incoming texts are displayed on the dashboard I would like to see a filtered list (Via Nesting) via number, then via queue. Current Nesting: Text➝Queue Nesting option: Text➝Number➝Queue

Currently, smart suggestions give the most recent successful intents as the chatbot suggestions. I think it may be better to make the smart suggestions be based off of the most frequently used successful intents. This would give FIs a better understanding of how their client base are using the chatbot, and would give end users prefilled suggestions based on the frequency of similar users.

We recently went through and removed all reference of the agent's last name for their safety, it was discussed that some client's may like to be able to show their agent's last initial for professionalism. We should add a toggle setting to the 'Core' section of the settings, within the 'General' subsection that when enabled displays the agent's last initial in all interaction types: