One number, one line: how PhoneShield fits a small team
PhoneShield team
The people who build and run PhoneShield
Written and kept current by the team behind PhoneShield, a sister company of Byte Federal, whose staff spent years meeting scam victims at cryptocurrency ATMs with the scammer still on the line.
In this article
Introduction
PhoneShield is built around one phone line: the number people already call, forwarded to PhoneShield, with vetted calls ringing one phone. That is a good fit for a shop, a practice, or a founder with a helper, and with a little care for a business of two to ten people who take turns answering the same line. This guide is honest about what one line means for a team, and shows the patterns that make it work.
The short version: the phone rings one person, but everything else about a call can be shared.
No seats, no roles
There are no team members, departments or routing rules in PhoneShield today. One account, one PhoneShield number, one private line. Everything below works within that, and the last section says plainly what is missing.
One number per account
Each account gets one PhoneShield number. You forward the phone people call to it, and set one private line where vetted calls land. Both are set on the Shield settings page, which also shows the carrier forwarding codes and offers a loop-back test to confirm the forward is live. The private line is verified by a spoken code: PhoneShield calls it, reads a code aloud, and you type it into the dashboard.
Whose phone rings?
The private line is the phone of whoever answers for the business that day. Changing it takes a minute: enter the new number and verify it with the spoken-code call. Some teams point it at a shared desk phone; others move it between mobiles each shift.
Several lines?
If two people each need their own screened line, that is two accounts, each with its own number, private line, assistant and $29.99 a month. Deliveries from both can go to the same Slack channel or inbox.
Favorites: owners and key clients
Favorites ring straight through. They do not meet the front desk, they are not classified, and no mode sends them to a message. When a favorite calls, the private line rings with a short whisper naming them, so whoever holds the phone knows before answering that it is the landlord, the accountant or the client who pays half the invoices. A sensible starting list for a small business:
- The owners and partners. If the private line is on a staff member’s phone that day, the owner calling in should not have to explain themselves to Nora.
- Everyone on the team. Add each colleague’s mobile so a call from the field reaches the duty phone directly, with the whisper saying who it is.
- Key clients and suppliers. The handful of numbers where a missed call costs real money. Keep this short; the point of favorites is that they always interrupt.
- The alarm company and the bank. Rare calls that are urgent when they come.
Contacts are the softer tier
A contact still meets the front desk, but the tag bypasses the shared block list for your account. Favorites for people who must ring, contacts for people who must not be blocked. See Favorites.
Receptionist in work hours, Open for the owner-run shop
Every call that is not a favorite and not blocked meets the front desk voice, says who they are and why, and gets a verdict from the intent classifier. What happens next depends on the mode. There are three, and a team usually lives in two of them.
Receptionist: the team pattern
The front desk hands the call to Nora. She talks to the caller, answers what she can, and saves a structured message. The private line stays quiet. This is the right mode when three people are serving customers at the counter and nobody can take a call properly. Switch it on at opening, off at closing.
Open: the owner-run shop
A caller with a real reason rings the private line, with a whisper saying who it is and why, and voicemail detection so an unanswered call is not lost. Nora can also connect a caller through to you in this mode. It suits an owner who wants to hear the phone and decide in the moment.
The third mode, Do not disturb, sends most callers to a transcribed message and is for the hours when nobody answers at all. Modes are switched by hand on the dashboard; no schedule flips them, so agree on who does it and when. A common arrangement is Receptionist during opening hours, Open for the owner’s paperwork hour afterwards, and Do not disturb overnight.
Whichever mode, known scams never get through
Known scam numbers are refused before the call is answered, at no cost, from your own blocked list, the shared block list, and repeated FTC Do Not Call complaints. See How the shared block list works.
Nora as the front desk
In Receptionist mode your assistant, Nora by default, answers calls that are not from favorites and not blocked. She speaks first, already knows why the caller said they were calling, and does the things a front desk does for a small team:
- Takes a structured message with the caller’s name, callback number and what they need. The same three fields every time, so a colleague who did not take the call can act on it.
- Answers from her knowledge: opening hours, address, what you do and do not do, whatever you put in her AI profile.
- Connects the caller to you in Open mode, ringing the private line with a whisper that says who it is, when it is worth an interruption.
- Flags spam and ends the call politely after the goodbye. A confident scam verdict from Nora puts the number on the shared block list for everyone.
Only Nora's talk time is metered, at $0.12 a minute beyond the 150 included each month, so a team in Receptionist mode all day should expect assistant minutes to be the only thing that moves its bill. Screening and blocked calls cost nothing.
Give her the team’s facts
Put names, hours and the two or three questions callers always ask into the knowledge and conditional responses of her AI profile. If callers ask for people by name, tell her who does what, so the message says “wants Sam about the invoice” rather than “wants to talk to someone”. See Customizing your assistant.
Working the Messages feed together
The Messages feed shows what is waiting on you. Anyone signed in to the account can open a note, tap “Call back”, and mark it done. The done state is shared, so the second person to look sees it is handled. The “Waiting on you” filter hides everything already done, which turns the feed into a to-do list for the whole team rather than a log.
Because there are no seats, everyone uses the same login. Nothing records which colleague marked a note done, and a note cannot be assigned to a person. The channel thread carries that bookkeeping today.
A simple routine for two to ten people
- Deliveries go to a shared Slack channel or inbox.
- Whoever picks a note up says so in the thread, calls back, then marks it done in the feed.
- The duty person checks “Waiting on you” at midday and before closing; it should be empty at the end of the day.
- Anything still open at closing is the next morning’s first job for whoever holds the private line.
A weekly review in Analytics
Every call ends in one of five outcomes, each with a reason: Blocked, Shielded, Rang you, Message, or Assistant. Analytics shows those outcomes per day, and ten minutes a week with that page is enough to keep the arrangement honest.
- Blocked and Shielded are the calls you did not have to deal with. If Shielded is climbing, read a few reasons: a legitimate caller type may be getting declined, and a line in Nora’s profile would fix it.
- Rang you versus Message tells you whether the mode is right. A shop in Open mode with a wall of unanswered rings should try Receptionist. A queue of messages that all say “please call back today” argues for the owner in Open mode for part of the day.
- Assistant minutes are the bill. If the same question appears in the transcripts every day, add the answer to Nora’s knowledge and the calls get shorter.
- Messages still open on Friday are a process problem, not a phone problem.
What is not here yet, and the workarounds
So you are not surprised later, PhoneShield today does not have:
- Multiple numbers or private lines on one account
- Team seats, roles, or per-person notifications
- Transfers to a named person, or department and skills-based routing
- Calendar integrations, or a schedule that switches modes for you
- SMS, WhatsApp or a mobile app; PhoneShield is voice calls and a web dashboard
The workarounds are the patterns above. For “transfer me to Sam”, tell Nora who Sam is and what he handles, so the message names him and lands where Sam sees it. For seats, the shared login plus the channel thread. For routing, move the private line to the duty phone each shift and put every colleague on favorites. For a second line, a second account with deliveries pointed at the same channel.
Tell us what you need
Small teams are exactly who we build for, and PhoneShield is in early access. If one line is not enough, write to us and describe your setup: how many people, how many lines, and what a transfer should do.
Related Articles
Ready to try PhoneShield?
Start screening your calls today and take back control of your phone.