Free Word download • Edit online • Save & share with Drive • Export to PDF
A Thank You For Your Request For More Information Letter is a formal written acknowledgment that a business sends to a prospect, client, or counterparty to confirm receipt of an inquiry about its products, services, or contract terms. It formally records that the request was received, summarizes the scope of what was asked, sets a concrete timeline for the substantive response, and — critically — protects the sending organization from inadvertently making binding representations before a formal proposal or agreement is in place. The letter functions legally as an invitation to treat, not an offer, provided it includes the appropriate non-binding disclaimer and reservation-of-rights language.
Responding to an information request with a casual email reply is common practice — and a meaningful source of commercial and legal risk. Specific statements about pricing, availability, or delivery timelines made in informal correspondence have been treated as binding representations in disputes, particularly where the recipient demonstrates reliance on them. A structured acknowledgment letter closes that gap: it confirms receipt professionally, sets expectations on timing, and makes unambiguously clear that the communication is administrative rather than contractual. Without it, a sales team's well-intentioned reply can become exhibit A in a misrepresentation claim or a pricing dispute. This template gives you a consistent, legally sound starting point you can complete in under 15 minutes — and that a lawyer can review quickly if the stakes warrant it.
| If your situation is… | Use this template |
|---|---|
| Responding to a prospect's general product or service inquiry | Thank You For Your Request For More Information |
| Formally responding to a government or institutional RFI | Request For Information Response Letter |
| Acknowledging a client's complaint while gathering information | Acknowledgment of Complaint Letter |
| Confirming receipt of a job application or resume | Application Acknowledgment Letter |
| Responding to a media or press inquiry | Media Inquiry Response Letter |
| Acknowledging a formal legal or regulatory information request | Response to Legal Information Request Letter |
| Following up after an initial product demo with next steps | Follow-Up Letter After Product Demonstration |
Why it matters: A price quoted in an acknowledgment letter can be treated as a binding offer in some jurisdictions if the recipient formally accepts it before you send a formal proposal with revised terms.
Fix: Either omit pricing entirely from the acknowledgment or append 'indicative only, subject to formal quotation and change without notice' immediately after any figure.
Why it matters: If the letter is later cited in a contract dispute or regulatory proceeding, the other party may challenge its weight on the basis that the signatory had no authority to bind the company.
Fix: Establish a signing policy that requires acknowledgment letters related to contracts above a certain value to be signed by a director, VP, or general counsel.
Why it matters: Without a governing law clause, courts must conduct a choice-of-law analysis to determine which jurisdiction's rules apply — a process that is expensive, unpredictable, and often produces results neither party anticipated.
Fix: Always include a governing law clause naming the jurisdiction, especially when the sender and recipient are located in different countries or states.
Why it matters: When the substantive response is delivered, scope disputes — 'that's not what we asked for' — are common and damaging to the relationship. Without a written scope summary, there is no anchor to resolve the disagreement.
Fix: Include a numbered list of the information categories requested and invite the recipient to correct it within three to five business days of receiving the acknowledgment.
Why it matters: Vague timelines signal disorganization, damage credibility with prospects, and provide no basis for a follow-up if the deadline passes without a response.
Fix: Always state a specific date or a defined number of business days — e.g., 'no later than [DATE] or within 7 business days of the date of this letter.'
Why it matters: In pre-litigation, regulatory, or contentious commercial contexts, the absence of a reservation-of-rights clause has been successfully argued as implicit waiver of certain defenses.
Fix: Keep the reservation-of-rights clause in every acknowledgment letter regardless of how routine the inquiry appears. It costs nothing and protects against edge-case arguments.
In plain language: Identifies the sending organization and the recipient, with the date the letter is issued.
[COMPANY NAME] ('Company'), located at [ADDRESS], acknowledges receipt of the inquiry submitted by [RECIPIENT NAME / ORGANIZATION] ('Requestor') on [DATE OF REQUEST].
Common mistake: Using a department name instead of the legal entity name as sender, which can create ambiguity about which entity is corresponding and who bears any resulting obligations.
In plain language: Formally confirms that the specific information request has been received and identifies the subject matter of the inquiry.
We acknowledge receipt of your request dated [DATE] regarding [SPECIFIC SUBJECT MATTER — e.g., pricing for [PRODUCT/SERVICE], terms of [CONTRACT TYPE], or specifications for [OFFERING NAME]].
Common mistake: Acknowledging a request in vague terms without referencing the subject matter — leaving both parties uncertain about what was actually received and increasing dispute risk.
In plain language: States clearly that the acknowledgment letter is not an offer, agreement, or commitment — it is administrative correspondence only.
This letter is provided for informational and administrative purposes only. Nothing contained herein constitutes an offer, agreement, representation, warranty, or legally binding commitment of any kind on the part of [COMPANY NAME].
Common mistake: Omitting this clause entirely. Without it, specific statements about pricing, availability, or delivery timelines made in an acknowledgment can be construed as binding representations.
In plain language: Briefly lists the categories of information the recipient has asked for, confirming mutual understanding of the scope of the request.
Our understanding is that your request encompasses the following: (a) [ITEM 1], (b) [ITEM 2], and (c) [ITEM 3]. If this summary does not accurately reflect the scope of your inquiry, please notify [CONTACT NAME] at [EMAIL / PHONE] within [X] business days.
Common mistake: Skipping the scope summary and proceeding directly to next steps — when the scope is later disputed, there is no written record confirming what both parties understood the request to cover.
In plain language: States when the recipient can expect a substantive response and names the specific next action the company will take.
We anticipate providing a full response to your request no later than [DATE / X BUSINESS DAYS from the date of this letter]. Your primary point of contact for this matter is [NAME], [TITLE], reachable at [EMAIL] or [PHONE].
Common mistake: Stating a response timeline without naming a specific point of contact. The recipient has no actionable path forward if the timeline slips, leading to follow-up emails to random inboxes.
In plain language: Establishes that any proprietary or sensitive information shared by either party in connection with the request will be treated as confidential.
Any proprietary, technical, or commercially sensitive information shared by either party in connection with this request shall be treated as confidential and shall not be disclosed to third parties without prior written consent, unless required by applicable law.
Common mistake: Including confidentiality language only for the company's outbound information while ignoring the requestor's materials — exposing the company to liability if the requestor's specifications or business data are later disclosed.
In plain language: Preserves the company's full legal rights and confirms that responding to the request does not constitute a waiver of any right, claim, or defense.
[COMPANY NAME] expressly reserves all rights and remedies available at law or in equity. Nothing in this letter shall be construed as a waiver of any right, claim, or defense, or as an admission of liability or obligation of any kind.
Common mistake: Treating this as boilerplate and deleting it to shorten the letter. In regulatory or pre-litigation contexts, the absence of a reservation-of-rights clause has been used to argue implicit waiver.
In plain language: Specifies which jurisdiction's laws govern the letter and any dispute arising from it.
This letter and any dispute arising out of or in connection with it shall be governed by and construed in accordance with the laws of [STATE / PROVINCE / COUNTRY], without regard to its conflict-of-laws provisions.
Common mistake: Omitting governing law in cross-border correspondence. When the sender and recipient are in different jurisdictions, the absence of a governing law clause forces courts to conduct a choice-of-law analysis — often producing an unexpected result.
In plain language: Contains the name, title, organization, signature, and date of the authorized person sending the letter, confirming it was issued by someone with authority.
Sincerely, [AUTHORIZED SIGNATORY NAME] | [TITLE] | [COMPANY NAME] | [DATE] | [EMAIL] | [PHONE NUMBER]
Common mistake: Having an unauthorized employee sign the letter without any signatory authority. If the letter is later referenced in a contract dispute, the lack of authority can be raised to challenge the correspondence's evidentiary weight.
Fill in the company's full legal name and address at the top of the letter, along with the recipient's full name, title, and organization. Enter the date the letter is being issued — not the date the original request was received.
💡 Use your registered legal entity name, not your trade name or DBA, to ensure the letter is attributable to the correct contracting party.
In the acknowledgment clause, cite the date the request was received, the reference number if one was assigned, and a concise description of the subject matter. This creates an auditable record tying your response to the specific inquiry.
💡 If the request came by email, quote the subject line verbatim. If it arrived via a web form or RFI portal, include the submission ID.
List the specific categories of information the requestor has asked for — product specifications, pricing, delivery timelines, contract terms, or other details. Keep this summary to three to five bullet points and invite the recipient to correct any misunderstanding within a defined timeframe.
💡 A short, numbered scope summary prevents scope-creep disputes later and demonstrates that you read and understood the request.
Confirm that the non-binding clause is present and clearly states the letter is not an offer or commitment. Review any factual statements in the letter — pricing estimates, availability windows — to ensure they are framed as preliminary and subject to change.
💡 If you must include any preliminary pricing or timeline information, add the phrase 'subject to formal agreement and change without notice' immediately after each figure.
Enter the date or number of business days by which you will deliver the substantive response. Add the name, email, and direct phone number of the designated point of contact. Do not leave the timeline or contact as placeholders — a blank here is equivalent to no commitment.
💡 Net 5 to 10 business days is the standard acknowledgment-to-response window for most B2B inquiries. Anything longer should be explained with a brief reason in the letter.
Review the confidentiality clause to ensure it covers both your outbound information and any materials shared by the requestor. If the inquiry relates to a sensitive tender, regulatory matter, or pre-contract negotiation, consider whether a standalone NDA is needed before sharing any substantive response.
💡 If you already have an NDA in place with this party, reference its effective date in the confidentiality clause rather than creating duplicate or conflicting obligations.
Route the completed letter to the appropriate authorized signatory — sales director, general counsel, or owner — before sending. Confirm their title and authority level match what would be expected for the subject matter of the inquiry.
💡 For high-value or legally sensitive inquiries, have legal counsel review the letter before it leaves the building, even if no substantive information is included.
Send the signed letter via email with read receipt, or by the same channel the original request arrived. Retain a copy of the sent letter and the original request in the same file or CRM record, timestamped.
💡 Store the original request and your acknowledgment letter together — if a dispute arises, having both documents in sequence is far more persuasive than producing each separately.
A thank you for your request for more information letter is a formal written acknowledgment sent by a business to confirm receipt of an inquiry about its products, services, or contract terms. It serves as an administrative record of the request, sets expectations about the response timeline, and protects the sender from inadvertently creating binding commitments through casual correspondence. It is commonly used in B2B sales, procurement, and professional services contexts.
An acknowledgment letter is generally not legally binding in most jurisdictions, provided it includes a clear non-binding disclaimer and does not contain language that could be construed as an offer capable of acceptance. However, specific statements about pricing, availability, or contract terms made in the letter can become binding representations if the recipient relies on them to their detriment. Including a reservation-of-rights clause and avoiding unqualified commitments reduces this risk significantly.
Use a formal acknowledgment letter when the inquiry relates to a significant contract, a regulated product or service, a government or institutional tender, or any situation where a dispute about the scope or terms of the request might arise later. Email replies work for casual inquiries, but a signed, structured letter creates a more reliable evidentiary record and signals a higher level of professional care to the recipient.
Avoid including specific pricing, delivery commitments, or contractual terms without a non-binding qualifier — these can be construed as offers. Do not include confidential technical specifications unless you have an NDA in place. Avoid admissions of past mistakes or liability, and do not make any statement that could be read as waiving a right or defense. When in doubt, consult legal counsel before adding any substantive content.
Yes. A signed acknowledgment letter carries more evidentiary weight than an unsigned document and confirms that an authorized representative of the company reviewed and endorsed the communication. The signatory's name, title, and authority level should match the significance of the inquiry — a senior-level or legal representative should sign letters related to large contracts or sensitive subject matter.
Best practice is to send the acknowledgment letter within one to two business days of receiving the request. In B2B procurement and government contracting, acknowledgment within 24 hours is often expected and sometimes required by the RFI process. Delaying acknowledgment risks the requestor assuming the inquiry was lost or ignored and approaching a competitor.
This template provides a useful starting framework, but formal government or regulatory information requests — such as those from the SEC, FTC, HMRC, or similar authorities — typically carry mandatory response requirements, specific format rules, and legal consequences for non-compliance. Consider this template a starting point only and engage legal counsel before responding to any regulatory information request.
This acknowledgment letter may include a brief confidentiality clause as a courtesy, but it is not a substitute for a standalone non-disclosure agreement. An NDA creates mutual, enforceable confidentiality obligations with defined remedies for breach. If the inquiry involves sharing proprietary pricing models, technical specifications, or strategic plans, execute a full NDA before providing any substantive response.
The core structure of this letter is consistent across major business jurisdictions, but the governing law clause, confidentiality standards, and any reference to statutory rights should reflect the applicable jurisdiction. In the EU, GDPR compliance may be relevant if personal data is processed in connection with the request. In Canada, French language requirements apply in Quebec. Consider local legal review for any cross-border correspondence involving sensitive subject matter.
An NDA creates mutual, enforceable confidentiality obligations with defined breach remedies and is required before sharing genuinely proprietary information. This acknowledgment letter may include a courtesy confidentiality clause but does not substitute for an NDA. Use both when the substantive response to the inquiry will include sensitive technical or commercial data — execute the NDA first, then send the full response.
A business proposal is the substantive, often binding response to an information request — it includes pricing, scope, timelines, and terms. This acknowledgment letter precedes the proposal, confirms the inquiry was received, and sets expectations about when the proposal will follow. The letter protects you during the gap between receipt and response; the proposal governs the deal itself.
A follow-up letter is sent by the requesting party to check on the status of a pending response. This acknowledgment letter is sent by the responding party to confirm receipt and set a response timeline. They address opposite sides of the same communication cycle — acknowledgment reduces the need for follow-ups by proactively managing the requestor's expectations.
A letter of intent signals a party's intention to enter into a specific agreement and may create preliminary obligations around exclusivity or confidentiality. This acknowledgment letter creates no such obligations — it confirms receipt and reserves all rights. If an information exchange leads to active deal negotiations, a letter of intent is the appropriate next document.
Acknowledging enterprise prospect RFIs about API capabilities, security certifications, and pricing tiers without inadvertently committing to custom feature development.
Confirming receipt of client briefs for consulting, legal, or accounting engagements before scoping a formal proposal, protecting against scope disputes.
Responding to supplier and buyer information requests about product specifications, lead times, and minimum order quantities during procurement processes.
Acknowledging requests from providers or payers for information about medical device capabilities or service coverage, with heightened attention to regulatory disclaimers.
In the US, acknowledgment letters are generally non-binding unless they contain language constituting an offer under the UCC or common law contract principles. State law governs enforceability of representations made in pre-contract correspondence, and courts in some states — notably California and New York — apply strict tests for whether written statements create promissory estoppel claims. A clear non-binding disclaimer and reservation-of-rights clause are essential for any commercially significant inquiry response.
Canadian common law provinces apply similar contract formation principles to the US, but courts have been receptive to promissory estoppel claims where a party relied on written representations made before a formal agreement. In Quebec, civil law principles apply and pre-contractual good faith obligations are more explicit under the Civil Code. French language requirements apply to business correspondence sent to Quebec recipients in provincially regulated sectors.
Under English law, acknowledgment letters are typically treated as invitations to treat rather than binding offers, provided non-binding language is clearly included. However, representations made in pre-contractual correspondence can give rise to misrepresentation claims under the Misrepresentation Act 1967 if they are false and the other party relied on them. GDPR obligations apply if personal data is referenced or processed in connection with the information request.
EU member states impose pre-contractual good faith obligations to varying degrees — Germany and France have relatively strong duties of good faith in negotiations that can extend to written acknowledgments. GDPR applies where the request or response involves processing personal data, requiring appropriate data handling disclosures. The governing law clause should specify a member state's law to avoid ambiguity under the Rome I Regulation, which determines applicable contract law for cross-border EU correspondence.
| Path | Best for | Cost | Time |
|---|---|---|---|
| Use the template | Standard B2B or B2C information request acknowledgments where the subject matter is routine and no sensitive data is shared | Free | 10–15 minutes |
| Template + legal review | Acknowledgments related to high-value contracts, regulated industries, or cross-border correspondence where governing law selection matters | $150–$400 for a brief legal review | 1–2 business days |
| Custom drafted | Government or regulatory information requests, pre-litigation correspondence, or inquiries involving trade secrets or highly sensitive commercial terms | $500–$2,000+ | 3–7 business days |
This document is one of 3,000+ business & legal templates included in Business in a Box.
Access over 3,000+ business and legal templates for any business task, project or initiative.
Customize your ready-made business document template and save it in the cloud.
Share your files and folders with your team. Create a space of seamless collaboration.
"Fantastic value! I'm not sure how I'd do without it. It's worth its weight in gold and paid back for itself many times."
"I have been using Business in a Box for years. It has been the most useful source of templates I have encountered. I recommend it to anyone."
"It has been a life saver so many times I have lost count. Business in a Box has saved me so much time and as you know, time is money."
Stop downloading documents. Start operating with clarity. Business in a Box gives you the Business Operating System used by over 250,000 companies worldwide to structure, run, and grow their business.
Start free · No credit card required
