Is Replying "I Agree" to an Email Legally Binding?
Often, yes. That's the uncomfortable answer.
An email reply can form an enforceable contract, and courts have enforced them. But "can" does a lot of work in that sentence. Whether yours binds you turns on three things most people never consider when hitting send: whether the terms were definite enough, whether you had authority, and whether your name at the bottom counts as a signature.
This guide covers when email acceptance binds, the one phrase that reliably prevents it, and where a formal signature is worth the friction.
Key takeaways
Email acceptance can form a binding contract under ESIGN and UETA.
The Statute of Frauds requires certain contracts to be in a signed writing — and an email can satisfy both.
Typing your name at the end of a message may count as a signature. Courts have looked at exactly this.
"Subject to contract" in your emails is the cheapest protection available.
Apparent authority means your job title may not save you.
Wills, codicils and testamentary trusts are excluded from ESIGN entirely.
Why an email binds at all
Contract formation needs an offer, acceptance, consideration and intent to be bound. Acceptance can be communicated by any reasonable means unless the offer specifies otherwise, and email has been a reasonable means for a long time.
The ESIGN Act (15 U.S.C. § 7001) and UETA § 7 add that a contract can't be denied legal effect solely because it's electronic. They don't create new contract law — they remove the medium as a defence.
Forcelli v. Gelco Corp. (N.Y. App. Div. 2d Dep't, 2013) is the clean illustration. A claims adjuster emailed settlement terms and ended with her typed name. The court held it a binding settlement under CPLR 2104. The sender did not think she was executing a settlement agreement. She was.
The Statute of Frauds, which most guides skip
Some contracts must be in writing and signed by the party being held to them. The usual categories:
Sale of goods at $500 or more (UCC §2-201)
Contracts that can't be performed within one year
Transfers of real property interests
Promises to answer for another's debt (suretyship)
Agreements in consideration of marriage
Here's the part people get wrong in both directions. The Statute of Frauds doesn't mean these can't be done electronically — UETA and ESIGN say an electronic record satisfies the writing requirement and an electronic signature satisfies the signature requirement. So an email can satisfy the Statute of Frauds, provided it's signed.
Which raises the question of what signing means.
Does your typed name count as a signature?
Sometimes. And the reasoning is instructive.
In St. John's Holdings, LLC v. Two Electronics, LLC (Mass. Land Court, 2016), a real-estate negotiation ran through brokers over text and email. One broker's message set out terms and ended with his first name. The court inferred that he intended to authenticate the message by deliberately typing his name at the end, and observed that the brokers typed names on messages containing material terms but not on informal exchanges — which it read as indicating which communications the parties meant to be bound by.
Two things make this case worth knowing rather than just citing:
First, the distinction it draws is the one that matters to you. Signing off "Tim" on a message with terms, versus not signing off on chat, was treated as evidence of intent. Most people's email habits make no such distinction.
Second, it didn't end well for the party relying on it. After trial the court found the message wasn't signed by the party to be charged and failed the Statute of Frauds, and the appellate court concluded the broker lacked authority to bind the seller anyway. Which demonstrates the real lesson: even when the writing and signature arguments work, authority can still defeat the whole thing — after two years and substantial legal costs.
In the UK, courts have gone further still, finding that an automatically generated email footer containing the sender's name can satisfy a signature requirement. [VERIFY CITATION — Neocleous v Rees [2019] EWHC 2462 (Ch)]
The phrase that prevents all of this
"Subject to contract."
Mark negotiation emails as subject to contract, or state plainly that no binding agreement arises until a formal document is executed by an authorised signatory. This is standard practice in commercial negotiation and it's close to free.
Put it in the body of substantive emails rather than only in a footer, since footers are easy to argue were never read.
If you want the inverse — a reply that is clearly binding — don't send a bare "I agree." Send "I agree to the attached Statement of Work dated 1 March 2026, on behalf of [Company], as [title]." Ambiguity is what creates the litigation, in both directions.
Authority: the issue that actually decides cases
Not everyone can bind a company. But internal job titles are weaker protection than people assume, because apparent authority asks what the other party reasonably believed, not what your org chart says. A manager who has handled vendor relationships for years may bind the company regardless of a signing policy they've never been told about.
Practical measures:
Write down a delegation of authority with thresholds, and tell people theirs.
Where you lack authority, say so explicitly rather than staying silent: "I'll need to route this to our CFO for approval."
Route approvals through a defined workflow so the right person signs in the right order. Common signing workflows covers sequential and approval-then-sign patterns.
Tell counterparties who your authorised signatories are, which undercuts an apparent authority argument later.
What email acceptance can't do
Documents excluded from ESIGN. Wills, codicils and testamentary trusts are carved out at 15 U.S.C. § 7003, along with certain family law matters, court documents, and specified notices such as utility cancellation, foreclosure, eviction and product recall.
Documents needing notarization or witnesses. An email reply satisfies neither. Where your state permits it, remote online notarization handles this properly.
Transactions with their own statutory formalities. Recorded real estate instruments, certain financial instruments, some regulated consumer contracts.
Anything requiring a specific consent process. Where law requires a consumer to receive a record in writing, ESIGN requires their affirmative consent to electronic delivery first.
When to insist on a formal signature
Risk scales with value, duration, and what's buried in the terms. An illustrative threshold — set your own:
Factor | Email may suffice | Use an e-signature |
|---|---|---|
Value | Low, one-off | Material to the business |
Duration | Immediate performance | Ongoing or auto-renewing |
Terms | Simple scope and price | Indemnities, limitation of liability, arbitration, non-compete |
Data | None personal | Personal data involved |
Counterparty | Long relationship, good faith | New, or litigious |
Statute of Frauds | Not engaged | Engaged |
Where it matters, a proper signature binds the signer to a specific document version, which is the gap email can't close. An email thread referencing "our standard terms" leaves open which version, attached when, read by whom. A completion certificate recording signer identity, timestamp, IP and authentication method closes it. How audit trails work sets out what a defensible one contains, and types of electronic signatures covers how signature level affects evidentiary weight — which matters more in the EU under eIDAS than in the US.
Regulated sectors often have consent and record-keeping rules email can't meet. For standard commercial documents, starting from a reviewed template removes the ambiguity before it arises: an MSA, SOW, service agreement or vendor agreement from the template library.
How this plays out
An agency's operations manager receives a vendor proposal by email — price, term, auto-renewal clause — and replies "I agree." No attachment opened, no signature, no approval.
Eighteen months later the agency tries to cancel. The vendor produces the thread and asserts a two-year term with an early termination fee.
The arguments available to the agency are the ones this article has covered: the manager lacked actual authority, the full terms were referenced but never provided, and "I agree" didn't specify what was being agreed to. The vendor's answer is apparent authority and definite terms in the email body.
Nobody can tell you how that resolves, which is the point. It's a fact-specific fight resolved through months of negotiation or litigation, costing both sides more than the disputed amount. Compare the alternative: the proposal routes to the CFO, who signs a specific document version, and the terms agreed are not in dispute because there's a certificate showing exactly what was signed and when.
Illustrative scenario, not a specific matter.
If you think you've already agreed to something
Talk to a lawyer before sending anything else. A follow-up email saying "I didn't mean that to be binding" can read as an acknowledgement that you sent an acceptance, and once a contract has formed you generally cannot withdraw unilaterally. The wording matters, and it's worth thirty minutes of advice.
Preserve the full thread with headers intact, including the attachments as sent. And raise it internally rather than hoping it goes away — your position is strongest while the facts are fresh. [LEGAL REVIEW]
Common mistakes
Replying before opening the attachment. You may be bound to terms you never read.
Assuming your title protects you. Apparent authority doesn't check the org chart.
Bare "I agree." Specify the document, date, capacity and company.
No "subject to contract" on negotiation emails.
Signing off with your name on messages containing terms without considering what that signals.
Missing auto-renewal windows in terms you never fully read.
Letting the only record live in one person's mailbox.
FAQ
Is replying "I agree" to an email legally binding?
It can be, where the email contained a definite offer, you had authority, and your reply communicated assent. ESIGN and UETA remove the medium as a defence. Ambiguity about intent, terms or authority is what makes enforcement uncertain.
What makes an email acceptance enforceable?
Offer with definite terms, unambiguous acceptance, consideration, intent to be bound — and, for contracts within the Statute of Frauds, a signed writing. An email can satisfy that last requirement.
Does my typed name count as a signature?
It may. Courts have treated a deliberately typed name as authentication, particularly where the sender typed it on substantive messages and omitted it from informal ones. Don't rely on its absence to protect you.
How do I stop emails becoming binding?
Mark negotiation correspondence "subject to contract" and state that no agreement arises until a formal document is executed by an authorised signatory. Put it in the body, not just a footer.
Can I be bound by an email I didn't send?
Possibly, where the sender had actual or apparent authority. This is why delegation policies and named signatories matter.
What should I do if I agreed by accident?
Speak to counsel before sending any correction. A retraction can be read as an admission, and a formed contract generally can't be withdrawn unilaterally.
Which contracts can't be formed by email?
Wills, codicils and testamentary trusts are excluded from ESIGN, along with certain family law and court documents and specified notices. Anything requiring notarization or witnesses needs a different process.
Does an e-signature carry more weight than an email reply?
Both are legally recognised. The e-signature produces better evidence: explicit consent, identity verification, and binding to a specific document version. The advantage is evidentiary, not a difference in legal status.
