Support and disputes
Support, reports, and marketplace resolution
Limowo needs a clear support path for account, listing, payment, seller, agent/API, safety, and dispute questions before broader production promotion.
Last updated: 1 July 2026
Contact LimowoSupport
support@limowo.com
Scope
Account, listings, messages, sellers
Launch gate
Response times, escalation, appeals
When to contact support
Contact Limowo for account access, verification, listings, messages, seller profiles, billing, safety reports, security reports, or agent/API integration questions.
- Use account, listing, message, order, seller, or command references where available.
- Explain the timeline, what happened, and the outcome you need.
- Do not send passwords, authentication tokens, full payment data, or sensitive identity documents by email.
Marketplace disputes
Limowo can review reports, messages, listings, moderation evidence, seller references, and relevant account signals. Unless a specific checkout or order flow states otherwise, users remain responsible for private agreements, pickup or delivery, item condition, and payments.
Reports and evidence
Useful reports include the affected listing, user, message, order, seller, request, or command ID, a short timeline, screenshots where safe, and the specific policy or product behavior that looks wrong.
Moderation and appeals
Listing, message, seller, agent/API, or account restrictions should be reviewable with evidence. Final appeal windows, escalation contacts, response times, and decision authority remain launch-gate operations requirements.
Account and seller support
Optional paid tools, invoices, receipts, and billing corrections should have dedicated workflows before paid features are promoted broadly.
Agent and API support
Technical support for public agent/API features should include request IDs, command IDs, client metadata, expected behavior, and observed errors. Never send API keys, session tokens, or secrets in ordinary email.

