Routing & orchestration

Work Automation & task routing

Route claims, orders, cases and follow-ups like conversations – with Work Automation designed, integrated, tested and supported end to end by a certified QVCCS squad.

Architect flow to the right agent On the left a dark tile represents a Genesys Cloud Architect flow: an incoming call, a decision diamond and an automated task step marked by a gear. An arrow leads into a large bullseye of concentric rings, with small dots for agents in each skill ring, representing skills-based, bullseye and predictive routing. A second arrow leaves the bullseye and selects the highlighted royal blue tile in a column of three agents, showing the interaction reaching the right agent. ROUTING & ORCHESTRATION Architect flow Skills · bullseye Right agent

In summary

Genesys Cloud Work Automation brings your back-office tasks into the same routing engine that handles customer conversations. QVCCS designs and builds worktypes, workbins, statuses, rules and workitem flows so claims, orders, cases and follow-ups are routed by ACD to the right people, with due dates and priorities that reflect your commitments. Specialists from our own bench connect Work Automation to the systems where tasks originate, plan workforce management with you and give supervisors one view of every call, message and workitem.

Who works on this

  • Senior Business Consultant / Business Analyst
  • Solution Architect
  • Senior Developer
  • Software Developer
  • Systems Integration Tester
  • Senior Platform Practice Lead (Genesys Cloud CX)
  • Every task in one queue modelBack-office workitems sit alongside calls and messages, so capacity, priority and ownership are managed in a single place.
  • Due dates that drive actionPriorities, due dates and expiry rules are designed so the most urgent and valuable work always surfaces first.
  • Automated task progressionWorktype rules and workitem flows react to creation, status changes and due, expiry or lifespan dates, updating, routing or closing work automatically.
  • Planned, not guessedWorkforce management forecasts and schedules workitems as their own media type, so back-office effort is planned with the same rigour as voice.
DiagramHow a back-office task moves through Genesys Cloud CX
  1. 01Task createdAPI, integration or event
  2. 02Worktype appliedAttributes, statuses, workbin
  3. 03Workitem flowRules, updates, due dates
  4. 04ACD routingQueue, skills, priority
  5. 05Agent completesStatus updated, system synced
  6. 06Measure & planDashboards and WFM

Each workitem is created, typed, automated, routed and measured like any other interaction.

01

Why Genesys Cloud Work Automation matters

Genesys Cloud Work Automation addresses a problem most contact centres know well: the conversation is managed carefully, but the work it creates is not. A customer calls about a claim, and the follow-up disappears into a shared mailbox, a line-of-business queue or a spreadsheet. Nobody can see how much is waiting, which items are about to breach a promise, or who has capacity. Work Automation turns those tasks into workitems that are routed, prioritised and reported with the same discipline as calls and messages, so customers get the outcome they were promised, not just a polite conversation.

For operations leaders the benefit is visibility and control. Supervisors see priority, due date, status, worktype, queue and routing state for their agents' workitems, and can rebalance people between front-office and back-office work as demand shifts. For technical teams it removes a tangle of homegrown task tools and email rules. QVCCS starts in discovery by mapping the tasks that matter most to your customers – the claim, the refund, the address change, the complaint – with current-state journey maps that show how each one is created, owned, escalated and closed today, before any configuration begins.

02

How workitems, worktypes and workbins fit together

Genesys Work Automation (BO01) is a published Genesys Cloud use case, and it rests on a small set of building blocks. A worktype defines a category of task, its schema of custom attributes and the statuses it moves through, grouped into predefined categories with allowed transitions between them. Workbins hold workitems for teams or processes. Each workitem carries priority, a due date, an expiry and a lifespan. When routing is enabled, workitems go to queues like an ACD interaction using standard, bullseye or preferred agent routing, so skills, language and utilisation apply. Workitems are created through API-triggered events, typically from your case, order or claims systems.

Automation comes from two places. Worktype rules act on creation, on status transitions and on date events such as due date, expiry or lifespan. Workitem flows in Architect then run the logic: updating attributes, changing status, priority, due date or assignee, transferring to a user or queue, or disconnecting the item. Each worktype has exactly one associated workitem flow, and only one flow execution can run on a workitem at a time. Data actions pull context from line-of-business systems, and for multi-step processes Genesys Case Management groups steps into caseplans. Our Genesys Certified Developers design all of this with your process owners.

A customer promise is only kept when the task behind it is routed, owned and measured – that is what Work Automation should deliver.

QVCCS point of view

03

Design decisions that make or break task routing

The worktype model is the most important design decision, and it is hard to undo. A worktype's schema cannot be swapped after creation, and its workitem flow association is fixed, so the way you split worktypes shapes your automation for years. Too few worktypes and every flow becomes a maze of branches; too many and reporting fragments. QVCCS architects model your tasks, attributes and statuses in the high-level design first, walk them through with real examples from your operation, and agree naming, ownership and change control in our naming and configuration standards before anything is built.

Blending back-office and front-office work needs equal care. Utilisation settings decide whether an agent can hold a workitem while taking a call, and how much interruption is acceptable. Priority and due-date rules decide whether an ageing claim should overtake a new chat. Conditional group routing does not support workitems, so overflow is designed with bullseye rings, preferred agents or queue membership instead. We design these rules with your operations and workforce teams, so live-channel service levels are protected while back-office commitments are still met, and we design scripts and schema display panels so agents see the right record with each workitem.

Integration is where many task-routing projects stall. The system that holds the case or claim must create workitems reliably, avoid duplicates, and receive updates when the work is done. Our Interface Control Documents define what triggers a workitem, which identifiers it carries, how status is synchronised back, and what happens when a call fails. We use least-privilege OAuth clients, plan for API and flow execution limits, and design idempotent creation, so a retry never leaves two people working the same claim. Negative testing then proves each of those failure paths before go-live.

04

How QVCCS delivers Work Automation

Work Automation crosses process, integration, routing and planning, so we muster a team from our own bench and own the outcome end to end. A Senior Business Consultant / Business Analyst runs discovery with operations, process owners, planners and IT, and is often the first person to map how a back-office task really moves today, including the workarounds. A Solution Architect produces the high-level and low-level designs and the interface contracts, and owns the worktype model. Senior Developers and Software Developers build the worktypes, rules, flows, data actions and any middleware. A Systems Integration Tester proves status transitions and duplicate protection under realistic volumes, and the Senior Platform Practice Lead peer reviews design and build.

Moving back-office work onto ACD routing changes habits as well as systems. Teams used to choosing their own next task from a shared list now receive work in priority order, and supervisors used to a spreadsheet of backlog now see live workbins. We plan that change with your operations leads: which processes move first, how existing backlog is migrated or worked down in the old system, and how agents and supervisors are trained to trust due dates and priorities. Negative testing covers expired items, out-of-order status changes, duplicate events and failed updates back to source, and a cut-over runbook lets one process prove the model before the next joins.

05

Planning, measuring and improving blended work

Workforce management supports workitems as their own media type, so back-office demand can be forecast, capacity planned and scheduled alongside voice and digital channels, with real-time adherence counting workitem time as on-queue. Genesys sets conditions: workitems forecast only with Automatic Best Method, reassigned workitems are not supported for forecasting and scheduling, and specific licences apply. QVCCS helps planners design planning groups and queue structures that meet those conditions, and configures the workitem performance views and dashboards supervisors use, so ageing items, items near their due date and workload by team are visible at a glance.

After go-live, QVCCS assesses each Genesys Cloud CX release that affects Work Automation and reviews ageing, due-date performance and rework with your supervisors, because those measures show whether the routing rules reflect your real commitments. Support follows your Genesys Cloud CX support model, alongside your provider or under SLA with us. As confidence grows, we help you extend it to new processes, automate more steps within workitem flows, adopt Case Management for multi-step work, and introduce AI to classify, summarise or enrich tasks. Each change goes through the same design, test and governance discipline, so your blended operation keeps improving without losing control of the commitments you make to customers.

What you get from QVCCS

  • Task inventory mapped from trigger to closure with process owners
  • Worktype, schema, status and workbin model designed for the long term
  • Worktype rules and workitem flows built for creation, status and date events
  • Blended routing and utilisation rules protecting live-channel service levels
  • Interface contracts and integrations with case, claims and order systems
  • SIT and negative test evidence traced to requirements
  • WFM planning approach, supervisor views and support aligned to your model

Genesys documentation references

Checked against current official documentation, October 2026. Genesys releases weekly, so we re-validate every design against the live release notes.

  1. About work automationhelp.genesys.cloud
  2. Define a worktypehelp.genesys.cloud
  3. Work with workitem flowshelp.genesys.cloud
  4. Workforce management workitems supporthelp.genesys.cloud
  5. Genesys Work Automation (BO01) use caseall.docs.genesys.com
  6. Conditional group routing overviewhelp.genesys.cloud

Methods & templates

Work Automation & task routing: the templates behind each stage

Every QVCCS engagement follows our seven-stage delivery lifecycle, each stage closed by a quality gate. For Work Automation & task routing, the work concentrates in Discover, Define, Design, Prove and Transition, and these are the techniques and standard templates we lean on there, each one traceable from requirement to design, build, test and support.

  1. 01DiscoverDiscovery sign-off
  2. 02DefineRequirements baseline
  3. 03DesignDesign authority review
  4. 04BuildBuild complete
  5. 05ProveGo / no-go readiness
  6. 06TransitionOperational acceptance
  7. 07Run & evolveService reviews
  • 1 · Discover

    Current-state journey maps

    Trace each back-office task from trigger to closure today, exposing hidden queues, owners and commitments that workitems must honour.

  • 2 · Define

    Business Requirements Document (BRD)

    Captures each task type's volumes, due-date commitments, statuses and ownership as prioritised requirements traced through to testing.

  • 3 · Design

    Interface Control Document (ICD)

    Fixes how source systems create workitems, which identifiers they carry, how status syncs back and how retries avoid duplicates.

  • 3 · Design

    Low-Level Design / build book (LLD)

    Specifies every worktype, schema, status transition, rule, workbin, queue and workitem flow so the build is consistent and auditable.

  • 5 · Prove

    Negative and failure-path testing

    Proves expired items, out-of-order status changes, duplicate events and failed updates back to source are all handled safely.

  • 6 · Transition

    Cut-over plan and runbook

    Phases processes onto Work Automation one at a time, with rehearsed rollback, so each proves the model before the next joins.

See the full QVCCS delivery method

How we deliver

Work Automation & task routing: how an engagement runs

  1. 01DiscoverWorkshops with operations, process owners, planners and IT to inventory tasks, volumes, handling times and commitments.
  2. 02Define & designBRD, traceability matrix, HLD, LLD and interface contracts set out worktypes, statuses, rules, flows, routing and integrations.
  3. 03BuildCertified developers configure Work Automation, workitem flows, data actions and connectors to the LLD, with peer review.
  4. 04ProveSIT, volume and negative testing traced to requirements, then UAT scripts with real agents before a phased cut-over.
  5. 05Run & extendAligned support and release reviews, then new processes, Case Management and AI added under the same governance.

The specialists on this work, from our own bench

  • Senior Business Consultant / Business Analyst
  • Solution Architect
  • Senior Developer
  • Software Developer
  • Systems Integration Tester
  • Senior Platform Practice Lead (Genesys Cloud CX)

Every engagement follows our seven-stage method, with design authority, engineering standards and four-eyes peer review behind it. How we deliver →

Questions

Work Automation & task routing: common questions

What is Genesys Cloud Work Automation?

It is the Genesys Cloud capability for creating and routing non-conversational tasks, called workitems, through the same ACD as calls and messages. Worktypes define each task's attributes and statuses, workbins group them, and worktype rules with workitem flows automate progression.

Can Genesys Cloud route back-office work alongside calls?

Yes. Workitems can be routed by ACD to queues using standard, bullseye or preferred agent routing, so the same agents can handle calls, messages and tasks. We design utilisation, priority and due-date rules so live service levels are protected while back-office commitments are still met on time.

Does Genesys workforce management support workitems?

Yes. Workitems are a media type in workforce management, so demand can be forecast, capacity planned and scheduled with other channels. Forecasting uses Automatic Best Method only, reassigned workitems are not supported, and licence prerequisites apply. QVCCS helps planners design planning groups and queues that work within those rules.

How do workitems get created from our existing systems?

Usually through the Platform API, called from your case, claims or order system or from middleware. Our developers define the interface contract, design duplicate protection and status synchronisation back to the source, and build and test the integration, including negative tests, so tasks arrive reliably and complete cleanly.

Last reviewed

Talk to a specialist about this

We work by introduction. Clients, partners and people introduced to us can reach the right specialist for this topic directly.

Who to contact