Virtual PBX for Small Businesses, What You Actually Buy

TL;DR: A virtual PBX for small businesses is a call-routing product. Every headline feature on it, auto attendant, extensions, ring groups, business hours, voicemail, is a decision about a call that somebody else already placed. That is fine if your phone volume arrives. It does nothing for the half of the day a growing company spends reaching out. The second thing you buy, and the one no feature grid prints, is a vendor who now holds your call detail. Under 47 CFR 64.2003(o) the term “telecommunications carrier” across the whole CPNI subpart includes an entity that provides interconnected VoIP service as defined in 47 CFR 9.3, so most virtual PBX providers are carriers for privacy purposes. 47 CFR 64.2003(d) defines call detail information as, for outbound calls, the number called and the time, location, or duration of any call, and for inbound calls, the number from which the call was placed. That is your call log, by name. The rules that follow give a small business four things to check that beat any feature comparison: the annual CPNI compliance certificate an officer must sign and file with the FCC Enforcement Bureau on or before March 1 in EB Docket No. 06-36 under 64.2009(e), which has to include any actions taken against data brokers and a summary of customer complaints about unauthorized CPNI release; the rule in 64.2010(b) that a carrier may hand you call detail over the phone only after a password that was not prompted by readily available biographical information or account information; the breach clock in 64.2011(b), which routes notice to the Secret Service and the FBI within seven business days and bars the carrier from telling you for seven full business days after that; and the right in 47 USC 222(c)(2) to have your CPNI disclosed, on affirmative written request, to any person you designate, which is how you leave. Ask those four questions. Then count your inbound and outbound calls separately and buy for whichever half is actually growing the business.

Start with what breaks, not with a definition. A five-person company buys a virtual PBX because calls are getting missed. Somebody rings the main number, it lands on one person’s cell, that person is on another call, and the caller hangs up. Nobody finds out. There is no record that the call happened, so there is nothing to fix on Monday. A virtual PBX solves exactly that problem, and it solves it well.

Then the same company tries to grow. Now a rep has a list of 200 people to reach, and the auto attendant has nothing to say about it. The greeting does not dial. The extension does not advance to the next number. The ring group does not log an outcome. So the company that bought a virtual PBX for small businesses to stop missing calls finds out it bought a product for one direction of traffic, and it is working the other direction by hand.

That is the whole decision, and it is worth saying plainly before the feature lists start. A virtual PBX is an answering system. If the growth plan is outbound, the answering system is not the purchase.

What a virtual PBX for small businesses actually is

PBX stands for private branch exchange. The name describes a switchboard that sat in a building and decided which internal desk an outside call should ring. Virtual means the switchboard now runs on a provider’s servers instead of in your closet, and the desks are apps, cell phones and handsets wherever people happen to be. The abstraction did not change when it moved. It is still a branch exchange, and its unit is still the extension.

Hold a virtual PBX feature list next to that sentence and the pattern is hard to miss. Auto attendant: route the arriving call by menu choice. Ring group: route the arriving call to several people. Business hours: route the arriving call differently at 7pm. Voicemail and transcription: store the arriving call when nobody took it. Call park, hold music, extension dialing, find me follow me. Every one of them is a routing decision made after the phone was already ringing.

So judge the product by the behavior it changes, not by the count of features. Ask what a person on your team no longer does by hand, where the outcome gets written down, what happens after nobody answers, and whether a second person can pick the conversation up tomorrow. A virtual PBX has good answers for the first three on inbound calls. It usually has no answer at all for outbound.

One term to separate from the pile while you shop. Virtual PBX, hosted PBX and cloud PBX are used interchangeably by most vendors and mostly describe the same arrangement. The deployment-model question, whether the exchange lives in your building or in a provider’s data center, is a different decision with its own cost, porting and emergency-calling consequences, and it is worked through in cloud PBX vs on-premise PBX. This page assumes you already decided to let a provider host it, and asks what you just handed them.

Your virtual PBX provider is a carrier under the CPNI rules

Here is the part the feature grids leave out. When the exchange moved into a provider’s cloud, your call records moved with it. Who called, who they called, when, for how long, from where. That data has a legal name, customer proprietary network information, and a body of FCC rules attached to it.

The first question is whether those rules reach a virtual PBX vendor at all, because the rules are written about telecommunications carriers and a software company selling a monthly subscription does not look like a phone company. The answer is in the definitions. 47 CFR 64.2003(o) states that for the purposes of that subpart, the terms “telecommunications carrier” or “carrier” shall include an entity that provides interconnected VoIP service, as that term is defined in section 9.3 of the rules. That sentence pulls the whole CPNI subpart over the top of interconnected VoIP providers. It is not an analogy. It is the definition the rules run on.

47 CFR 9.3 then tells you which vendors qualify, in four parts. An interconnected VoIP service enables real-time, two-way voice communications; requires a broadband connection from the user’s location; requires internet protocol-compatible customer premises equipment; and permits users generally to receive calls that originate on the public switched telephone network and to terminate calls to it. Read that against the product you are about to buy. A virtual PBX that gives your business a real phone number, answers calls the public dials, and lets your team call out, meets all four. Vendors that only connect users to each other inside their own app do not, and the rules below do not bind them the same way. Check that before you rely on any of this.

What is actually covered is specific, and worth quoting because it is more concrete than most privacy language. Under 47 CFR 64.2003(d), call detail information is any information that pertains to the transmission of specific telephone calls, including, for outbound calls, the number called, and the time, location, or duration of any call, and for inbound calls, the number from which the call was placed, and the time, location, or duration of any call. That is a description of your call log. Your prospect list, in effect, written down by the hour.

Behind the FCC rules sits the statute. 47 USC 222(a) places a duty on every telecommunications carrier to protect the confidentiality of proprietary information of, and relating to, other carriers, equipment manufacturers, and customers. Section 222(h)(1) defines CPNI as information relating to the quantity, technical configuration, type, destination, location, and amount of use of a telecommunications service, made available to the carrier solely by virtue of the carrier-customer relationship, plus the information in the bills. Destination and amount of use. For a sales team, that is the work product.

What a virtual PBX vendor can do with your call records without asking

The honest answer is: more than most buyers assume, and less than the scary version. Learn the boundary rather than the headline.

Under 47 CFR 64.2005(a), a carrier may use, disclose, or permit access to CPNI to provide or market service offerings among the categories of service to which the customer already subscribes from that same carrier, without customer approval. So your provider can mine your call patterns to sell you more of what you already buy from them. Under 64.2005(b), it may not use CPNI to market a category you do not already subscribe to from that carrier unless it has your approval. 64.2007(b) sets how that approval works: marketing communications-related services to you can run on opt-out or opt-in approval, and anything outside the permitted uses requires opt-in approval. Under 64.2007(a)(3), the carrier has to keep records of approval, oral, written or electronic, for at least one year.

One prohibition is worth knowing by name because it is the one that protects a buyer who is shopping. 47 CFR 64.2005(b)(2) states that a carrier may not use, disclose or permit access to CPNI to identify or track customers that call competing service providers. The example in the rule is a local exchange carrier using local service CPNI to track customers who call local competitors. If you are calling other vendors from the phone system you are thinking of leaving, that rule is the one that says your provider is not allowed to notice.

Third parties are the real exposure, and the rules make them countable. 47 CFR 64.2009(c) requires every carrier to maintain a record of all instances where CPNI was disclosed or provided to third parties, or where third parties were allowed access to it, including a description of each campaign, the specific CPNI used, and what products and services were offered. Carriers must keep that record for a minimum of one year. That is a document your vendor is obligated to have. Ask for the summary.

Four questions to ask a virtual PBX provider before you sign

Feature comparisons between virtual PBX providers converge fast, because the features converged years ago. These four do not converge, they are answerable from public rules, and a vendor’s reaction to them tells you more than a demo.

First, ask for the annual CPNI certificate. 47 CFR 64.2009(e) requires an officer of the carrier, as an agent of the carrier, to sign and file a compliance certificate with the Commission every year, stating personal knowledge that the company has established operating procedures adequate to ensure compliance with the subpart. The filing must carry a statement explaining how those procedures work, an explanation of any actions taken against data brokers, and a summary of all customer complaints received in the past year concerning the unauthorized release of CPNI. It goes to the Enforcement Bureau on or before March 1 in EB Docket No. 06-36, covering the previous calendar year. A vendor that cannot tell you whether it files one, or who signed it, has told you something.

Second, test the phone authentication yourself. This is a ten-minute test and it is the most useful thing in this article. Call your prospective provider’s support line and ask them to read you call detail from the account. Under 47 CFR 64.2010(b), a carrier may disclose call detail information over the telephone, on customer-initiated contact, only if the customer first provides a password that was not prompted by the carrier asking for readily available biographical information or account information. If there is no password, the carrier may only send the call detail to the address of record or call the customer back at the telephone number of record. 64.2003(m) defines readily available biographical information to include a social security number or its last four digits, mother’s maiden name, home address, or date of birth; 64.2003(a) defines account information to include an account number or the telephone number on the account. So if a support agent reads your call history back after you supply a name and an account number, the control you were promised is not there. Run that test on the vendor you already use too.

Third, understand the breach clock before there is a breach. 47 CFR 64.2011(b) requires the carrier, as soon as practicable and no later than seven business days after reasonable determination of a breach, to notify the United States Secret Service and the FBI through a central reporting facility. The same paragraph then bars the carrier from notifying customers or disclosing the breach publicly until seven full business days have passed after that law enforcement notification, with two exceptions: an extraordinarily urgent need to prevent immediate and irreparable harm, after consultation with the investigating agency, and a direction from the investigating agency to delay notice for an initial period of up to 30 days where disclosure would impede a criminal investigation or national security. Add it up. Your call records can be in someone else’s hands for a couple of weeks before you are told, lawfully. That is not a reason to avoid a virtual PBX. It is a reason to know which data you are putting there, and to keep your own copy of the pipeline somewhere you control.

Fourth, confirm the exit before you need it. 47 USC 222(c)(2) states that a carrier shall disclose customer proprietary network information, upon affirmative written request by the customer, to any person designated by the customer. That is a statutory right to have your own call detail handed to whoever you name, including the provider you are migrating to. Vendors rarely advertise it. Put the request process in writing during the sales cycle, while the vendor still wants the signature, not during a migration.

Two notes on currency, because these rules move. Subpart U of Part 64 carries a source note of 82 FR 44419, September 21, 2017. The current eCFR text of 64.2010 carries cross-references to an amendment published at 88 FR 85814 on December 8, 2023 and a correction at 88 FR 88261 on December 21, 2023, and 64.2011 carries a cross-reference to an amendment published at 89 FR 10002 on February 12, 2024. Read the section itself before you quote it in a contract negotiation.

The virtual PBX feature list is an inbound feature list

Back to the floor. Split your phone volume into two piles and the buying decision mostly answers itself.

The arriving pile is what a virtual PBX is built for, and the requirements are real. A call comes to the main number. Somebody has to get it. If the first person is busy, somebody else has to get it. If nobody is there, the call needs a defined destination rather than a dead end. Kixie’s ring groups handle this part the way a virtual PBX does: incoming calls route to multiple agents simultaneously, linearly down a list, or in linear round robin so calls distribute evenly, and a No Answer Action setting decides where a call goes when nobody in the group is available, which can be anywhere except back to the same ring group. Agents can take those calls on a mobile phone, a desk phone or a landline, and a single agent can have more than one device ring at once. That is the answering machinery, and a small business genuinely needs it.

The departing pile is where the category stops helping. Think about what the work actually is. A rep has a list. The rep picks a number, dials it, waits through the ring, gets voicemail, decides whether to leave one, hangs up, writes a note, looks at the list, and picks the next number. Most of that is not selling. It is clerical work between conversations, and after a few rejections it turns into the thing reps do instead of calling: reorganizing the list, rereading notes, finding a reason the next call should happen later.

An auto attendant has no opinion about any of this. Neither does an extension. So if outbound is how the company grows, the questions change: who decides the next number, what happens automatically after no answer, where does the outcome get written, and what can a manager inspect on Friday. That is the gap Kixie’s PowerDialer is built for. It advances to the next number as soon as the rep finishes a call or drops a voicemail, and on the Multi-Line PowerDialer plan it dials up to four lines at once. Calls, texts, outcomes and recordings log into the CRM through Kixie’s CRM integration without anybody typing them in, which is what makes the activity inspectable later. Two things worth pricing separately, because as of October 29, 2026 Kixie lists both as premium add-ons rather than plan inclusions: AI Human Voice Detection, which sorts a live answer from a machine, and ConnectionBoost, which combines local presence, number monitoring and progressive caller ID to manage outbound number reputation and pickup rates. Price the add-ons with the seats. A dialer that burns its own numbers stops working within a month, and the tool that prevents that is usually the line item somebody cut.

Notice that the two piles need different things from the same phone system, and that a company with both is the normal case, not the exotic one. The clinic that books appointments also calls patients back. The contractor who answers bid requests also follows up on quotes. The question is never which pile exists. It is which one is growing.

How to run the virtual PBX decision for a small business

Do this in order, and do the counting before the demos.

Count the two piles for one normal week. Not a guess. Pull the call log from whatever you use now and split it: calls that arrived, calls your team placed. If the arriving pile is 80% of the volume and the growth plan is referrals, buy the answering system and stop reading feature lists. If the departing pile is growing, the answering system is a component of the purchase, not the purchase.

Write down the three failure moments. What happens when the main number rings and the first person is busy. What happens at 7pm. What happens when a rep dials a list of 200 and nobody picks up on the first pass. Make each vendor answer those three on a screen share instead of on a slide.

Run the authentication test from question two above. It takes ten minutes and it is the only part of a sales cycle where you observe the vendor’s actual operating procedure rather than its description of one.

Ask where the outcome gets written. If call outcomes live only in the phone vendor’s dashboard, then every report you will ever run about your pipeline depends on a system you may leave. If they land in your CRM automatically, the record survives the vendor.

Price the whole thing, including the parts that are not seats. Numbers, usage above any included minutes, porting, hardware if you want handsets, and whatever the vendor calls an add-on. Get it in one written quote covering a full year rather than a monthly per-seat number.

Confirm the exit in writing before you sign. The number port and the CPNI request under 222(c)(2) are both easier to agree on while the vendor still wants the deal.

Then pilot it with the two or three people who make the most calls, for two weeks, and watch one number: missed calls on the arriving side, conversations per rep per day on the departing side. If neither moved, the system did not change the work, whatever the feature list said.

Virtual PBX for small businesses FAQs

Can a small business keep its existing phone number on a virtual PBX

Yes, number portability is a legal right rather than a vendor favor, and the timelines and the data a carrier may require are set by rule rather than by your new provider’s onboarding team. The porting mechanics, including how long a simple port takes and what a carrier can ask you for, are covered in cloud PBX vs on-premise PBX. Start the port after the new system works, never before.

Does a virtual PBX work with desk phones

Usually yes, and the useful version of the question is which device rings for which person. In Kixie’s ring group settings, you choose the device an incoming call rings for each agent, and you can select more than one device for a single agent so a call reaches both a cell phone and the dialer. Confirm the specific handset models with any provider before buying hardware, because compatibility lists change.

What happens to calls during an internet outage

The arriving call still reaches the provider, because it never needed your office network to get there. What breaks is the last hop to an endpoint sitting behind the dead connection. So the answer depends entirely on the fallback rule you configured: a No Answer Action that forwards to a mobile number keeps the call alive, and a system that only rings desk apps does not. Set that rule on day one and test it by unplugging something.

Is a virtual PBX the same as a cloud PBX

In practice the two terms describe the same thing, a branch exchange that a provider hosts, and most vendors use them interchangeably along with hosted PBX. The distinction that actually carries consequences is the one between a provider-hosted exchange and equipment you operate yourself, which changes cost, control and emergency-calling duties. That comparison is in cloud PBX vs on-premise PBX.

Who can see a small business’s call records on a virtual PBX

Your provider can, and the FCC rules decide what it may do with them. Under 47 CFR 64.2003(o) the CPNI subpart treats an interconnected VoIP provider as a carrier, 64.2005 limits marketing use to categories you already subscribe to unless you approve more, 64.2009(c) requires a retained record of every third-party disclosure, and 64.2010 sets how the provider must authenticate you before handing call detail back. Ask for the annual certificate described in 64.2009(e) and run the phone authentication test before you trust any of it.

Does a virtual PBX help a small sales team make more calls

No, and that is the single most common mismatch in this category. A virtual PBX routes calls that arrive; it does not decide the next number, advance a list, detect whether a human picked up, or record the outcome. Those are dialer functions. A small team whose growth depends on outbound work should evaluate the answering features and the outbound features as two separate requirements, then buy one system that covers both rather than two that overlap.

Sources

• 47 CFR 64.2003, Definitions, Subpart U, Customer Proprietary Network Information, Electronic Code of Federal Regulations. Paragraph (o) states that the terms “telecommunications carrier” or “carrier” have the meaning set forth in section 3(44) of the Communications Act of 1934, as amended, and that for the purposes of this subpart the term shall include an entity that provides interconnected VoIP service, as that term is defined in section 9.3 of these rules. Paragraph (d) defines call detail information as any information that pertains to the transmission of specific telephone calls, including, for outbound calls, the number called, and the time, location, or duration of any call and, for inbound calls, the number from which the call was placed, and the time, location, or duration of any call. Paragraph (a) defines account information as information specifically connected to the customer’s service relationship with the carrier, including an account number or any component thereof, the telephone number associated with the account, or the bill’s amount. Paragraph (b) defines an address of record as a postal or electronic address the carrier has associated with the customer’s account for at least 30 days. Paragraph (m) defines readily available biographical information as information drawn from the customer’s life history, including a social security number or the last four digits of that number, mother’s maiden name, home address, or date of birth. Paragraph (g) ties CPNI to the definition in section 222(h)(1) of the Communications Act. Subpart U carries a source note of 82 FR 44419, September 21, 2017. Reviewed October 29, 2026.
• 47 CFR 9.3, Definitions, Electronic Code of Federal Regulations. The section defines an interconnected Voice over Internet Protocol (VoIP) service as a service that enables real-time, two-way voice communications; requires a broadband connection from the user’s location; requires internet protocol-compatible customer premises equipment (CPE); and permits users generally to receive calls that originate on the public switched telephone network and to terminate calls to the public switched telephone network. It adds that, solely for purposes of compliance with the Commission’s 911 obligations, an interconnected VoIP service includes a service that meets the first three parts of the definition and permits users generally to terminate calls to the public switched telephone network. Reviewed October 29, 2026.
• 47 CFR 64.2005, Use of customer proprietary network information without customer approval, Electronic Code of Federal Regulations. Paragraph (a) permits a carrier to use, disclose, or permit access to CPNI for the purpose of providing or marketing service offerings among the categories of service to which the customer already subscribes from the same carrier, without customer approval. Paragraph (b) provides that a carrier may not use, disclose, or permit access to CPNI to market service offerings within a category of service to which the subscriber does not already subscribe from that carrier unless the carrier has customer approval, subject to the exceptions in paragraph (c). Paragraph (b)(2) provides that a carrier may not use, disclose or permit access to CPNI to identify or track customers that call competing service providers, giving the example of a local exchange carrier using local service CPNI to track customers that call local service competitors. Paragraph (c)(3) refers to entities that provide interconnected VoIP service as that term is defined in section 9.3 of the chapter. Reviewed October 29, 2026.
• 47 CFR 64.2007, Approval required for use of customer proprietary network information, Electronic Code of Federal Regulations. Paragraph (a) permits approval through written, oral or electronic methods, places the burden of demonstrating compliance on a carrier relying on oral approval, provides that an approval or disapproval remains in effect until the customer revokes or limits it, and requires a carrier to maintain records of approval, whether oral, written or electronic, for at least one year. Paragraph (b) provides that a carrier may, subject to opt-out approval or opt-in approval, use its customer’s individually identifiable CPNI for the purpose of marketing communications-related services to that customer and may disclose it on the same basis to its agents and affiliates that provide communications-related services, and that except for uses permitted without approval under 64.2005 or described in that paragraph, a carrier may only use, disclose, or permit access to individually identifiable CPNI subject to opt-in approval. Reviewed October 29, 2026.
• 47 CFR 64.2009, Safeguards required for use of customer proprietary network information, Electronic Code of Federal Regulations. Paragraph (c) requires all carriers to maintain a record of their own and their affiliates’ sales and marketing campaigns that use customers’ CPNI, and a record of all instances where CPNI was disclosed or provided to third parties or where third parties were allowed access, including a description of each campaign, the specific CPNI used, and what products and services were offered, retained for a minimum of one year. Paragraph (d) requires a supervisory review process for outbound marketing situations with records kept for a minimum of one year. Paragraph (e) requires an officer, as an agent of the carrier, to sign and file with the Commission an annual compliance certificate stating personal knowledge that the company has established operating procedures adequate to ensure compliance with the subpart, accompanied by a statement explaining how those procedures ensure compliance, an explanation of any actions taken against data brokers, and a summary of all customer complaints received in the past year concerning the unauthorized release of CPNI, filed annually with the Enforcement Bureau on or before March 1 in EB Docket No. 06-36 for data pertaining to the previous calendar year. Paragraph (a) requires carriers to implement a system by which the status of a customer’s CPNI approval can be established prior to use, and paragraph (b) requires personnel training and an express disciplinary process. Reviewed October 29, 2026.
• 47 CFR 64.2010, Safeguards on the disclosure of customer proprietary network information, Electronic Code of Federal Regulations. Paragraph (a) requires carriers to take reasonable measures to detect and protect against attempts to gain unauthorized access to CPNI and to properly authenticate a customer prior to disclosing CPNI based on customer-initiated telephone contact, online account access, or an in-store visit. Paragraph (b) provides that carriers may only disclose call detail information over the telephone, based on customer-initiated telephone contact, if the customer first provides a password that is not prompted by the carrier asking for readily available biographical information or account information, and that absent a password the carrier may only disclose call detail information by sending it to the customer’s address of record or by calling the customer at the telephone number of record, while permitting the carrier to discuss call detail information the customer supplies without carrier assistance. Paragraph (c) requires authentication without readily available biographical information or account information before online access, and paragraph (e) sets the same constraint on establishing a password and on any back-up authentication method. The section carries a cross-reference to an amendment published at 88 FR 85814 on December 8, 2023 and a correction published at 88 FR 88261 on December 21, 2023. Reviewed October 29, 2026.
• 47 CFR 64.2011, Notification of customer proprietary network information security breaches, Electronic Code of Federal Regulations. Paragraph (a) provides that a carrier shall notify law enforcement of a breach of its customers’ CPNI and shall not notify customers or disclose the breach publicly until it has completed the law enforcement notification process. Paragraph (b) requires the carrier, as soon as practicable and in no event later than seven business days after reasonable determination of the breach, to electronically notify the United States Secret Service and the Federal Bureau of Investigation through a central reporting facility, and provides that the carrier shall not notify customers or disclose the breach publicly until seven full business days have passed after that notification, subject to paragraph (b)(2) for an extraordinarily urgent need to avoid immediate and irreparable harm after consultation with the relevant investigating agency and paragraph (b)(3) permitting the investigating agency to direct a delay of up to an initial 30 days, extendable, where disclosure would impede or compromise a criminal investigation or national security. Paragraph (c) requires customer notification once the law enforcement process is complete. The section carries a cross-reference to an amendment published at 89 FR 10002 on February 12, 2024. Reviewed October 29, 2026.
• 47 USC 222, Privacy of customer information, United States Code, U.S. Government Publishing Office. Subsection (a) states that every telecommunications carrier has a duty to protect the confidentiality of proprietary information of, and relating to, other telecommunication carriers, equipment manufacturers, and customers. Subsection (c)(1) limits a carrier’s use, disclosure of, or permitted access to individually identifiable CPNI to the telecommunications service from which the information is derived or services necessary to or used in its provision, except as required by law or with the approval of the customer. Subsection (c)(2) states that a telecommunications carrier shall disclose customer proprietary network information, upon affirmative written request by the customer, to any person designated by the customer. Subsection (h)(1) defines customer proprietary network information as information that relates to the quantity, technical configuration, type, destination, location, and amount of use of a telecommunications service subscribed to by any customer and made available to the carrier solely by virtue of the carrier-customer relationship, together with information contained in the bills pertaining to telephone exchange service or telephone toll service, excluding subscriber list information. Reviewed October 29, 2026.
• Kixie Ring Groups, kixie.com. The page states that ring groups route incoming calls to multiple agents in one of three ways, simultaneous, linear, and linear round robin; that simultaneous ring groups ring all assigned agents at once and connect with whoever answers first, linear ring groups ring one agent at a time based on list position, and linear round robin distributes calls evenly among agents; that a No Answer Action setting determines what happens when no assigned agent is available and calls can be routed anywhere except the same ring group; that any number of agents with an active Kixie account can be added to a ring group; and that within ring group settings an external device such as a mobile phone, desk phone or landline can be selected per agent, with multiple devices available for a single agent. Reviewed October 29, 2026.
• Kixie Plans, kixie.com. The page publishes a Professional plan including click to call and click to text, SMS templates, Voicemail Drop and live call coaching; a Single-Line PowerDialer plan adding the single-line PowerDialer and calling session management; and a Multi-Line PowerDialer plan described as Professional features plus PowerDial up to 4 lines simultaneously, with calling session management and AI Human Voice Detection marked as a premium add on. ConnectionBoost and Conversation Intelligence are listed under Available Add-ons as premium add-ons. All plans are described as including unlimited minutes covering calls in the US and Canada. Reviewed October 29, 2026.
• Kixie PowerDialer, kixie.com. The page states that Kixie’s PowerDialer uses multi-line dialing and AI Human Voice Detection to help sales teams spend less time dialing manually and more time in live conversations; that the PowerDialer automatically dials through a list of leads and that as soon as a rep completes a call or leaves a voicemail the next number on the list is dialed automatically; that calls, texts, outcomes and recordings are logged in the CRM automatically; and that ConnectionBoost combines local presence, number monitoring, and progressive caller ID to help teams manage outbound number reputation and pickup rates. Reviewed October 29, 2026.

Sources verified by the Kixie Research Team on October 29, 2026.