You want a list. A spreadsheet with company names in one column and “US-based support” in the other, so you can spend money on the second column and skip the first. Reasonable thing to want. Every few months someone posts a partial version of it and the replies correct half of it within an hour, because those entries were true eighteen months ago and are not true now.

The blunt answer: No accurate public list of companies that keep customer support in the United States exists, and none can be maintained, because support location is not a company-level fact. It is a queue-by-queue, shift-by-shift, contract-by-contract fact, and it changes without any announcement. What does exist is a reliable way to find out about the specific companies you care about, in about twenty minutes each, and that is worth more than a list anyway.

One disclosure first, because it should affect how you read this: the company publishing this article does outsourced support work, including offshore. That gives us a clear view of how these operations get built, and it also gives us a bias. Nothing below is an attempt to talk you out of your preference. If you want to spend your money with companies that employ Americans to answer their phones, that is a legitimate use of your money, and the rest of this is about how to act on it.

Why the list you want can’t be kept honest

Four structural reasons, and they compound.

Most companies use more than one site. A mid-sized retailer might have fifteen in-house staff in Ohio on escalations and high-value accounts, a domestic vendor on weekday overflow, and an offshore vendor covering nights, weekends and the December peak. All of it is “their support.” A list entry reading “US-based” is true at 10am Tuesday and false at midnight Sunday.

The split runs by queue, not by company. Billing offshore, technical onshore. Or chat and email offshore, phone onshore, because voice carries accent friction and text does not. Or tier one offshore and tier two onshore, the most common arrangement of all, and the reason so many people report that the first person couldn’t help and the second fixed it in four minutes.

Vendor contracts turn over. Outsourced support is usually contracted in one to three year terms. A company that moved support to Manila in 2022 may have moved it to Bogotá in 2024 for time-zone reasons, then brought escalations back to Kansas after a churn problem. Nobody issues a press release about any of it.

Almost nobody discloses it voluntarily. There is no upside in publishing a support map and a clear downside, so the default is silence. Companies that do keep support domestic usually advertise it, which is the one reliable signal in the whole system.

Add remote work on top. A vendor in Texas may staff your queue from three states, and a Philippine vendor may have US-based leads on the same account. The model where a call center is a building in a place describes less of the industry every year.

What you can actually find out about a specific company

You can get a solid answer on most companies. Run these in order and stop when you have enough.

• Look for a published support location policy. Search the company’s own site for phrases like “based in the United States,” “US-based support,” “our support team is located.” Companies that keep support domestic tend to put it on the product page, the support page footer, or the about page, because they are paying more for it and want credit. Silence is not proof of offshoring, but a company that could truthfully claim domestic support and doesn’t is unusual.
• Read their job postings. This is the single best signal available to an outsider. Search their careers site, and separately search Indeed and LinkedIn for the company name plus “customer support,” “customer service representative,” “member services,” or “technical support.” If every support opening is in Tampa and Boise, support is domestic. If there are no support openings at all while the company is clearly growing, support is contracted out, and you have learned something real.
• For public companies, read the 10-K. Use the SEC’s EDGAR full-text search, which covers filings since 2001. Search the company name and terms like “call center,” “customer support,” “outsourced,” or the names of countries. Risk-factor sections frequently disclose reliance on third-party customer-service providers and sometimes name the regions, because reliance on a single offshore site is a risk shareholders are entitled to know about. This is the only place many companies say it in writing.
• Ask the agent. Most support agents are permitted to answer this, at both domestic and offshore sites. What gets people stonewalled is the accusatory version. Try: “Quick question, nothing to do with my issue, and no problem either way. What city are you in?” Roughly nine times in ten you get a straight answer. If the agent says they aren’t allowed to say, that is itself informative.
• Ignore the area code and the accent. Toll-free numbers say nothing about where a call lands. Accents tell you about a person, not a site: domestic centers employ immigrants, offshore centers employ people raised on American media, and guessing wrong is both rude and useless.

What US law requires, and what it plainly does not

There is no general duty to tell you where support sits

Be careful here, because summaries circulating online routinely describe proposed legislation as though it were in force. No federal law requires a company to disclose the country in which its customer support agents work, and no FCC rule imposes one either.

What federal law actually requires in this area is narrower. The FTC’s Telemarketing Sales Rule, at 16 CFR 310.4(d), requires a telemarketer selling goods or services to promptly disclose the identity of the seller, that the purpose of the call is to sell, the nature of what’s being sold, and, where a prize promotion is involved, that no purchase is necessary. Location is not on that list. On the carrier side, 47 CFR 64.2010 requires telecommunications carriers to take reasonable measures to protect against unauthorized access to customer information and sets out authentication duties. It says nothing about where the person doing the authenticating is sitting.

The Made in USA rules do not fill the gap. The FTC’s Made in USA Labeling Rule at 16 CFR 323.2 makes it an unfair or deceptive practice to label a product Made in the United States unless final assembly or processing happens here, all significant processing happens here, and all or virtually all components are made and sourced here. That is a product-labeling standard, not a services-origin standard, and it requires nobody to tell you where their help desk is.

What does still apply is ordinary deception law. If a company advertises US-based support and routes you offshore, that is a false claim about a service, and false claims about services are within the FTC’s Section 5 authority regardless of the labeling rule. So the advertised claim is worth more than a silence, and it is worth a complaint if it turns out to be untrue.

Bills to create a real disclosure duty have been introduced in Congress repeatedly, most often as the United States Call Center Worker and Consumer Protection Act. The recurring design pairs a right to ask an agent where they are with notice requirements and federal-funding consequences for employers that move call center work offshore. None of it has become law. Check the current status on congress.gov rather than trusting any summary, this one included.

Where location genuinely is constrained

There are real mandates, and it’s worth understanding what they actually pin down, because in most cases they constrain where data may go rather than where a person may sit.

• Federal tax information. IRS Publication 1075, which governs agencies and contractors handling federal tax information, includes an offshore operations section and a control enhancement restricting “the accessing, processing, storage, and transmission of FTI to the United States and its territories.” This one does effectively bind agent location, because access is in the list. If you are calling a state agency about your taxes, the person on the line is in the United States.
• Defense and export-controlled work. Under ITAR at 22 CFR 120.50(a)(2), releasing technical data to a foreign person counts as an export even when the release happens inside the United States. Nationality is the actual legal test, which is why defense-adjacent programs carry US-persons-only clauses.
• Government contracts generally. Solicitations and agency policies impose place-of-performance and citizenship terms. Those are contract terms, not general law, and they vary by agency and by contract.
• Regulated financial and health functions. Banking and healthcare rules demand controls, oversight and accountability rather than geography. Medicaid programs require attestations about offshore subcontracting, and health privacy duties follow the records to subcontractors anywhere. That makes offshore handling of certain records administratively expensive, not illegal.
• Data-residency clauses in private contracts. When a large enterprise buyer requires that its customer records never leave US infrastructure, that flows down to the support vendor. It is the most common real constraint of all, and it is written by lawyers, not legislators.

What actually decides whether support is any good

Here the honest version departs from both sides of the usual argument. A badly run domestic center and a well-run offshore one are both extremely common, and what separates good from bad is not the country. It is five things, all of them budget decisions made by the company that hired the center.

Training investment. Two weeks of product training versus four days of script reading produces a visible difference on the first call. Tenure and attrition. Annual attrition in this industry runs high everywhere; a team where the average agent has eight months of experience behaves completely differently from one averaging three weeks. Scope and authority. The most maddening support experience in the world is a competent, sympathetic person who is not permitted to issue your refund. That is a permissions setting, not a skills gap. Staffing to demand. Understaffed queues produce rushed agents who transfer you to get their handle time down. Incentive design. Bonus an agent on average handle time and they will end calls; bonus them on resolution without a repeat contact and they will fix things.

The BLS puts US customer service representative employment at roughly 2,666,000 jobs in 2025, with median pay of $44,770 a year, and projects a 5% decline over the decade to 2035, a loss of about 141,800 positions. Those are real domestic jobs, and the pressure on them is coming at least as much from automated deflection as from offshoring.

The reasons to prefer domestic support, stated straight

People often present these as irrational, and they aren’t.

• Supporting local employment. Directing your spending toward companies that employ people in your country is a coherent choice. It does not need an efficiency justification.
• Dialect and regional familiarity. An agent who knows what a nor’easter does to a roof, or how a Texas utility bill is structured, resolves certain calls faster. This is about shared context, not about accents.
• Data jurisdiction. Keeping your personal information under US legal process, with US courts and US regulators available, is a defensible position on its own terms.
• Time-zone alignment. Domestic support usually means business-hours support that matches yours, with fewer overnight shifts, which correlates with lower fatigue and lower turnover.

If you run the business, you can simply answer the question

The reason this question circulates unanswered is that almost no company has bothered to answer it. Three moves make you the exception.

Publish where support sits. One honest paragraph on your support page beats any marketing claim: which functions your own employees handle and where, and which partners handle the rest, in which countries. Customers punish honesty far less than companies fear. They punish being misled.

Offer a choice of queue where volume allows. Above a few thousand contacts a month this is usually feasible: a menu option or a checkbox for a domestic queue, with a longer stated wait. Customers who care about location will accept a longer wait for it. Customers who do not will take the faster option and be equally happy.

Write location into the vendor contract. A verbal assurance from a vendor’s sales team means nothing eighteen months in, after a site consolidation nobody told you about. Name the permitted delivery sites, require written consent before work moves, require notice of subcontracting, and take audit rights. Then use them once, early, so both sides know the clause is real.

A research routine, and where to look first

Here’s the workable version. Pick the ten companies you spend real money with each year, run the checks above on each in one sitting, and write down what you found and the date you found it. Ten entries you verified yourself and will re-check next year beat a crowdsourced list of two hundred, and it is the only version that stays true.

When you’re choosing between new vendors, the categories where domestic support is most often advertised as a deliberate differentiator are worth knowing: credit unions and community banks, which frequently promote US-based member service as a selling point against the national banks; home security and alarm monitoring, where monitoring center location is a standard spec; and US-manufactured durable goods, particularly tools, outdoor equipment and appliances, where the brand’s domestic manufacturing story usually extends to the warranty line. Small-business software and web hosting is a fourth, though the claims there need checking more often. In each case the claim is on the marketing page, which means you can hold them to it.

Questions that come up next

Can an agent get in trouble for telling me where they are? Usually not. Some employers prefer agents not volunteer it and a few instruct them to deflect, but at most centers it is a permitted answer. Ask politely, accept what you get.

Does “our support is US-based” have a legal definition? No. There is no equivalent of the all-or-virtually-all product standard for service claims. It is an advertising claim, assessable for deceptiveness under general FTC authority, which means a company making it while routing you offshore has a problem, but the phrase itself is not defined anywhere.

What about a “press 1 for a US representative” option? Where it exists it is a company policy choice, not a legal right, and it usually routes to a domestic queue smaller than the main one. Expect a longer hold.

If you are on the other side of this question and you are designing a support function you’d be willing to describe publicly, that is exactly the work AB7 Solutions does. We build and run outsourced support and BPO and KPO operations, we do the contract and delivery-site design that makes a location commitment verifiable rather than decorative, and we staff domestic, offshore and blended teams depending on what the account actually needs. We will also tell you when a blended model is the wrong answer for your customer base, because a support line your customers resent is not a saving. If you want a straight conversation about how to structure it, and what to publish about it: call +1 321 341 7733, or email ab@ab7solutions.com or director@ab7solutions.com. More at www.ab7solutions.com.

Sources: FTC Telemarketing Sales Rule, 16 CFR 310.4(d); FTC Made in USA Labeling Rule, 16 CFR 323.2; FCC CPNI safeguards, 47 CFR 64.2010; ITAR, 22 CFR 120.50(a)(2); IRS Publication 1075 (Rev. 11-2021), section 2.C.7 and control SA-9(5); US Bureau of Labor Statistics, Occupational Outlook Handbook, Customer Service Representatives; SEC EDGAR full-text search.