Assembled Workforce Management

Currently, when a person is added in Assembled their details do not sync to Workday. This means that people are created twice: once in Assembled, once in Workday. Managerial relationships are also not captured in Assembled. Request: Allow workforce managers to create people in Assembled, associate them with their managers in Assembled, and sync automatically to Workday so the same information is reflected in both places.

It would be really helpful to be able to have the creation of new employees in Workday or updates to employee data in Workday create/update people in Assembled! This would save us and our BPOs a ton of time. Thanks!

Freshdesk is used across many teams as a secondary contact. including an integration of this will help build better and more accurate requirements.

We would like to see scheduled activities for the future dates to be reflected in Looker. We spoke with out data team and according to them, we can't export Assembled future data to be reflected in Looker. Is that something that Assembled is blocking? Is there a way to lets say send scheduled phone/chat/case hours for next week or month if its already plotted in Assembled?

we would like the option to start a backfill forTalkdesk without opening a ticket

Currently, Assembled's HiBob integration syncs all approved time off requests regardless of policy type. Some customers use HiBob policy types (e.g. "Remote working" to track employees working abroad) that are purely HR/compliance-driven and not relevant for WFM. There is no way to prevent these from syncing into Assembled, and HiBob's own permissions system can't help either as it only controls access at the category level (all time off or none). Allow customers to configure an allow-list or block-list of HiBob policy types would help keep agent schedules clean and focused on what's operationally relevant, preventing HR-only policy types (such as compliance or remote working trackers) from creating noise in Assembled. It would also reduce support overhead from customers trying to understand unexpected event types appearing in their schedules.

Currently subdomains like company1.example.com and company2.example.com need to be tracked as separate websites on the Chrome extension. Adding just " example.com " only tracks subdomains like example.com/company1 . Adding website tracking for both types of subdomains would help ensure better consistency.

I should be able to configure an idle timer for the Chrome extension that automatically pauses or stops activity tracking after a defined period of mouse and keyboard inactivity, so that agent activity data more accurately reflects actual working time.

Chrome extension capability for Gladly.