👋 Hey there
You've written RFPs for all kinds of stuff - software, facilities, consulting. And now the business wants an RFP for hotline intake and routing.
On paper, it sounds pretty simple. The business wants a vendor to pick up hotline calls and get them to the right people, and that's pretty much it.
But once you start writing it, it gets specific fast. How quickly does someone need to answer? Should callers be asked questions first, or put straight through? What happens at 2am when the person on-call doesn't pick up?
On a crisis line, those answers really matter. They decide how long someone in crisis waits, who they end up talking to, and whether anyone picks up at all.
And most of them aren't yours to answer - they're the business's. So before you write anything, take these questions to your business owner. At Helpline, we set up call routing for hotline teams. These questions come straight from that work. (There's a template at the end too.)
There are two kinds of vendors
The first thing the business has to decide is pretty basic - who picks up the phone?
Someone else picks up first
This is your traditional answering service. Someone there picks up, follows the script you gave them, asks the caller a few questions, and transfers them to whoever's on your schedule.
So your people know what's going on before they even say hello.
The downside is the caller has no idea they've reached an answering service. They think they're talking to you, so they might start explaining everything to someone who doesn't work for you.
And depending on the vendor, operators might be in another country (which only matters if the business needs calls handled locally).
The call goes straight to your people
With a call routing service, your own staff pick up the calls. Callers just hear a quick menu - something like "press 1 for a workplace emergency, press 2 for facilities, press 3 for HR" - and the call rings whoever's on-call for that team. If they don't pick up, it goes to a backup.
Callers get to your people a lot faster this way. But your on-call staff only knows which button the caller pressed.
So which one's better?
Honestly, it depends on what the business cares about more - knowing more about a caller up front, or getting them to their own people as fast as possible.
What to ask your business owner
Ask this one first. The answer pretty much tells you which kind of vendor you need.
Some callers just want to get through
More questions means your people know what they're walking into. It also means the caller waits longer, and has to explain things to a stranger first.
A short menu gets them through fast, but your people won't know much when they pick up.
For urgent calls, the short menu usually makes more sense. (Nobody in crisis wants to spell out their email address.)
So it's worth asking:
- What do we need to know before a call reaches our people?
- Should urgent calls skip the questions?
- Would we be okay with AI answering calls, or does it have to be a person?
Sometimes nobody picks up
The on-call person is already on another call, or they're out dealing with another incident.
So the business needs to decide how hard to try to reach someone. For something urgent, that could mean ringing a few people at once, trying them again, and pulling in a manager if nobody's answered after a set time.
For something less urgent, the caller can leave their number and whoever's free next calls them back.
So it's worth asking:
- Who gets the call if the on-call person doesn't answer?
- When should a manager get involved?
- How many calls might come in at once?
- Should callers be able to ask for a callback?
The first voice they hear isn't yours
If the business goes with an answering service, those operators become the first voice of your hotline.
Which is a pretty big deal on a crisis line.
So it's worth asking:
- Should callers be told they've reached an answering service?
- Do operators need training in our crisis protocols?
- Is it ever okay for an operator to go off script?
- Do operators need to be in a certain country?
Something goes WRONG and nobody knows why
When a call gets missed, the first thing everyone asks is what happened.
Without good call logs, nobody can really say - it turns into your organization's word against the vendor's.
Good logs show who the call rang and when, who picked up and who didn't, and even whether someone was out of reception. Not every vendor tracks that much, so put it in the RFP.
So it's worth asking:
- If a call is missed, what do we need to be able to find out?
- Do we need access to the call logs ourselves?
- Do all calls need to be recorded?
- How should correct routing be covered in the contract?
Want all of this in one place?
We put every question from this post into a template you can send to your business owner. They fill in the answers, and you've got most of what you need for the RFP.
Open the cheat sheet in Google Docs
Before it goes out
A few more things the business should sort out before vendors start sending proposals:
- How many calls come in each month. Vendors will ask, and it shapes what they propose.
- Where each type of call should go. If that playbook isn't done yet, vendors will still need it at some point.
- Whether people should be able to reach the line by email, text, or chat. And if so, whether those should alert the on-call person like a call would.
- Whether the business wants to keep an eye on burnout, like seeing who's taking the most calls.
One last thing. Before you send it, show it to whoever's actually on the hotline. They'll catch stuff you'd never think of.
Want to talk any of it through? Book a free consultation with Helpline. Bring your draft, and we'll go over it together.
How to turn business owner answers into an RFP
- Pick the vendor model: Use the business owner's answers on intake depth vs speed to choose answering service vs direct routing.
- Send the questionnaire: Open the cheat sheet in Google Docs and collect answers in one place.
- Document escalation: Write primary, backup, and manager rules before vendors propose architecture.
- Require call logs: List the fields you must see after any missed or misrouted call.
- Review with hotline staff: Have whoever covers the line read the draft RFP before it goes out.
Frequently asked questions
Who should answer these questions before we write a hotline RFP?
The program or operations owner who runs the hotline should answer these questions, with input from on-call staff and supervisors. Procurement can facilitate the interview, but routing, intake, and escalation policy belong to the business.
What is the difference between a hotline answering service and call routing in an RFP?
An answering service uses third-party operators to answer first, collect intake, and transfer calls. Call routing sends callers to your own staff using menus or rules tied to schedules and backups. The RFP should name which model you want, because pricing, training, and SLA language differ.
Should our hotline RFP require call logs we can access ourselves?
Yes, if you need to investigate missed or misrouted calls without waiting on the vendor. Require fields such as ring targets, timestamps, answer outcome, and fallback steps, plus export or dashboard access for your authorized staff.
How much intake should we require before a caller reaches an advocate?
Match intake depth to urgency. Crisis calls usually need the shortest path to a trained responder. Lower-urgency lines can collect more context up front. The business owner should define required questions, optional questions, and any menu options in the RFP.
What call volume should we include in a hotline routing RFP?
Include average and peak monthly call volume, typical concurrent calls, and growth expectations if you have them. Vendors use volume to size redundancy, operator staffing (for answering services), and failover design.
Can we reuse these answers in grant applications?
Yes. Operational answers about staffing, hours, escalation, and outcomes often feed grant narratives. Align RFP requirements with grant language using your organization's grant boilerplate so funders see the same service model vendors will implement.



