A useful LitBuy support request identifies one problem, the record it concerns and the outcome you need. “Please help with my order” leaves more unanswered than a message describing an incorrect option, a particular parcel event or a login error.
Start with the relevant record and use a verified contact route. Do not put your full account history into a public community post in the hope that someone will recognise the issue.
Identify the support channel
The LitBuy Google Play listing checked in September 2026 names support@litbuy.com as its support email. Recheck current contact details through your established platform access or application listing before sending case information. Distinguish customer support from business enquiries or developer contact details.
A phone number displayed near a company's information does not automatically establish a customer-service hotline or WhatsApp service. Do not treat an unsolicited message, familiar avatar or copied logo as proof that a person represents support.
Include the detail that changes the next action
| Issue | Useful information to provide privately |
|---|---|
| Wrong product option | Selected option, what the record or photo shows and the discrepancy |
| Missing measurement | The exact dimension and measurement method needed |
| Parcel status question | Relevant reference, latest event and its date |
| Different quoted amount | Earlier and current scope, inputs and the fee being questioned |
| Account access | Error wording, device or app version and the stage that fails |
Use the QC guide, tracking guide and login guide to narrow the issue before writing. A clear question is easier to answer than a collection of unrelated screenshots.
For an amount or transaction-status question, the payment methods guide helps separate the selected basket, currency, promotion and existing payment attempt.
A message structure you can adapt
State what you tried, what happened instead and what you need clarified. Then attach the smallest relevant supporting record through the appropriate private channel.
For a garment measurement question, explain that the visible width does not identify its endpoints and ask whether it was measured flat between the points you need. Do not describe it as a confirmed sizing defect unless that is what the information establishes.
If you are still choosing rather than asking about a placed order, use a specific product to frame the question. For example, open the ribbed crewneck sweater on OG, identify your intended option and ask for the particular measurement you cannot determine. This is a product reference, not a support channel or a reason to buy again while an earlier order remains unresolved.
For a shipping charge question, identify the input or line item that differs. Ask for its calculation or scope rather than assuming a refund is already due. The shipping calculator guide helps organise those inputs.
Keep the conversation consistent
Retain the reply and case reference if one is supplied. When following up, add the new information and identify the question still unanswered. Avoid submitting several incompatible descriptions of the same event.
Do not invent a deadline from another shopper's reply time. Read the response and any timing information provided for your case. An acknowledgement is not the same as an approved return, completed refund or confirmed delivery.
Protect information without hiding the problem
Keep passwords, verification codes and full payment-card information out of support messages. For public discussion, also remove names, email addresses, order references, tracking labels and readable identifying codes. A private support channel may need a relevant order reference; a public screenshot does not.
If you are asked to install an application, use the app identity guide to check its source. An unknown APK or remote-access request is not a necessary conclusion from an ordinary order question.
Verify a WhatsApp number before using it
Treat a claimed LitBuy WhatsApp contact as unverified until it matches contact information obtained through the platform's own support route. Do not send login codes, passwords or full payment details to a number copied from a community post. If the contact cannot be confirmed, use the support channel you can verify instead.
Keep returns and shipping instructions separate
For a return enquiry, establish the applicable process, eligibility and receiving instructions before sending an item. Do not reuse a company address or another customer's label. The warehouse guide distinguishes receiving arrangements from general contact information.
Once the question is resolved, return to the correct stage of the buying guide. A support exchange should clarify the existing purchase, not push you into placing a duplicate order or buying something unrelated.