Skip to content
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

Closed
9 tasks done
Satendra-SR opened this issue Mar 31, 2021 · 4 comments
Closed
9 tasks done

Webhook changes for missed calls and other call types #68

Satendra-SR opened this issue Mar 31, 2021 · 4 comments
Assignees
Labels
enhancement New feature or request priority: high This issue or pull request is on high priority

Comments

@Satendra-SR
Copy link
Member

Satendra-SR commented Mar 31, 2021

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:

  • call back
  • scheduled call (default)
  • live call

Flow categories:

  • Registration flow - “registration”
  • For content delivering flow - “content”
  • Nudges flow - “nudge”
  • Survey flows - “survey”
  • Blast flow - "blast"
  • Other flow - "other" (should be default)

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.

@Satendra-SR Satendra-SR added the enhancement New feature or request label Mar 31, 2021
@Satendra-SR
Copy link
Member Author

Satendra-SR commented Mar 31, 2021

@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).

@Satendra-SR Satendra-SR added the priority: high This issue or pull request is on high priority label Mar 31, 2021
@Satendra-SR
Copy link
Member Author

For Missed flow - “missedcall”’ sharing my findings and considerations below:

Call logs table changes

  1. Need to add parent_run_uuid column which specify if the flow is being triggered by an another flow (parent)
  2. Need to add parent_flow_name column to capture the name of parent flow

Flow changes:

  1. Pass parent variable to webhook from each flow.
  2. The system will handle the call logs by checking if parent flow name is similar to missed call > mark the call as missed call else it will be a regular call.

Capturing flow categories:
Initially, we were discussing to capture flow categories in the call logs but it seems irrelevant here. We are capturing call log corresponding to a call (not flow), and one call can have multiple flow categories. For example, for first time missed call, it will run:

  1. missedcall flow
  2. registration flow
  3. content flow (most likely)

@Satendra-SR
Copy link
Member Author

Satendra-SR commented Apr 1, 2021

Updated the requirements in the issue description, sharing the highlights below.

  • Need to update the documentation (for flow naming conventions for missed call flow).
  • The flow categories is divided now into two part, see the updated description above.
  • Add new column to call logs (flow_category).

@Satendra-SR
Copy link
Member Author

This is deployed on prod and tested as well. Closing this item

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request priority: high This issue or pull request is on high priority
Projects
None yet
Development

No branches or pull requests

2 participants