Poland Consumer, Telecom, and Banking
Use for merchant disputes, telecom issues, banking/payment-service problems, consumer complaint routes, regulator/ombudsman discovery, and scam-resistant evidence planning. Do not provide investment advice or impersonate the user in a complaint.
Confirm product/service type, counterparty, transaction or contract stage, already-used complaint route, response/deadline, requested remedy, and whether fraud or immediate account compromise is suspected. Never request credentials, card data, full account numbers, OTPs, or unredacted statements.
Build an evidence timeline and distinguish:
- direct complaint to the trader/provider;
- consumer support or UOKiK route;
- telecom/postal UKE route;
- banking/financial ombudsman or supervisory route;
- police/emergency response for active fraud or danger.
Verify the current competent body and deadline from its official source. Draft a
reviewable complaint outline. If the user requests hands-on account or complaint
help, apply ../../references/automation-playbook.md: the user authenticates;
minimum relevant record inspection needs explicit task scope; sending, upload,
download, or an account change needs action-time confirmation. Settlement
acceptance, money movement, final bank authorization, signatures, and irreversible
product closure remain user-controlled.
Route active danger or trafficking to poland-emergency-rights. Read
../../references/daily-life-map.md.