Legacy Dev Forum Posts

 View Only

Sign Up

Back to discussions
Expand all | Collapse all

Unable to Schedule 2 personal callbacks with outbound campaign calls

  • 1.  Unable to Schedule 2 personal callbacks with outbound campaign calls

    Posted 06-05-2025 18:18

    Jeremy_MONZO | 2021-03-17 16:18:48 UTC | #1

    Hello,

    I would like create a personal callback for outbound campaign call like this only the agent who has scheduled the callback can receive the interaction. For have the conversation context (information from customer) and use skillid when I create call back I have used this API : /api/v2/conversations/${input.conversationId}/participants/${input.participantId}/callbacks

    I have suceed to create personals callbacks with this APi, but when the agent receive the personal callback if he wants create another callback, an error is displayed : {"message":"A callback is already in the process of being routed on this conversation","code":"callback.error.callback.already.being.routed","status":400,"messageWithParams":"A callback is already in the process of being routed on this conversation","messageParams":{},"contextId":"50f1bfab-8aae-43e4-bcaf-749d8e4f9e75","details":[],"errors":[]} [41c62f1a-8568-4b76-8da2-55af3afbc238

    So impossible to create callback from another callback with this API, weird behavior when we use outbound campaign calls, anyone has any hints for me?

    thanks jeremy

    Jeremy_MONZO | 2021-03-25 14:40:54 UTC | #2

    Hello,

    I'm thinking about other ways for create personnal callback, for example used diffrent queue instead skillid, for example : assign the callback to a specific queue and only one agent will be member of the queue. For this scenario, which API must be used for assign specifc queue AND keep the context of the outbound campaign calls (calling list id, values from callings list, script). Any hints is welcome

    thanks Jeremy

    system | 2021-04-25 14:40:58 UTC | #3

    This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.

    This post was migrated from the old Developer Forum.

    ref: 10311



Related Content