A telecom letter of agency (LOA) is a signed document that authorizes a third party to act on your behalf with your carriers, most often to obtain customer service records and file billing disputes. Under FCC rules a carrier must act on a valid LOA within 60 days, and the document controls exactly how much power you hand over. Scoped narrowly, it lets an auditor read your records and dispute wrong charges. Scoped loosely, it can also let someone order, change, and disconnect your services, which is far more authority than a records review needs.
The name is the first thing people get wrong, and it matters. Many vendors call this a Letter of Authorization, but the FCC’s official term in federal statute is Letter of Agency. They describe the same document, and the confusion is harmless right up until a carrier rejects a form for not matching the exact wording or record on file.
Key Takeaways
- An LOA authorizes a third party to obtain your carrier records and act on your account. Its scope is a choice, not a fixed template.
- For an audit or expense program, scope it to record access and dispute filing only, never to ordering or disconnecting services.
- The details on the LOA must match the carrier’s account record exactly, or the request gets rejected.
- The records it unlocks, customer service records, are the ground truth an audit reconciles against.
- Number-porting LOAs and audit LOAs look similar but grant different powers. Read which one you are signing.
Short Version
The letter of agency is the key that lets a provider pull your carrier records and dispute charges without you sitting on every call. The only real decision is scope. Grant enough to read records and file disputes, and no more. A well-written LOA is narrow, specific, and time-bound; a risky one authorizes actions you never intended.
What a Letter of Agency Authorizes
A letter of agency appoints a named third party as your agent with your carriers for a defined set of actions over a defined period. At minimum, an audit-focused LOA authorizes release of your customer proprietary network information, defined in federal law as 47 U.S.C. section 222, which includes billing records, service records, and account details. That release is what lets an auditor see what you are actually being charged for, line by line.
The reason scope matters is that some LOAs go much further. Broad templates authorize the agent to order, change, and maintain services across every carrier, which is convenient for a provider and dangerous for a client who only wanted a records review. The safe default is explicit: read the records, file the disputes, touch nothing else.
The Two LOAs People Confuse
A porting LOA and an audit LOA share a format but grant different authority, and signing the wrong one causes different problems. Knowing which you are handing over is the whole point.
| Porting LOA | Audit / expense LOA | |
|---|---|---|
| Purpose | Move phone numbers to a new carrier | Obtain records and dispute charges |
| Grants | Authority to initiate a carrier change | Authority to read records and file disputes |
| Main risk | Data mismatch rejects the port | Over-broad scope grants ordering rights |
| Should it allow disconnects? | Only the numbers being ported | No |
What the LOA Unlocks: Customer Service Records
The document is administrative, but what it unlocks is the most valuable data in a telecom audit. A customer service record, or CSR, is the carrier’s own account of the services provisioned on an account, and it regularly disagrees with both the invoice and your internal records. Reconciling those disagreements is where audit findings come from, and none of it is possible until the LOA authorizes the carrier to release the CSR. This is why record access is the first real step of any telecom refund recovery effort.
How to Fill and Scope One Correctly
A clean LOA process avoids the two failure modes, rejection and over-authorization, by getting the details right and the scope tight. Work through it in order.
- Copy details from a recent invoice. Use the exact account holder name, service address, and account number as the carrier has them, not your everyday business name.
- Name the agent precisely. State who is authorized and for which accounts or number ranges.
- Limit the actions. For an audit, authorize record access and dispute filing. Strike ordering, changing, and disconnecting.
- Set a validity window. Give the authorization explicit start and end dates rather than leaving it open-ended.
- Sign with authority. The signer must be the person authorized to obligate the account, or the carrier can reject it.
Getting the details right is not busywork. When the information on the LOA does not match the carrier’s record, the losing or holding carrier rejects it and returns a reason code, and the entire timeline slips while you correct a mismatched address or a missing account number.
Where the LOA Fits in a Telecom Program
The letter of agency is the authorization layer underneath most telecom expense work, which is why it usually gets signed early in onboarding. It enables the record pulls that feed inventory, it authorizes the disputes that recover money, and its scope should be coordinated with your MACD process so that ordering and disconnecting stay under internal control while records and disputes are delegated. When RadiusPoint begins a telecom engagement, the LOA is scoped to exactly that: authority to obtain customer service records and file disputes, gathered as part of the standard onboarding data set, with service-ordering authority deliberately left with the client.
Frequently Asked Questions
Is a Letter of Agency the same as a Letter of Authorization?
Yes, in practice. Letter of Agency is the FCC’s official term in federal regulation, and Letter of Authorization is a widely used synonym for the same document. Use whichever term your carrier’s form uses to avoid a wording mismatch.
How long is an LOA valid?
For as long as the document states, which is why you should set explicit start and end dates. Open-ended authorizations are harder to control and should be avoided for anything beyond a specific, time-boxed engagement.
Does an LOA let a provider disconnect our services?
Only if the LOA says so. A well-scoped audit LOA does not grant disconnect authority. If a template includes ordering, changing, or disconnecting language and you only want a records review, remove it before signing.
How fast must a carrier act on an LOA?
Federal rules require a carrier to submit a preferred carrier change order within 60 days of receiving a valid letter of agency. Most carriers act within days, but 60 days is the outer regulatory limit for carrier-change requests.
What information does an LOA require?
The account holder name as the carrier has it, the service address, the account number, the numbers or services in scope, a validity period, and an authorized signature. Pulling these from a recent invoice is the reliable way to match the carrier record.
How We Researched This
We reviewed current search results for the telecom letter of agency on 1 September 2026, comparing porting-focused and audit-focused definitions from carriers and expense consultants. The 60-day carrier-change requirement and the CPNI definition were confirmed against FCC rules and 47 U.S.C. section 222 as cited in published carrier LOA forms. Scoping guidance reflects standard telecom audit practice, where record access and dispute filing are separated from service-ordering authority.
Latest Updates
2 September 2026: Rewritten to center the audit and record-access use of the LOA, distinguish it from a porting LOA, and add explicit scoping steps that keep ordering and disconnect authority with the client.
References
- FCC, Letter of Agency terminology and preferred carrier change rules.
- 47 U.S.C. section 222, Customer Proprietary Network Information.
- Carrier LOA forms (Telnyx, FTS) illustrating CPNI release and broad-scope authorization language.
This article is general information and not legal advice. A letter of agency is a legal authorization; have counsel or a qualified advisor review scope and wording before signing anything that grants a third party authority over your accounts.