Professional services
Requirements analysis & capture
Marry what you know about your business with what we know about Genesys Cloud CX – and leave discovery with requirements that are complete, prioritised and traceable to design and test.
Genesys Cloud requirements analysis is where every successful contact centre programme begins. QVCCS brings architects, business analysts, telecoms engineers and platform specialists together to discover how your business really works today, explore the art of the possible on Genesys Cloud CX, and capture what you need in a Business Requirements Document, a Functional & Non-Functional Requirements Specification and a Requirements Traceability Matrix. Whether you are migrating, refreshing your platform, building a first contact centre or preparing an RFP, you leave with requirements that are complete, prioritised and testable.
- Enterprise Solution Architect
- Senior Business Consultant / Business Analyst
- Business Analyst
- IT Systems, Telecoms & SIP Engineer
- Senior Platform Practice Lead (Genesys Cloud CX)
- Solution Architect
- Every stakeholder heardFrom the leadership team to agents on the floor, we interview every group that shapes, runs or depends on your contact centre.
- Current state made visibleCall flows, IVR, queues, staffing, telephony, sites and systems are reviewed so nothing in today's operation is lost in translation.
- Requirements you can buildA BRD, functional and non-functional specification and traceability matrix written to be clear, specific, complete and testable.
- Ready for RFP or deliveryThe same discipline produces a vendor-ready RFP pack or the signed-off baseline for a QVCCS design and build.
- A typical Genesys Cloud implementation timelineThe stages of a Genesys Cloud CX implementation, from discovery to run: who is involved, the artefacts, the quality gates and what sets the timeline.Read the guide
- Questions for your Genesys Cloud business case, by stakeholderThe questions your board, finance, IT, security, operations and HR will ask about a move to Genesys Cloud CX, and the evidence that answers each one well.Read the guide
- Contact centre RFP requirements: capture, writing, scoring and a checklistHow to capture, write and score contact centre RFP requirements, with a downloadable checklist covering volumes, integrations, security, AI and migration.Read the guide
- 01Stakeholder mapEvery group, every voice
- 02DiscoveryWorkshops, audits, readiness
- 03Art of possibleLive Genesys Cloud CX demos
- 04DefineBRD, FRS and NFRs, MoSCoW
- 05TraceabilityRTM linked to design and test
- 06BaselineSigned off, change controlled
Discover closes with discovery sign-off and Define with the requirements baseline, so design starts from requirements everyone has agreed.
01
Why Genesys Cloud requirements analysis matters
You understand your business and how it operates. We understand contemporary contact centre technology and Genesys Cloud CX in depth. Marrying those two bodies of knowledge is the key to downstream success, and Genesys Cloud requirements analysis is where that marriage happens. Organisations come to us at different moments: migrating from an on-premises automatic call distributor to the cloud, refreshing from another cloud platform to Genesys Cloud CX, building and operating a contact centre for the first time, or preparing an RFP or RFI that must give vendors everything they need to respond accurately. In every case the requirements capture defines the deliverables and scope in detail, so the programme that follows is built on facts rather than assumptions.
Getting requirements wrong is expensive because the cost surfaces late – as change requests during build, defects in user acceptance testing or workarounds after go-live. Cloud platforms add a further trap. Genesys Cloud CX is a service that Genesys releases new features to every week, so requirements that simply replicate a legacy platform screen by screen can lock in old limitations and miss better native capabilities. Our analysts separate what the business needs from how the current system happens to deliver it, and record for each area whether the goal is like-for-like parity or deliberate transformation. That single distinction prevents a great deal of rework later.
02
Who we speak to and what we review
A multichannel or omnichannel contact centre touches almost every part of an organisation, so we speak to almost every part of it. Typically that includes the leadership team; contact centre management, supervisors and team leaders; agents and customer service representatives; workforce management and human resources; IT, including application developers and DevOps engineers; telecommunications, networking and information security; compliance, regulatory and legal; the online and eCommerce, marketing, social media and brand teams; loyalty and retention; outbound, collections or debt management; and reporting and business intelligence. Each group sees the contact centre differently, and each holds requirements the others would never think to mention.
Alongside the interviews we review the evidence: current documentation, call flows, IVR structure, queues, skills, staffing and schedules, contact reasons, volumes and handle times. We assess sites, offices, connectivity and telephony against Genesys guidance on customer network readiness, which covers matters such as SIP trunk provider capabilities, quality-of-service tagging and firewall allowlisting. We consider regulatory, commercial, online, social and digital strategy. Where you already run Genesys Cloud CX, we audit the existing organisation's configuration – exported with CX as Code where appropriate – so requirements start from what is really there rather than what people remember.
You know your business; we know Genesys Cloud CX. Requirements analysis is where the two meet – and where downstream success is decided.
03
Discovery workshops and the art of the possible
Consultant-led discovery is delivered remotely, like all QVCCS work unless we mutually agree otherwise: structured video workshops, screen-shared walkthroughs of your current configuration and reports, and recorded play-backs. We run discovery workshops with groups of key stakeholders and demonstrate the art of the possible on Genesys Cloud CX as part of discovery, so your teams have a rounded, accurate and current baseline from which to express their requirements. It is much easier to ask for predictive routing, an agentic virtual agent or automated wrap-up summaries when you have seen them working. We map current-state customer and employee journeys and ask the important question of every process: does it have to be this way, or is it this way because it always has been?
The workshops use proven facilitation techniques. Stakeholder mapping makes sure the right people are in the right sessions. Journey, process and data mapping expose hand-offs, duplicated effort and the systems of record each step depends on. Requirements are written as user stories with Given/When/Then acceptance criteria wherever behaviour matters, and every requirement is prioritised with MoSCoW – must, should, could, won't this time – so scope decisions are explicit and owned by the business. After each round we play back what we heard, in writing, so stakeholders can correct us before anything is baselined.
04
The outputs: BRD, specifications and traceability
The Business Requirements Document states the goals, objectives and needs of your business, surfaced through discrete stakeholder groups so each defines what it expects. It records scope, assumptions, constraints, dependencies and the measures by which success will be judged, such as service levels, first-contact resolution or containment. The BRD is written in business language and signed off by business owners. It answers the question of why the programme exists and what it must achieve, and it becomes the reference against which every later design decision and change request is tested.
The Functional & Non-Functional Requirements Specification turns intent into precise statements. Functional requirements define what the solution must do: channels, routing, self-service, integrations, recording, quality, workforce management and reporting. Non-functional requirements describe its qualities: availability, performance, security, data residency, resilience and supportability. On Genesys Cloud CX these must reflect real platform facts – for example the AWS core regions available for your organisation, the shared responsibility for uptime set out in the Genesys service level agreement, and a weekly release cadence. Each requirement carries a unique identifier, owner, MoSCoW priority and acceptance criteria.
The Requirements Traceability Matrix links every requirement forward to the high-level design, the low-level design or build book, the build items and the systems integration and user acceptance test cases that prove it, so nothing is lost and nothing is built without a reason. The High-Level Design then describes the solution at component level, and the Low-Level Designs go down to hostnames, IP addresses, protocols and transport for each building block. For RFP and tender work we produce a largely complete RFP document for your stakeholders to top and tail, with architectural drawings in Visio or other formats and Word, PowerPoint or Excel annexes.
05
Who captures your requirements, and how
We take a holistic, solution-orientated approach. For each engagement we muster a multidisciplinary team from our own bench, shaped to your programme. An Enterprise Solution Architect with more than 40 years' experience sets direction and owns the architectural view. A Senior Business Consultant / Business Analyst leads the workshops and the BRD, supported by Business Analysts with operational and workforce management depth. An IT Systems, Telecoms & SIP Engineer covers networking, security, carriers and sites. Our Senior Platform Practice Lead (Genesys Cloud CX) reviews every specification against current platform capability. Even when you meet only two of us, the whole practice stands behind the work.
Quality is built into the method rather than inspected at the end. Discovery closes with a discovery sign-off, and definition closes with a formal requirements baseline; after that, change control and a RAID log keep scope visible and decisions recorded. Every document is peer reviewed within the practice before you see it. Because the people who capture your requirements stay accountable through design, build, testing and go-live, the knowledge gathered in discovery is never handed over and lost. Our leadership has worked in contact centre technology since 1984, and that experience shows most clearly in the questions we ask before anything is built.
What you get from QVCCS
- Stakeholder map and discovery report covering people, process and technology
- Current-state journey maps and site, network and telephony readiness assessment
- Business Requirements Document signed off by your business owners
- Functional & Non-Functional Requirements Specification with MoSCoW priorities
- Requirements Traceability Matrix linked to design and test
- Vendor-ready RFP or RFI pack with drawings and annexes, if required
Genesys documentation references
- Customer network readiness (Genesys Cloud)help.genesys.cloud
- Genesys Cloud system requirementshelp.genesys.cloud
- AWS regions for Genesys Cloudhelp.genesys.cloud
- Genesys Cloud Service Level Agreementhelp.genesys.cloud
- Genesys Cloud feature release schedulehelp.genesys.cloud
- Genesys Cloud Terraform provider (CX as Code) – Terraform Registryregistry.terraform.io
Methods & templates
Requirements analysis & capture: the methods and templates we use
Every QVCCS engagement follows our seven-stage delivery lifecycle, each stage closed by a quality gate. For Requirements analysis & capture, the work concentrates in Discover and Define, and these are the techniques and standard templates we lean on there, each one traceable from requirement to design, build, test and support.
- 01DiscoverDiscovery sign-off
- 02DefineRequirements baseline
- 03DesignDesign authority review
- 04BuildBuild complete
- 05ProveGo / no-go readiness
- 06TransitionOperational acceptance
- 07Run & evolveService reviews
Stakeholder map
Identifies every group that shapes, runs or depends on the contact centre, so no requirement is missed through an absent voice.
Discovery workshops and current-state journey maps
Expose how customers and employees are served today, demonstrate the art of the possible, and challenge processes kept only by habit.
Readiness assessment
Surveys sites, networks, carriers and telephony against Genesys network readiness guidance before design depends on them.
Business Requirements Document (BRD)
Records goals, scope, constraints and success measures in business language, signed off by the owners who will judge the outcome.
MoSCoW prioritisation and Given/When/Then acceptance criteria
Make scope decisions explicit and every requirement testable, so user acceptance testing proves exactly what the business asked for.
Requirements Traceability Matrix (RTM)
Links each requirement to design sections, build items and SIT and UAT test cases, closing the requirements baseline gate.
How we deliver
Requirements analysis & capture: how an engagement runs
- 01MobiliseWe agree objectives and shape the team from our bench, then build the stakeholder map and workshop plan.
- 02DiscoverInterviews, readiness reviews, data analysis and configuration audits establish an accurate picture of today's operation.
- 03ExploreRemote discovery workshops demonstrate the art of the possible on Genesys Cloud CX and challenge inherited processes.
- 04DefineBRD, functional and non-functional specifications written, prioritised with MoSCoW and given testable acceptance criteria.
- 05BaselinePeer-reviewed, signed-off requirements and traceability matrix placed under change control, ready for design.
- Enterprise Solution Architect
- Senior Business Consultant / Business Analyst
- Business Analyst
- IT Systems, Telecoms & SIP Engineer
- Senior Platform Practice Lead (Genesys Cloud CX)
- Solution Architect
Every engagement follows our seven-stage method, with design authority, engineering standards and four-eyes peer review behind it. How we deliver →
Questions
Requirements analysis & capture: common questions
What does a contact centre requirements analysis include?
It covers stakeholder interviews, discovery workshops, a review of current call flows, IVR, queues, staffing, systems, sites and telephony, and analysis of contact reasons and volumes. The outputs are typically a Business Requirements Document, a Functional & Non-Functional Requirements Specification and a Requirements Traceability Matrix, followed by high-level and low-level designs when you proceed to delivery.
Can you help us write an RFP for a cloud contact centre?
Yes. We produce a largely complete RFP or RFI document for your stakeholders to top and tail, with requirements written so vendors can cost them accurately, plus architectural drawings and annexes. Because we work only on Genesys Cloud CX, we are open about that focus and write requirements in terms of business outcomes and qualities rather than one vendor's feature names.
Do requirements workshops need to happen on site?
No. All QVCCS work is performed remotely unless we mutually agree otherwise. Stakeholder interviews, discovery workshops, journey mapping and live demonstrations of Genesys Cloud CX run over video, with screen-shared reviews of your call flows, reports and configuration. If a site visit would add value, for example to observe a complex operation, we agree it with you during mobilisation.
Should we replicate our current system on Genesys Cloud CX?
Only where parity is what the business needs. We record for each area whether the goal is like-for-like or transformation, because copying a legacy design can lock in old limitations and miss native capabilities. Discovery demonstrations of the art of the possible help your teams make that choice with full information.
Last reviewed