So here's the scenario:
- The call comes in, the user answers it, all is normal.
- The user starts a warm transfer. The third person answers.
- The user wants to put the caller on hold and speaks to that third person. My code does this by calling
someObject.postConversationsCallParticipantConsult
(I think the object code name isConversationAPI
or similar; long-named Genesys things get saved as variables so I've long since forgotten - it's "conversations" in my code, lol). This works fine. The caller is on hold, and the third person is talking to the user. If the user want to talk to the caller again, I can use that same function to switch back. This all works fine, butlet's say I don't do that here. - Now, let's say the caller is still on the line with the third person: how do I hang up the third person and talk to the user again? The docs would seem to suggest it's
deleteConversationsCallParticipantConsult
(and it is - if I'm talking to the caller and the third person is on hold). But the other way around........ idk, there seems to be either a different parameter I need to pass, or else maybe a different API endpoint completely..... as usual, the minimalist docs kinda leave me flummoxed and wishing I could go back to native apps.The docs (in API Explorer, which I've heard on here is the place I should be looking) just says "conversationId" and participantId", and these little one-worders are not much to go on. I've tried the phone number of the third person. I've tried the
destinationParticipantId
I get from the API endpoint that starts the warm transfer, but in all cases I get the same result "pending consult transfer does not exist" (404).
I'm guessing - and I mean this is the head-scratchinest API I've ever worked with so this is a complete shot in the dark - maybe the key word in that error is "pending". Maybe for some reason, Genesys "thinks" the transfer hasn't started yet. I got the caller on hold and the third person on the line, so from my puny human perspective it most certainly has... buuuuut... idk, just food for thought I suppose. This is one of those tools where you generally have to think waaay outside the box, just cuz u never know what kind of random it'll throw ya. At this point... Could it be
deleteConversationParticipantCode
maybe? Doesn't sound right (not sure what the "code" part means in this context, sounds more like an admin feature to me). But I'm kinda getting used to grasping at straws here. I'm sorry for constantly having to come on here and bug for help, but I so frequently run out of ideas on how to debug stuff. I've been a developer here for 10+ years but this API kinda makes me feel like a compete noob sometimes. I'm sure the answer is hiding in plain sight someplace... just a bit of a needle-in-a-haystack treasure hunt, an infinite loop of trial/error/DuckDuckGo.