What should the request for proposal include?
- Channels, volumes by hour and weekday, and seasonal peaks
- Languages, required level and how you will test it
- Systems and tools the team will use, and who pays for licences
- Current KPIs and the service levels you expect
- Data types handled, and any regulatory requirements
- Requested start date and expected growth
Which questions reveal how a provider really works?
- Do you employ the agents directly, full-time?
- Will our team work only on our account?
- What was your attrition over the past twelve months, and how do you calculate it?
- Which roles are included in the price: team leads, QA, workforce planning, IT?
- How quickly can you replace someone who leaves, and who pays for the training?
- Can we interview candidates and join their training?
What should you check on security?
- Named accounts with single sign-on and multi-factor authentication
- Least-privilege access to your systems, reviewed regularly
- Managed devices, and rules on phones, printing and removable media
- Logging and how quickly access is removed when someone leaves
- A data processing agreement and, for transfers from the EU or UK, standard contractual clauses
Continue reading
What should you ask references?
- How long have you worked with them, and how has the team changed?
- How did they handle the first serious problem?
- How accurate was the original quote compared with what you pay today?
- Would you choose them again, and for which work?
How do you design a pilot that tells you something?
Pick work that is representative but contained, such as one channel or one language. Agree three to five KPIs, a baseline and a target before go-live, review real conversations weekly, and decide in advance what result means scale up, extend the pilot or stop.