This is a Beta API - Undergoing further development. If you have any suggestions, idea or questions about this API please reach us at firstname.lastname@example.org.
This API performs best when the audio is clear and meeting length is greater than 10 minutes. Longer length meeting are broken down by our algorithm in contextually relevant parts which helps in producing high quality topic hierarchy.
Topic hierarchy understands customer conversation and returns the parent (global) topic and it's child topics.
- Parent Topic: Identify the highest level abstraction of a meeting. These are the key points on which the speakers of the meeting expanded and discussed at length.
- Child topic: These are the subtopics that aggregate or are originated from the parent topic itself. Child Topics are the topics which are linked to the parent topic as they form the time chunks of the parent topics in a certain way.
|No||true||Gives you topic hierarchy when passed in Topic API.|
|For each topic in the response, it has a parentRefs field which point to its parent topic. If parentRefs is NULL it signifies that the topic is a parent.|
In sample diagram below that we created for your understanding. This shows how one conversation can have multiple parent (global) topics and each parent topic can have multiple child-topics in it.
For example, if in a meeting “Sales Conversation” was talked about and after it “Activity Call logs”, “Salesforce”, “Draft”, “Custom Integration” and “Jira” were talked.
So, the topic hierarchy algorithm will find a pattern in the conversation and make Sales Conversation as the parent topics and the rest of the topics as the child topics under it.