VoIP RFP in North Carolina: A Guide for Public Agencies

By Nicky Smith, Founder, Carolina Digital Phone · October 13, 2026 · 21 min read

Published October 13, 2026. Last updated October 13, 2026.

Sooner or later, somebody in a staff meeting says it: "Don't we have to put the phones out for bid?" The room goes quiet, everyone looks at the finance officer, and a project that should take three months takes nine.

The short answer for a VoIP RFP in North Carolina is that state law usually does not require one for a hosted phone service. Your own purchasing policy might. Federal money in the project might. And even when nothing requires it, a well-written RFP is often the smartest way to buy.

I should say where I sit. Local Business VoIP is the small-business site of Carolina Digital Phone, Inc. We have been answering North Carolina RFPs from towns, counties, and school systems since 2000, so this guide comes from the vendor's side of the table. I am not your attorney, and nothing here is legal advice. What I can tell you is what the statutes say, where to confirm it, and what separates an RFP that draws five good proposals from one that draws two you cannot compare.

Does North Carolina law require an RFP for a hosted phone system?

In most cases, no. The state's bidding rules for local governments are written around buying things and building things. They do not reach contracts for services. The UNC School of Government, which teaches purchasing law to local officials across this state, puts it in one line: "Services contracts are not subject to the competitive bidding laws."

So the first question is not "how much does it cost?" It is "what are we buying?" A hosted phone system is mostly a service. The provider owns and runs the platform, and you pay by the user each month. Desk phones are equipment. Many projects contain both.

Two cautions. First, the way a deal is priced can change how it is classified. Phones that are included in the monthly service look different from phones you buy outright for six figures. If your project has a large hardware line, ask your attorney how to handle it before you ask vendors for prices. Second, state law is the floor, not the ceiling. Plenty of North Carolina boards have adopted purchasing policies that require proposals or quotes for services above a set dollar amount. Read yours first.

Our main site has a companion article on the legal side, North Carolina RFP requirements for hosted telephone and VoIP services. This guide picks up where that one stops: how to write and run the RFP.

What changes when there is federal money in the project?

Nearly everything about the "services are exempt" answer. When a project is paid for with federal grant or loan funds, the federal Uniform Guidance applies, and it requires competition for services as well as goods. The School of Government calls the result the "most restrictive rule." You follow whichever is strictest: federal rules, state law, or your own policy.

Its July 2025 summary chart lays out the tiers for service contracts. Below the federal micro-purchase level, shown as $10,000, no quotes are needed. From there up to $250,000, you need price quotes from an adequate number of sources and a written record. At $250,000 and above, you need sealed bids or competitive proposals. Federal thresholds are adjusted from time to time, so confirm the current figures with your grantor agency.

School systems ask about E-Rate at this point. Voice service has not been eligible for E-Rate support since funding year 2019, as the FCC's eligible services notice for that year explains, so E-Rate bidding rules are usually not what drives a phone RFP. Network equipment in the same project can be a different story. Ask your E-Rate consultant before you combine them.

What is the IT RFP option, and why do agencies like it?

It is a section of state law, G.S. 143-129.8, that lets a city, county, or school system buy information technology through a request for proposals. It can be used in place of sealed bidding. State law counts telecommunications as information technology, so phone systems qualify. Four features make it a good fit for a phone project.

• You choose on value, not only price. The contract goes to the vendor that submits the "best overall proposal as determined by the awarding authority." A sealed bid has to go to the lowest responsible bidder.
• You set the scoring in advance. The factors you will use have to be identified in the RFP itself. That protects you and tells vendors what matters.
• You may negotiate. The statute lets you negotiate with a proposer to reach a contract that best meets your needs, as long as the changes would not have altered who could compete or who would have won.
• Proposals stay sealed until award. They are not open to public inspection until a contract is awarded.

Notice is given the same way as for a formal bid. In practice that means advertising the RFP and allowing enough time for a real response. This is the route I see most often for mixed projects, where the service, the phones, the installation, and the training are all in one contract and the agency wants one company answerable for all of it.

What are the paths besides an RFP?

There are at least five, and for a small office one of them is usually the better choice. The School of Government's chart of bidding exceptions lists the statutory ones.

Those exceptions are written for purchases that would otherwise have to be bid. For a pure service contract you may not need an exception at all, which is why the classification question comes first. Whichever path you take, write down why. A one-page memo to the file is the cheapest insurance in public purchasing.

Why do so many towns and school boards issue an RFP anyway?

Because it is often the right tool even when it is not required. I see four reasons again and again.

• Local policy says so. The board adopted a rule years ago, and the rule applies.
• The system is a safety system. A phone system that carries 911 calls, classroom phones, and paging deserves a closer look than copier paper.
• The public is watching. A documented, scored competition is easy to defend at a board meeting and in the newspaper.
• Federal funds are involved. Competition is then required.

It is also fair to say when an RFP is more than the job needs. A twelve-phone town hall does not need a forty-page solicitation. Three written quotes against a clear one-page list of requirements will get that town a better answer in a quarter of the time. Match the process to the size of the decision.

What does a bad phone RFP look like?

It looks like the last one, with the dates changed. Let me describe a situation I have seen more than once.

The difference was not length or legal language. The first RFP described a machine. The second described what the town needed to happen.

What should a North Carolina VoIP RFP ask for?

Ask for outcomes in nine areas, and tell vendors enough about yourself that they can price the work accurately. An RFP with no phone counts is an invitation to guess.

A few of those deserve more than a row.

911. Federal rules for multi-line telephone systems require direct dialing of 911, notification to someone on site, and a dispatchable location with the call. Put those in the RFP as pass or fail, and ask each vendor to show how it will be done in your buildings. Our guides on how to assign dispatchable E911 locations and on school VoIP with paging and E911 show the level of detail to expect.

The price form. This is the single most useful page in any phone RFP. If every vendor fills in the same form, you can compare them. If each sends its own quote, you will spend two weeks building a spreadsheet and still not be sure. Ask for the five-year total. Ask what is not included. Our post on transparent VoIP pricing lists the lines to put on the form.

Who does what. Ask each vendor to state which jobs are theirs and which are yours. Our guide to VoIP as a service has a table you can borrow.

References. Ask for three North Carolina public agencies of about your size, with a name and a phone number, and then call them. Ask one question above all: when something broke, who answered?

How should you score the proposals?

With weights you publish in the RFP and a committee that scores separately before it meets. Under the IT RFP statute the evaluation factors have to appear in the RFP, so decide them before you release it, not after you read the proposals.

Here is a starting point for a public agency. Change the weights to fit what matters most to you.

Three habits make scoring fair and fast. Score cost by formula from the price form, so it is arithmetic and not opinion. Give every finalist the same demonstration script, built from your own call flow, so you see your town hall on the screen and not a canned sales tour. And keep the individual score sheets. They are your record.

What mistakes lead to weak proposals, or none at all?

From the vendor's side of the table, the same eight show up year after year.

• Reusing an old equipment RFP. Questions about trunk cards tell cloud providers you want a box.
• Naming a brand. Specify what the phone must do, not who makes it.
• Leaving out the counts. No buildings, no users, no numbers, no accurate price.
• Scoring on price alone. You will get the cheapest answer to a question you did not mean to ask.
• No price form. Every quote arrives in a different shape.
• No question period. Vendors guess, and guesses get padded.
• Too little time. A ten-day window favors whoever already knew it was coming.
• Forgetting the analog lines. The fax, the alarm, and the elevator phone surface the week of the switch. Our guide to premise PBX alternatives explains how to plan for them.

How long does a phone RFP take?

Plan on three to five months from the first draft to the first call on the new system. The RFP itself is rarely the slow part. Board calendars and number porting are.

If you have a hard deadline, such as a copper line shutoff or a lease ending, work backward from it and start earlier than feels necessary. Our number porting timeline guide explains the last row.

How do you run a VoIP RFP, step by step?

Follow six steps. The first two decide whether you need an RFP at all, so do not skip ahead to writing one.

1. Check the funding source and read your own purchasing policy

   Find out whether any federal grant or loan money is paying for the project, and read your board-adopted purchasing policy for rules on service contracts.

   Federal funds bring federal competition rules. Local policy can require quotes or proposals even where state law does not. These two answers shape everything after.

2. Decide what you are buying

   List the service and the equipment separately, with rough dollar amounts, and ask your attorney how the contract should be classified.

   A hosted service billed monthly is generally a service contract. Phones and other hardware bought outright are purchases, and $30,000 and $90,000 are the state thresholds to watch.

3. Choose the lightest purchasing path that fits

   Pick among written quotes under local policy, a state contract, piggybacking, a group purchasing program, a sole source finding, or an RFP under G.S. 143-129.8.

   Small service-only projects seldom need a full RFP. Larger, multi-site, or safety-critical systems usually benefit from one. Write a short memo recording which path you chose and why.

4. Inventory what you have and set your requirements

   Count buildings, users, phones, and numbers, list every device connected to the current system, and write down how calls should be answered.

   Separate must-haves, such as 911 location for every phone, from preferences. Include paging, fax, alarm, and elevator lines. This inventory becomes the first section of the RFP.

5. Write the RFP with scoring factors and one price form

   Describe the outcomes you need in plain language, publish the evaluation factors and their weights, and require every vendor to use the same price form.

   State 911 requirements as pass or fail. Ask for the total cost over the full term. Set a question deadline and have your attorney review the terms before release.

6. Run a fair process and document the award

   Advertise as required, answer all questions to all vendors at once, score proposals individually, hold scripted demonstrations, check references, and keep the records.

   Under the IT RFP statute you may negotiate with a proposer within the scope of the RFP. Keep the score sheets and the reasons for the award. Then plan the number port and training with the chosen vendor.

Who should be on your vendor list?

At least one provider that works in North Carolina every day. National companies answer public RFPs well on paper. What the paper cannot show is who walks your buildings before the switch, who knows your county's 911 center, and who picks up when the police department's phones act up on a Saturday.

Carolina Digital Phone has provided hosted phone service from Greensboro since 2000, and local government and schools are two of our main markets. We have a team dedicated to them with its own direct line, (336) 543-0000. Our platform runs in data centers in downtown Greensboro, Research Triangle Park, and Dallas. Our engineers are in North Carolina, and they plan the system, move the numbers, train the staff, and support it afterward.

You can read more in hosted VoIP for local government, our municipal upgrade case study, the government phone compliance guide, and our pages for government and K-12 schools. On the main site, see government phone systems and education phone systems. School systems can also visit HostedVoIPforSchools.com or request a quote at HostedVoIPPhoneSystem.com. To learn who we are, read why organizations choose Carolina Digital Phone, our history, and what it means to be a trusted communications partner.

For a quick callback from a local onboarding engineer, HostedBusinessTelephone.com takes about a minute. And if you are still deciding whether to replace the system at all, start with hosted VoIP in North Carolina.

North Carolina gives public agencies more room than most people in that staff meeting assume. Use it. Decide what you are buying, pick the lightest process that fits, and if that process is an RFP, write one that describes what your callers and your staff need to happen. The proposals will be better, the scoring will be faster, and the board will have an easy vote.