-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Webhook changes for missed calls and other call types #68
Comments
@prtkdost Please go through the issue and add some more details wherever required (especially regarding different flow categories, what all we are going to capture in each categories). |
For Missed flow - “missedcall”’ sharing my findings and considerations below: Call logs table changes
Flow changes:
Capturing flow categories:
|
Updated the requirements in the issue description, sharing the highlights below.
|
…nt-flow-categories #68 handling different flow categories
This is deployed on prod and tested as well. Closing this item |
Is your feature request related to a problem? Please describe.
Currently, the system is partially capturing missed calls. Apart from that, the system is handling registration and content flow categories.
Describe the solution you'd like
We need to handle other flow categories as well to capture more details. These details can play critical role in generating different metrics.
The flow categories we need to handle are:
Call categories:
Flow categories:
Describe alternatives you've considered
None
Additional context
The flows categories tell the system to capture different data set specific to that category.
For example: the registration flow categories tells system that we need to capture users registration details.
The text was updated successfully, but these errors were encountered: