IRS Notice Intake: Authorization and Representation Boundaries

Capture the notice without deciding what it means

Record the CP or LTR number, notice date, stated response or payment date, tax form and period, delivery channel, client’s description, pages received, attachments, and any prior action. Preserve a clean copy through the approved channel and distinguish the notice text from the client’s interpretation. Support may use the IRS notice index to identify general published instructions, but it should not decide whether the IRS is correct, calculate a balance, concede an issue, choose evidence, draft a protest, waive appeal rights, or promise resolution.

Verify identity, engagement, and authorization separately

Identity verification, engagement scope, permission to receive information, and authority to represent are different controls. IRS guidance distinguishes Form 8821 tax information authorization from Form 2848 power of attorney; an 8821 designee may inspect or receive specified information but is not thereby authorized to represent the taxpayer. Confirm the tax matters and periods shown in the authoritative authorization record. A spouse, employee, family member, bookkeeper, or return preparer is not automatically authorized for every conversation or action.

Route representation and Circular 230 work

Practice before the IRS includes consequential communications and representation work governed by current law, authorization, practitioner status, engagement, and Circular 230. General support should not claim attorney-client privilege, practitioner-client privilege, power of attorney, admission to practice, or a representative relationship. Route dispute strategy, appeals, collection alternatives, penalty relief, substantiation, amended returns, transcripts, conferences, agreements, and signature questions to the designated qualified professional, and confirm that person accepted the matter.

Protect dates, evidence, and client expectations

A notice workflow should preserve the exact stated date, source, time received, response method, submission evidence, delivery confirmation, and next owner. Do not tell a client that calling, uploading, paying, or asking for help automatically preserves appeal rights or pauses collection. If the notice appears suspicious, follow the IRS verification path and the practice’s fraud procedure rather than using contact information supplied by an unverified message. Tell the client what is known, what remains unverified, what was routed, and when a status update will occur.

Build the control table

Govern knowledge and qualified handoff

Every answer should point to a dated, owned source. Separate public IRS education, firm policy, engagement terms, client statements, return data, notices, account records, and practitioner analysis. Require qualified review for tax positions, preparation, filing, representation, Circular 230, Section 7216, fees, deadlines, payments, notices, privacy, security, identity, accessibility, consent, and jurisdiction questions. Log the source version, authorization state, authority boundary, receiving owner, and client confirmation. A summary is useful only when its provenance can be checked and the authorized destination accepts the matter.

Protect taxpayer data and service resilience

Collect the minimum information needed in approved channels. Define identity verification, access, retention, redaction, recording, consent, export, deletion, document, and vendor controls under the practice’s written information security plan. Provide accessible interaction, effective communication, error recovery, a human alternative, and reviewed language support without inventing a language count. Test outages, stale deadlines, duplicate uploads, malicious prompts, attempted credential disclosure, impersonation, suspicious notices, and failed handoffs with synthetic data. Record limitations, owners, incident paths, and rollback procedures.

Apply scope and qualified review

This article provides general operational information, not tax, legal, accounting, financial, representation, preparer, privacy, security, identity, accessibility, or compliance advice. Client, entity, return, form, tax period, notice, authorization, engagement, fee arrangement, deadline, payment, practitioner status, jurisdiction, systems, and current law control. A configured conversational system may assist approved intake and routing, but this article does not claim LumiTalk prepares, signs, files, amends, or transmits returns; calculates tax, penalties, interest, refunds, or fees; selects a position; gives tax advice; represents a taxpayer; executes a payment; validates Section 7216 consent; guarantees deadlines, outcomes, security, or compliance; reads live IRS or client data; or provides exact pricing, availability, language, or integration coverage.

Primary sources

Use current primary sources as the factual floor, then obtain practice, engagement, practitioner, client, return, notice, tax period, and jurisdiction-specific qualified review. Understanding Your IRS Notice or Letter · Power of Attorney Information · Disclosure Authorizations · Office of Professional Responsibility and Circular 230

Continue through the Tax Practices cluster

Use the hubs and service page for cluster context, then compare adjacent guides before implementing a workflow. Tax Practices resource hub · Tax & Accounting resource hub · LumiTalk for tax-practice operations · Tax Practice Customer Support Operations Guide · Tax Deadlines, Extensions, and Payment Support · Section 7216 and Data Security Guide