A computer for call center work needs to run the agent's complete working environment: dialler or browser phone, CRM, knowledge base, security tools and the peripherals used at the desk. Selecting it from a CPU label or the softphone's minimum RAM figure leaves important compatibility questions unanswered.
Start with a seat brief, then test a representative agent workflow before approving a fleet. The useful question is whether the exact computer, software and desk setup can complete the required work throughout a shift and hand over cleanly to the next agent.
Identify the agent application and browser combination
Record the contact-centre platform, agent application or embedded client, version, browser, operating system and required features. Browser calling, a separately installed softphone and a physical desk phone create different endpoint requirements. List the CRM and knowledge-base applications alongside the calling tool, including approved extensions and authentication steps.
Use the documentation for that deployment. For example, Twilio's Flex UI requirements list a 2 GHz processor, 2 GB RAM and 1024 × 768 screen resolution as minima. They specify an up-to-date Chrome or Edge browser, with Edge support limited to the Flex UI Agent Desktop. The browser width must also be at least 1024 pixels. These are Flex UI conditions, not a specification for a complete CRM-loaded agent seat.
Genesys Cloud's requirements make a similar distinction: they recommend exceeding the minimum specifications for WebRTC voice, video or demanding third-party applications, and testing the desired agent configuration. Browser support also depends on the feature. Its Safari limitations include the Genesys Cloud WebRTC phone. A browser that opens the login page is therefore not sufficient compatibility evidence.
Size the whole agent workflow
Write down the applications that stay open during a normal interaction. Include the CRM tabs, customer record, knowledge search, messaging, document viewer and any approved recording or assistance software. Record simultaneous work, not just a list of installed applications. A supervisor monitoring dashboards may need a different test from an agent handling one voice interaction.
Ask IT to propose candidates using that application set and the software suppliers' current requirements. During the pilot, observe memory use, CPU demand and response delays while the agent moves between tasks. Keep operating-system updates, security policy and background tools consistent. Do not remove required protection to make a weak candidate appear adequate.
Separate local delays from network or platform issues. A slow CRM response does not automatically identify a computer fault; poor call audio does not automatically identify a CPU problem. Record what the agent was doing, the exact symptom and relevant endpoint and network observations so the responsible IT or platform owner can investigate.
Check the headset, ports and working display
Record the exact headset model, USB connector, adapter or dock, microphone path and any required call-control functions. Confirm the relevant platform and headset documentation before describing mute or answer buttons as compatible. Leave enough usable ports for the keyboard, mouse and required peripherals with the proposed desk cabling.
Twilio's initial audio device check guidance identifies missing browser microphone permission, disconnected or faulty USB headsets and headset driver issues as possible causes of audio-device problems. Test the actual headset through the approved browser and agent application. Do not rely only on an operating-system sound test.
Display checks should use the real working layout. Confirm that the agent can see call controls and the required CRM fields at the approved resolution and scaling. If two monitors are needed, verify the computer's outputs, adapters and simultaneous display arrangement. A monitor's diagonal size alone does not show whether the application layout is usable.
Complete an agent-seat and peripheral matrix
Create a row set for each distinct role or deployment. A supervisor, a browser-voice agent and a desk-phone agent should not inherit the same acceptance result without checking their differences. Copy this worksheet and replace the prompts with exact versions and decisions.
| Seat input | Record for this role | Approval or test evidence |
|---|---|---|
| Role and concurrency | Agent or supervisor; channels and simultaneous tasks | Operations owner confirms the representative workflow |
| Calling application | Vendor, client type, version, features and phone path | Platform owner checks the current requirements |
| Browser and OS | Exact browser build, OS edition and approved extensions | IT records support and update policy |
| Other applications | CRM, knowledge base, messaging and background tools | Pilot runs the required applications together |
| Candidate computer | Exact model, CPU, RAM, storage and network connection | IT records the offered configuration and pilot observations |
| Headset and USB path | Model, connector, adapter or dock and required controls | Test microphone, playback, mute and permitted call controls |
| Displays and desk | Monitor count, outputs, resolution, scaling and cabling | Agent completes the interaction without hidden controls |
| Shift handover | Sign-out, next-agent sign-in, audio selection and desk reset | Operations and IT approve the handover result |
| Acceptance | Task targets, test duration, failures and decision owners | Signed result tied to this exact seat configuration |
Use the desktop quotation guide when comparing what each desk quote includes. Keep that commercial comparison separate from the application and peripheral evidence recorded here.
Run a representative shift and handover pilot
Agree the pilot tasks and acceptance criteria before running calls. Use an authorised test environment or approved test calls and suitable test records. Have the platform owner provide accounts and calling permissions. The equipment test does not replace permission to use customer data or production telephony.
Start with sign-in and the audio-device check. Complete an inbound or outbound test interaction, open the CRM record, search the knowledge base, enter notes and finish the required wrap-up. Test hold, transfer or call controls only when they form part of the approved workflow. Record whether the agent hears clearly, is heard clearly and can complete the agreed tasks.
Repeat the workflow with the expected background applications and over a representative period. Include the shift-change steps: sign out, change to the next authorised user, reconnect the headset where that is normal practice and confirm audio selection again. Add screen locking and the approved idle or resume behaviour to the test. Ask IT to review OS suitability through the Windows 11 fleet-readiness guide where a Windows migration is involved.
Record every exception with an owner and retest after a relevant change. Release only the role and configuration that passed. A changed browser policy, headset adapter or application version may require another compatibility check before it is treated as equivalent.
A hypothetical seat comparison
Suppose a team plans 40 agent seats. Each pilot agent must keep a browser phone, CRM and knowledge base open, with one USB headset and two monitors. These are illustrative requirements, not a tested fleet specification, stock statement or C Prompt customer example.
Test the proposed candidates against those tasks and the team's agreed limits for delays and audio problems. If a candidate loses microphone access after shift handover, record and resolve that failure before approval. A higher RAM figure on its own would not prove that the permission, device-selection or adapter issue had been fixed.
Frequently asked questions
Is the calling platform's minimum RAM enough for the whole seat?
It may cover only the documented application. Include the CRM, browser tabs, security tools and other concurrent tasks, then pilot the full environment. Choose the capacity from the actual software requirements and observed workload rather than a universal call-centre RAM rule.
Will any USB headset work with a browser phone?
Do not assume that it will. Check the exact headset, connector, driver requirements and platform support. Test microphone permission, audio selection, playback and the call-control functions you actually require through the intended agent application.
Does every agent need two monitors?
Use the job's working layout to decide. Test whether the agent can see the calling controls and required application fields at the approved scaling. If two displays are specified, verify the outputs, adapters and desk arrangement as part of that seat's acceptance.
Does renting computers include dialler or CRM integration?
Confirm the equipment scope separately. Software accounts, licences, telephony configuration and CRM integration need explicit responsibilities and approval from their owners. An equipment enquiry or a successful computer pilot does not establish that those services are included.