Connector Improvement: Pull in advanced insights if enabled for account
Answered
frankly, the call data is useless if we dont have certain insights like end_reason and ended_by on the conference level or disconnected_by on the call_summary level, for the price we are paying to ingest this data, duration by itself has minimal analytic value
https://www.twilio.com/docs/voice/voice-insights/api/conference/conference-summary-resource
https://www.twilio.com/docs/voice/voice-insights/api/call/details-call-summary
-
Official comment
Hi Daniel,
We see your request regarding advanced insights such as end_reason, ended_by, and disconnected_by for the Twilio connector. What are the full list of fields needed for conference_summary and call_summary? If only these fields end_reason, ended_by, and disconnected_by are necessary we can add those columns to the existing conference and call table. If there are fields specific to conference_summary or call_summary that are needed, please let us know.
Looking forward to your insights.
Thanks,
Frank -
Hi Daniel,
Thank you for your feature request. Currently, this connector improvement is not on our roadmap, but we appreciate your feedback. I encourage you to upvote this feature in our feature request portal to help us prioritize it based on demand. We continuously evaluate our roadmap, and your input will be valuable in our future planning.
Best,
Sandeep Preetam Saila
Please sign in to leave a comment.
Comments
2 comments