Features & Bugs

i cant choose tags from recordings in call history i must go to recording tab to choose tag for a recording

https://www.loom.com/share/08e1b0c6cf1849658ce752d1b67ba9bb

The idea is to copy the default summary prompt to a transcription rule so that different rules can have different prompts

Currently, when transcription service is activated, call recordings are transcribed and summarized as set in the Settings. So there is just on summary prompt that is applied to all call recordings. I see some possible improvements here: Assign a custom summary prompt for each transcription rule. Still apply the default one if not set on rule level. Copy applied summary to the call recording record where summary is attached. Allow to change this summary prompt. On prompt change send the transcript to the ChatGPT to create a new summary. That means we should refactor summary from a Text field to a One2Many field to generated summaries.Or, simplier, leave it as a Text but join with previous summaries. Create a mass record summarize action to query on multiple call records. More ideas?

The idea is to add to the Agent a HTTP server with one page nifty JS just to show a live dashboard similar to QPanel. https://github.com/roramirez/qpanel/blob/master/samples/animation.gif

When sending AMI events sometimes odoo is busy (restarting, upgrading, transaction errors) so in this case the event is lost. If it is a Hangup event then call is stuck in Active Calls. We need to handle such case and retry the rpc query.

sometimes it's necessary to keep a lot of recordings and there are some specific datastores with specific discs. Please add a possibility to keep these files instead of uploading to odoo and add availability for odoo just to use record link

When forwarding calls its not clear who you are conntected to if connected to customer or other agent. You do not see if customer is on hold or he can hear you back again.

It's possible to run the Agent middleware right on the Odoo server. We don't know yet how much delay can be between Agent and Asterisk from the AMI events point of view as the Agent receives many events but when Odoo & Asterisk are not too far from each other it must work smooth. So, this kind of feature will dramatically simplify the setup and AMI connection. The only thing that we should take special care is getting call recordings using Asterisk built-in HTTP server with static mapping and doing recording cleanup from cron on Asterisk. So, documentation will follow.

Integration with knowledge base module especially the one on Odoo 16 enterprise.