📊Post Campaign Analytics
This page explains how to get the most of out of campaign analytics.
Last updated
This page explains how to get the most of out of campaign analytics.
Last updated
Post cal analysis is built of three independent feature::
Questions
Information to Gather
Webhooks
These are the questions a VoiceGenie user provides when creating a campaign. At the end of a call, VoiceGenie analyzes the conversation between its assistant and the customer to answer these questions using responses from the Possible Answers set. These answers are displayed on the call details page within the campaign analytics. A shorthand is required, which will serve as the column name identifying the question on the analytics page.
Users might seek specific information from each call, with each piece of information referred to as an entity. For instance, users may desire the extraction of meeting dates, addresses, emails, ages, etc., if mentioned in the conversation. By default, email, name, and location are collected, and users have the option to add two more entities, resulting in a total of five entities collected per call.
Webhooks serve as URL endpoints where VoiceGenie can send call-specific/customer-specific data at the conclusion of each call. Users can add these webhooks in the Actions tab within the assistant page. When selecting a specific assistant in a campaign, users will receive a list of the added webhooks associated with that assistant. Alternatively, users can directly add webhooks on the campaign creation page.
The default entities, along with any additional entities added by the user, will be included in the webhook data. These webhooks can be employed to automate various processes. For instance, you can integrate a Zapier webhook to streamline the meeting booking process. In your script, prompt users to provide their meeting date-time and email. Then, set up a Zap (Zapier flow) to receive this information from VoiceGenie, enabling Zapier to handle the meeting booking automatically.
