1) What a demand letter is (and what it is not)
A demand letter is a written, extrajudicial notice asking another party to comply with an obligation—most commonly pay a debt, deliver something, perform a contractual undertaking, stop a harmful act, or vacate a property. In Philippine practice, it often serves three overlapping purposes:
- Notice and opportunity to comply (settlement / good faith).
- Triggering legal effects (e.g., putting the debtor in delay or “default” in certain situations).
- Creating evidence (proof that a demand was made and received).
A demand letter is not the same as:
- Court summons or a pleading;
- Formal service of court processes under the Rules of Court; or
- A guaranteed “requirement” in every case (sometimes it is required, sometimes not).
2) Is it legally “proper” to send a demand letter via messaging apps?
The short legal answer
Yes—generally, it is proper and legally defensible to send a demand letter through messaging apps (e.g., SMS, Facebook Messenger, Viber, WhatsApp, Telegram), as an extrajudicial demand/notice, provided you do it lawfully, ethically, and in a way that you can later prove authenticity and receipt.
Why it’s generally acceptable
Philippine law recognizes that “writing” and “documents” can exist in electronic form, and Philippine procedure recognizes electronic evidence, subject to authentication and reliability. A message can qualify as a written communication for purposes like notice and extrajudicial demand—but the practical question is evidentiary: can you prove (a) who sent it, (b) who received it, (c) what exactly was sent, and (d) when.
So the “propriety” of using messaging apps is less about permission and more about risk management and proof.
3) When a demand matters legally
A) Putting the debtor in default (delay)
Under Philippine civil law concepts, a debtor generally incurs delay when there is a demand by the creditor—judicial or extrajudicial—unless the obligation falls under recognized exceptions (e.g., time is of the essence, demand is waived, the obligation states no demand is needed, performance is impossible through the debtor’s fault, etc.).
Practical takeaway: If you want to claim delay-related consequences (like certain damages or interest in some contexts), sending a provable demand helps.
B) Accrual of interest, penalties, and damages
Contracts often provide that interest/penalties begin to run upon demand or upon default. If your contract says “upon demand,” then your messaging-app demand can be useful—again, if provable.
C) Interrupting prescription (limitation periods)
Philippine civil law recognizes that written extrajudicial demand can interrupt prescription in many civil actions. A messaging-app demand may qualify as “written,” but in real disputes, the fight becomes: Was it received? Was it authentic? What was the content?
Practical takeaway: If you are near a deadline, do not rely on messaging alone—use multiple channels that generate stronger proof.
D) Statutory or rule-based prerequisites
Some cases or procedures effectively expect or require prior demand or notice (examples include certain property-related actions like ejectment where demand to vacate is central, and some streamlined procedures where proof of demand is commonly submitted). In these cases, messaging-app demand can help—but only if it meets the evidentiary burden and the specific requirement (e.g., the right person, right address/account, clear ultimatum, reasonable time, etc.).
4) Messaging apps vs. “service of process”: don’t confuse them
A demand letter is an extrajudicial communication. It does not have to comply with the strict formalities of court service rules—unless you are trying to treat it like formal service (which is a different legal category).
That said, once litigation begins, service and notice issues become technical. Messaging apps are not the safest default for formal court service unless allowed by rules, agreement, or court directive in your specific context. For pre-suit demands, you have more flexibility.
5) Evidentiary considerations: admissibility, authentication, and weight
Sending a demand via Messenger/Viber/SMS is easy. Proving it in court is the real work.
A) What you must be able to prove
- Identity/attribution: the account/number belongs to the respondent.
- Authenticity: the message is what you claim it is (not altered/fabricated).
- Integrity: the content has not been tampered with.
- Receipt/reading: ideally that it was delivered/seen (not always required, but very helpful).
- Context: the message clearly functions as a demand, not casual chat.
B) Common proof you can use (practical, Philippine setting)
Screenshots of the full conversation thread showing:
- names/handles,
- profile identifiers,
- phone number/email link (if visible),
- date/time stamps,
- the demand message, and
- subsequent replies (especially acknowledgments).
Screen recordings scrolling from earlier messages to the demand and beyond (to reduce “selective screenshot” attacks).
Exported chat logs (where the platform allows it).
Affidavit testimony from the sender explaining:
- how the account is yours,
- how you know the recipient account is theirs,
- how/when you sent it,
- and attaching the screenshots/exports as annexes.
Corroboration:
- previous transactions where that account was used for payments,
- the same number used in the contract/PO/invoices,
- prior acknowledgments from that account,
- remittance slips referencing that number/account.
C) Typical defenses you should anticipate
- “That account/number isn’t mine.”
- “I lost my phone; someone else used it.”
- “Screenshots can be edited.”
- “I never saw it / it didn’t reach me.”
- “You messaged the wrong person.”
Countermeasure mindset: build a record that ties the account/number to the person through independent evidence (contracts, invoices, prior payments, admissions, or other communications).
D) “Seen” receipts and delivery ticks
“Seen” indicators are helpful, but not perfect. Some platforms allow read receipts to be disabled; some “seen” markers can be ambiguous. Treat them as supportive, not absolute.
6) Risks and legal pitfalls unique to messaging demands
A) Harassment, threats, or coercion
A demand letter should demand performance—not intimidate. If your messages become aggressive, repetitive, or humiliating, you risk:
- potential criminal exposure if language crosses into unlawful threats/extortion-like territory,
- civil claims for damages (in extreme cases),
- and reputational blowback that undermines settlement.
Rule of thumb: Firm + factual + time-bound, never menacing.
B) Defamation / cyberlibel risk
If you accuse someone of fraud, estafa, theft, or “scammer” in a way that is defamatory and not carefully handled, you create defamation/cyberlibel risk—especially if you send it to others or post it.
Safer approach: Describe conduct in neutral terms (“unpaid obligation,” “breach,” “non-payment despite due date”), reserve criminal accusations for counsel-driven strategy, and avoid broadcasting.
C) Data privacy and misdirected messages
If you send sensitive personal or financial details to the wrong number/account, you may create data privacy and liability headaches. Messaging apps also sync across devices; recipients may have shared access.
Minimize sensitive data: include only what’s necessary to identify the obligation, and keep attachments controlled.
D) Unauthorized practice / ethical issues (especially for lawyers)
If you are counsel, you must keep within professional responsibility norms: communicate appropriately, avoid deception, avoid undue pressure, and if you learn the other party is represented, communications should respect representation boundaries.
Even for non-lawyers, impersonation, doxxing, and public shaming tactics can backfire legally.
E) Platform volatility and preservation problems
Accounts get deleted, messages unsent, phones get wiped, and screenshots get challenged. If the dispute is headed to litigation, preserve evidence early.
7) Best practices: how to do it right (Philippine-ready playbook)
A) Use a “belt and suspenders” delivery strategy
Messaging apps are great for speed, but for serious claims, combine channels:
- Messaging app (fast notice + potential admission),
- Email (timestamps, attachments, easier printing),
- Courier/registered mail to last known address (stronger traditional proof),
- Personal service with signed acknowledgment when feasible.
If you can do only two: messaging + email (and keep records).
B) Make the message look like a real demand letter
Even inside a chat, structure matters:
Subject line (yes, in chat): “FINAL DEMAND FOR PAYMENT – [Invoice/Loan]”
Identify parties and transaction:
- date, amount, contract/invoice number, due date
State the breach:
- “Payment remains unpaid despite due date.”
Make a clear demand:
- “Pay ₱___ on or before ___.”
Specify payment instructions (but avoid oversharing sensitive info)
State consequences calmly:
- “If unpaid, we will pursue appropriate legal remedies…”
Offer settlement contact:
- “You may contact ___ to discuss payment arrangements.”
Attach documents (PDF preferred): invoice, SOA, contract excerpt.
C) Give a reasonable deadline
Common practice: 5–15 days depending on urgency and context. Too short can look oppressive; too long delays remedy.
D) Keep tone professional and non-inflammatory
Avoid:
- “Manloloko ka”
- “Ipakukulong kita bukas”
- “Siguraduhin mong…” (threatening language)
- profanity, insults, public tagging
Use:
- “We demand payment…”
- “Kindly settle…”
- “We will be constrained to pursue remedies…”
E) Don’t “spam demand”
Send one well-crafted demand, maybe one follow-up reminder. A barrage of messages looks like harassment and weakens your posture.
F) Preserve evidence immediately
- Screenshot + screen record
- Save attachments
- Back up chat exports
- Keep a folder with filenames including date/time
- If litigation is likely, consider having your evidence packaging done systematically (affidavit + annexes).
8) Messaging-app demand letters in specific common scenarios
A) Loans and informal utang
Messaging demands are common and often effective because borrowers respond—those responses can become admissions.
Key: tie the account/number to the borrower (prior chats about the loan, GCash references, prior acknowledgments).
B) Business receivables (invoices, SOA)
Send a PDF demand letter and SOA via email and messaging. Ask for acknowledgment: “Please confirm receipt.”
C) Landlord-tenant (rent arrears / vacate)
Demand via messaging is useful for speed, but for disputes likely to go to court, also send a written demand through more formal channels to the address, and be careful with statutory/required elements depending on your remedy.
D) Employment-related demands
These are sensitive. Messaging can be misconstrued as intimidation. Prefer formal HR/legal correspondence, keep language neutral, and avoid threats.
9) Practical templates (chat-friendly)
Template 1: Payment demand (polite but firm)
FINAL DEMAND FOR PAYMENT – ₱[amount] ([reference])
Hello [Name]. This is a formal demand regarding your unpaid obligation in the amount of ₱[amount] arising from [loan/invoice/contract] dated [date], due on [due date]. As of today, the amount remains unpaid.
We demand that you pay ₱[amount] on or before [deadline date] through [payment method] and send proof of payment to this account/email.
If payment is not made within the stated period, we will be constrained to pursue the appropriate legal remedies available to us, including the filing of the necessary action, without further notice.
For settlement arrangements, you may contact [name/contact].
Thank you.
Template 2: Demand with installment option
We demand full payment of ₱[amount] on or before [date]. If you are unable to pay in full, kindly propose a written installment schedule within 48 hours for our consideration, otherwise we will proceed with legal action.
Template 3: Acknowledgment request (helps evidence)
Please confirm receipt of this demand message and attached documents by replying “RECEIVED” with the date and time.
10) FAQs
Is a messaging-app demand “valid” if they don’t reply?
It can still be valid as an extrajudicial demand/notice, but proof of receipt becomes harder. Delivery/read indicators, correct account identification, and follow-up via other channels matter.
Can I rely on a screenshot in court?
Screenshots are commonly used, but the opposing party may challenge authenticity. Strengthen them with context (thread), screen recording, exports, and testimony/affidavit explaining how they were obtained.
Should I threaten criminal charges (estafa) in the demand?
Be careful. Overstating criminal liability or using it as leverage can backfire and expose you to counterclaims or complaints if it becomes coercive or defamatory. Stick to facts and state you will pursue “appropriate legal remedies” unless your counsel has a clear basis and carefully worded strategy.
Is messaging better than registered mail?
Messaging is faster and may trigger admissions; registered mail is more traditional and often easier to explain as proof of notice. Best practice is both, especially for high-value or litigation-bound claims.
What if I’m messaging someone abroad or an OFW?
Messaging is often the most reliable immediate channel. Still, preserve proof and consider sending email and a formal letter to the last known address.
11) Bottom line
Sending demand letters via messaging apps in the Philippines is generally proper and usable, and in many real-world disputes it is practically effective. The decisive issues are:
- Proof (identity, authenticity, receipt),
- Tone and legality (avoid threats, harassment, defamatory accusations),
- Privacy and accuracy (send to the right account, limit sensitive data), and
- Redundancy (use messaging as a channel, not your only channel, when stakes are high).
If you tell me what kind of demand you mean (unpaid loan, invoice, rent arrears, vacate, damages, breach of contract), I can draft a version optimized for messaging plus a companion formal letter style—with wording that preserves your leverage while minimizing legal risk.