How to set up a help desk phone line: numbers, call flow, and what it costs

Start with the call, not the software

Most guides to a help desk phone line open with a vendor list. That’s backwards. A phone line is a promise to a person who is already having a bad day: someone picks up, and what I say ends up on a ticket. If you design for that sentence first, the tooling choices get much easier.

This guide walks through the setup in the order you’ll actually make decisions: the number, the call flow, who answers, how the call becomes a ticket, and what it costs at a realistic call volume. It’s about the plumbing underneath. If you’d rather read about bolting voice onto a help desk you already run, see how to add phone support to your help desk; this one is for building the line itself.

Step 1: choose the number

You have three real choices.

• A new local number. Cheapest and fastest. Good if your clients are in one region and you don’t mind a new number on your website.
• A toll-free number. Looks established and works across regions, but costs more per month and per minute (figures below).
• Port your existing number. If clients already have your number saved, port it. Porting means moving it from your current carrier to the new provider; it takes days to weeks depending on the carrier, so start it first and keep the old service active until it completes.

Don’t forward a mobile phone as a shortcut. You lose call records, and no ticket gets created when the owner is in a meeting.

Step 2: pick a telephony source

There are two ways to get a line, and they price very differently.

Carrier-level (build it from parts)

A carrier API such as Twilio or Telnyx sells you numbers and minutes, and you wire up the call logic yourself.

As of 2026-10-05, Twilio’s US voice pricing lists local numbers at $1.15/month and toll-free at $2.15/month. Inbound minutes are $0.0085 on local and $0.0220 on toll-free.

Telnyx lists voice at $0.002/minute plus SIP trunking fees, with numbers at $1.00/month, as of the same date. Their page doesn’t give a single all-in inbound figure, so price your actual setup before assuming the headline rate.

The catch: this is a toolkit, not a phone system. Ring groups, menus, voicemail-to-ticket, and the softphone your techs answer on are all yours to build or buy separately.

Packaged business phone (pay per user)

A business phone app gives you numbers, a softphone, and basic routing in one subscription. Quo is a current example. As of 2026-10-05 its plans run Starter $15, Business $23, and Scale $35 per user per month on annual billing ($19, $33, and $47 month to month). Each plan includes one new or ported number per user, and porting is free. Its pricing page shows phone menus (IVR) appearing at the Business tier and above, so if you want a menu, budget for at least that plan.

The catch here is different: the phone system and your help desk are two products. Calls are logged in one place and tickets live in another.

Step 3: design the call flow on paper

Before you configure anything, draw the flow. For a small IT team it usually fits on an index card:

1. Greeting. Business name, and one sentence on what to do. Keep it under ten seconds.
2. Menu (optional). Two options at most: “existing issue” and “new issue.” Skip the menu entirely if you have fewer than four techs; callers hate menus more than they hate a short ring.
3. Ring order. Who rings first, for how long (20-30 seconds is typical), and who rings next.
4. Fallback. What happens when nobody answers: voicemail, a second group, or an automated answer.
5. After hours. A different path from business hours. Decide now whether urgent callers get an on-call number or a promise of a callback.

Write the callback promise as a number you can keep, such as “within two business hours.” Whatever you say becomes your de facto SLA.

Step 4: decide who answers

Three models, in rising order of coverage:

• A ring group of techs. Simple, but it interrupts whoever is mid-fix, and nobody covers lunch.
• A rotating front-line person. Better for focus; needs a rule for coverage.
• An automated first answer. An AI or scripted agent picks up, collects the problem, and either resolves a status question or hands off with context. For after-hours coverage specifically, see how a help desk answers calls automatically.

The honest tradeoff: an automated answer helps most with status questions (“where’s my ticket?”) and after-hours capture. It doesn’t replace a human for an angry client with a server down.

Step 5: make every call a ticket

This is the step that separates a help desk phone line from a phone. For every call, you want:

• Caller identified. Match the incoming number to a contact or organization, so the tech sees who’s calling before they say hello.
• A ticket created or updated. Not a call-log entry in a separate tool. If the caller has an open ticket, the call should attach to it.
• A recording or summary attached where the next tech will see it.
• Missed calls and voicemails turned into tickets, not left in a mailbox someone checks on Fridays.

If your phone system and help desk are separate products, test this end to end before go-live: call from a known number, call from an unknown one, hang up before anyone answers, and leave a voicemail. Four calls will show you most of the gaps. Our guide to logging calls and email in one help desk covers the same test from the email side.

Step 6: price it at a real volume

Take a small team that gets 300 inbound minutes a month and has four techs.

These are arithmetic on the published rates above, not quotes. The carrier row looks tiny because it leaves out the part you’d have to build. The packaged row looks larger because it includes it. Neither includes your help desk subscription, which is the point: with a separate phone system you’re paying for both.

Step 7: test, then publish the number

Before you put the number on your website:

• Call during hours and after hours.
• Let it ring through to the fallback.
• Check the recorded greeting from a mobile phone, not just the speaker on your desk.
• Confirm a ticket exists for each test call.
• Have a tech answer from the softphone on their normal laptop and headset, since audio quality problems usually live there.

Then publish it in your email signature, your website footer, and your ticket auto-reply, so the phone line is discoverable in the same places people already look for support.

Where ITSM fits

If you’d rather not assemble the line from a carrier, a phone app, and a help desk, ITSM puts the ticketing and the voice in one product. Calls create and update tickets directly, the browser softphone is a $10/seat/month add-on, and the AI phone agent is an add-on that answers from live ticket data. The free tier is 2 seats at $0 with instant signup at /register; Basic is $29/month with 3 seats and $5/month per extra seat. Check the current add-on terms on the pricing page before you plan around them.

ITSM is a small product with a free tier, and no public customers yet; if you already have a phone system you like, wiring it to your help desk is a perfectly good route.