Actions59
- Blacklist Actions
- Call Actions
- Client Actions
- Entity Actions
- Import Actions
- Lead Actions
- PBX Actions
- Queue Actions
- Report Actions
- Get Daily Managements
- Get Dropped Calls
- Get Summary
- Get Time Slot
- Get Users Management
- Get Calls
- Get Client Management
- Get Forms
- Get Incoming Call
- Get IVR Survey
- Get Log ACW
- Get Managements by ACW
- Get Managements per Hour
- Get Messaging Tickets
- Get PDP Control
- Get List PDP
- Get PDP Ranking
- Get Phones
- Get Platform Detailed
- Get Platform Summarized
- Get Product Managements
- Get Products
- Get Progress Managements
- Get Strategies
- Get Tickets Tracking
- Sequence Actions
- Template Actions
- Ticket Actions
- User Actions
Report → Get Dropped Calls
AI-generatedOverview
This node interacts with the Beex Contact Center API to retrieve a report on dropped (abandoned) calls for a specified campaign portfolio and year. It is useful for customer service managers or analysts who want to monitor call abandonment rates within their contact center campaigns. For example, a user can specify a campaign ID and year to get detailed data on calls that were dropped, helping to identify issues in call handling or staffing.
Use Case Examples
- Retrieve dropped calls report for campaign ID '12345' for the year 2023 to analyze call abandonment trends.
- Use the dropped calls report to generate monthly summaries of abandoned calls for performance review.
Properties
| Name | Meaning |
|---|---|
| Portfolio ID | ID of the campaign in which the information will be filtered, obtained from the ID column in the Campaigns module on the platform. |
| Year | Year in which the information will be retrieved, formatted as YYYY. |
Output
JSON
json- The JSON output contains the dropped calls report data retrieved from the Beex API, which may include details such as call counts, timestamps, and other relevant metrics.
Dependencies
- Beex Contact Center API
- API key credential for authentication
Troubleshooting
- Ensure the API key credential is correctly configured and has the necessary permissions to access the reports endpoint.
- Verify that the Portfolio ID and Year parameters are correctly set and correspond to valid data in the Beex platform.
- Common error messages include HTTP status codes and messages indicating invalid or missing parameters; these can be resolved by checking the input parameters and API key validity.
Links
- Beex Contact Center API Documentation - Official API documentation for reference on endpoints and parameters.