Reaching one named person
Direct numbers and extensions that follow somebody away from a desk, without publishing a personal mobile.
Read about virtual systems
Salt Lake City, UT
Business VoIP in Salt Lake City, UT
One pair of codes covers the whole Wasatch Front, from Ogden down through Salt Lake City to Provo. That is roughly four fifths of the state's population on one footprint, so 801 tells a caller you are somewhere on a hundred mile strip and nothing more precise than that.
Disclosure: AldoMedia is a paid affiliate of Unitel Voice. If you sign up through a link on this page we may earn a commission, at no extra cost to you. We only recommend what we would set up for our own clients, and we say plainly below who should not buy this.
One corridor, one code, most of the state
801 was issued in 1947 and covered Utah entirely until 1997, when everything outside this corridor was split off as 435. In March 2009, 385 was laid over what remained, taking exactly the same ground rather than a piece of it.
So two things are true at once. Ten digit dialling has been normal here for fifteen years, which means nothing you have printed since is incomplete and there is no reprinting job waiting for you. And the footprint those two codes share is unusually crowded: the corridor holds most of the state's businesses, so a local number here is the least distinguishing thing about you.
A caller reading 801 learns that you are on the Wasatch Front. They do not learn whether you are forty minutes north of them or forty minutes south, and in a strip this long that distinction is exactly what they care about. The digits cannot help, and a business that leans on them is leaning on nothing.
The practical advice is short. Keep an 801 number if you hold one, because it has had longer to sound like the place and it is printed on things you have paid for. Porting it to a new provider is routine and is on business phone numbers. If you are offered 385, take it, because it has covered the same ground since 2009 and nobody local reads it as strange.
What a corridor does to the question a caller asks
In most cities the local question is whether you are in town. Here it is where on the strip you are, because a customer at one end and a supplier at the other are ninety minutes apart in traffic and both hold the same area code.
That makes coverage a thing you have to state rather than imply. A business that says which parts of the corridor it actually serves, and says it in the greeting and on the page somebody reads before dialling, removes the only real friction in the market. A business that leaves it to the area code has answered nothing, because the area code covers all of it.
The same applies to how far out you go. Once you leave the corridor the numbers turn into 435 and the distances get serious quickly, so if you do take work out there, say so plainly. If you do not, say that too. Both are better than letting a caller drive the assumption.
None of which makes the service local
There is no Utah phone product. The software is the same one a business in Delaware is sold, it runs a long way from here, and your address changes nothing except the three digits on the front of the number.
What VoIP is and what it asks of the connection into your building are on the main business VoIP guide. The rest of the state, which runs on one code covering nearly all of the map, is on business VoIP in Utah.
Who gains here, and a warning about outbound calling
The working economy along this corridor is unusually mixed for its size: software and data centres, financial services, logistics and distribution, healthcare, outdoor product manufacturing, and a large contact and support sector that serves customers well outside the state.
That last group should read the rest of this section carefully, because it is the one place on this site where a phone system can get a business into real trouble. If your people place outbound calls in volume, you are in territory governed by telemarketing rules, consent requirements and calling time restrictions, and those bite regardless of how the calls are carried. Some of them are federal, some are state by state, and the state ones follow the person you are calling rather than where you are sitting.
Nothing here is legal advice and we are not in a position to give it. What we can say is that this is a question for somebody qualified, asked before you scale outbound calling rather than after, and that any provider who waves it away while selling you an auto dialler has told you something useful about them. Ask plainly what the service does and does not do about consent records and calling windows, and get the answer in writing.
For everybody else the ordinary advice applies. A direct number per person for known callers, a short greeting rather than a long menu, and one published number that reaches whoever is genuinely free. Virtual phone system and auto attendant and extensions cover those. And if you are one person whose customers already reach you, this is a monthly cost against a problem you do not have.
The decisions behind the number
None of these are about Salt Lake City. They settle what a code shared by most of the state's businesses cannot.
Keeping the front short
Menus and greetings, and why a known caller should not work through five options to reach one person.
Read about auto attendantThe number itself
Keeping an 801 number you already hold, and what porting one between providers involves.
Read about business numbersWhether to switch at all
The honest case for keeping a copper line, which still applies to some buildings and connections.
Read VoIP vs landline
Common questions
Salt Lake City VoIP questions
Is an 801 number better than a 385 one?
Slightly, and not enough to wait for. The two have covered identical ground since 2009, so nobody along the corridor reads 385 as out of town. Port an 801 number if you already hold one, because it is printed on things you have paid for. If you are starting fresh, take what is offered and spend the attention elsewhere.
Our customers are spread from Ogden to Provo. Does a local number help?
Barely, because the same pair of codes covers all of that. A caller learns you are somewhere on a hundred mile strip, which is not the question they are asking. Naming the parts of the corridor you actually serve does more than the code ever will, and it costs nothing to say.
We are setting up an outbound calling team. What should we ask about?
Ask somebody qualified before you scale it, not afterwards. Outbound calling at volume runs into consent requirements and calling time restrictions that apply regardless of how the calls are carried, and the state level ones generally follow the person being called rather than where your office is. From a provider, ask in writing what the service does about consent records and calling windows. A provider who brushes the question aside while selling you a dialler has answered a different question.
Say where on the corridor you work
Tell us which parts of the Front your customers actually sit in and how calls reach a named person today. If a plain setup already covers it, that is what we will tell you.