Unable to send calls to campaign using CLI

Question

Hi
I am trying to invoke outbound campaigns using the StartOutboundVoiceContact CLI/API without pinpoint.

aws connect start-outbound-voice-contact --destination-phone-number +1xxx --contact-flow-id xxx  --instance-id xx --source-phone-number +1xxx --campaign-id xxxx  --traffic-type CAMPAIGN --answer-machine-detection-config EnableAnswerMachineDetection=true,AwaitAnswerMachinePrompt=true

But the calls do not follow the campaign logic. I have set it check if 100% agents are available in queue before dialing out.  Both for predictive and progressive mode.

As soon as I hit the CLI calls are dialing out to the destination number even if there are 0 agents logged into the queue.

It looks like the CLI / API does not follow the campaign but simply put the calls into the contact as normal calls even hough I have specified the traffic type as CAMPAIGN.

Any idea what is wrong ?

Answer

when you are using the CLI to make the outbound call, even with CAMPAIGN ID specified, it is ignored. So the call is made right away with AMD enabled. The only way that pacing taken into account is when you use this with AWAS Pinpoint. AWS Pinpoint is checking the strategy in your campaign before request Connect to make the call.

The logic in this is to use this API to make self-service outbound with AMD without any agent dependencies.

Unable to send calls to campaign using CLI

Relevant content