Sending EVI call info (summaries, structured data) to webhook URL after calls
J
Jeremy Hadfield
Once we add webhooks, it will be possible to send info to the webhook URL after each EVI call. This webhook could be linked to the developer's server, or used to do things like post slack messages to the user's channel.
For example, some things we could send over the webhook at the end of EVI calls:
- Generated call summaries
- Main conversational topics (potentially with the major expressions per topic)
- Structured data defined by the user (e.g. action items, conversation issues)
- Voice metrics (e.g. avg number of words per turn for user and assistant, silence/pause length, etc)
- The call's audio recording
- Data on the user's expressions, e.g. spikes in frustration, averages, top 3 expressions, satisfaction score
- Other things
Community question: What other information would be helpful to send over a webhook after EVI calls?
Josh Goldberg
Having access to the raw audio data is necessary for auditing the chat sessions since transformer STT models are susceptible to hallucination.
I know I can capture the audio on my own, but I'd rather not double the bandwidth usage for the user.