Independent study lab
This is an independent, free, learning-only student project. It respects every company and vendor. Trademarks belong to their owners. It is not affiliated with or endorsed by Amazon Web Services, Cisco, Genesys, Salesforce, Twilio, or any other company. If you have a concern, the page will be removed or corrected promptly through the contact form. Nothing here is sold. There are no ads. The author is happy to volunteer for any organization.
Third-party WFM configuration and faults — Learn it in 5 minutes
About five minutes of reading
The integration is the agent event stream plus a historical extract. If either is late, adherence is fiction.
Aspect's deployment uses one agent-event stream, optionally Firehose into S3, and scheduled report exports. Eleveo describes the same pair: agent events for the live listener, CTRs and recordings for history. Both need a status map.
Faults: one shard and two consumers, a status renamed in Connect and not in the WFM tool, a missed logout, and a schedule that was never published so adherence is blank.
- Give each consumer its own iterator.
- Alarm on iterator age.
- Map statuses in a reviewed table.
- Do not send production events into a vendor lab account.
Number on this page: Stream 1. Agent events, sized for every consumer
Sources and go deeper
- Connect Customer agent event streams - Amazon Connect Customer AWS docs. last checked 2026-10
- Forecasting & agent scheduling in Connect Customer - Amazon Connect Customer AWS docs. last checked 2026-10
- Workforce management - Wikipedia Wikipedia. last checked 2026-10