1回答
- 新しい順
- 投票が多い順
- コメントが多い順
0
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.
回答済み 1年前
関連するコンテンツ
- AWS公式更新しました 3年前
That makes completely no sense. Why would AWS create an API and mention an API attribute, release it and completely ignore it. This then forces me to use pinpoint to use as a dialer instead of creating my own dialer.
What other solution do I have to use HVCO via API and not use pinpoint.