Support requests: explain the issue without oversharing
appu.lviv.ua editorial team · 22 October 2026
A concise description with a timestamp and transaction reference helps more than repeated messages. Separate observations from assumptions.
Describe expected and actual behaviour
State what you did, what the rules led you to expect and what the interface actually showed. Add the page address, language, browser and time. Quote any error text accurately. Do not present a suspected cause as an established fact.
Keep one case reference
Ask for a case number and retain the conversation. Add new details to that case. If another team takes over, ask about the next step and response channel. Never post identity documents in public comments.
Document an unresolved issue
Summarise the timeline, previous answers and the specific remedy requested. Keep the relevant rule version. Where appropriate, use a verified channel of the competent authority for a formal complaint. Do not give credentials to a paid intermediary promising an easy resolution.
Keep a coherent support timeline
Frame a request as the difference between expectation and observation. State the action taken, the relevant rule and the system’s actual response. Include the necessary technical details and reference. Ask for a case number and the next step if another team takes over. Send later information in the same conversation. Parallel messages can fragment the context and produce answers to different parts of the problem. Retain the final explanation. If it misses a specific question, identify that omission rather than repeating everything unchanged. This makes it clearer which circumstances have been checked and which evidence is still required.
History and reference numbers
When a result is unclear, start with the ledger rather than a theory about its cause. Keep the round or request reference, exact time, currency and visible status. Arrange multiple entries in order: a debit, completion and credit may appear separately. A screenshot supplements this timeline but does not replace an identifier. Avoid posting account details or full payment credentials publicly. Submit evidence through verified support and request a case number. Add later details to the same case. This gives the reviewer a sequence rather than disconnected messages and lets you compare each response with earlier explanations.
Keep useful evidence without oversharing
Investigating a transaction requires its identifying details, not access to all your banking. Keep the original receipt separately and prepare a correspondence copy with the date, amount, currency and reference. Remove unrelated purchases and unnecessary personal information where the verification procedure permits. Never include a password, security code or one-time authentication code. Ask why an additional document is needed before submitting it. A screenshot may lack the necessary identifier, so clarify which record enables tracking. Extra disclosure does not automatically speed up review. Keep the submission time and channel to establish which evidence the reviewer already received.