1 Risposta
- Più recenti
- Maggior numero di voti
- Maggior numero di commenti
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.
con risposta un anno fa
Contenuto pertinente
- AWS UFFICIALEAggiornata 2 anni fa
- AWS UFFICIALEAggiornata 2 anni fa
- AWS UFFICIALEAggiornata 3 anni fa
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.