Short answer
Keep both accurately described with dates and requested remedies. Do not downgrade a demand or ignore a complaint because it arrived through ordinary support; a professional can explain reporting requirements.
An illustrative example
A support message asks for compensation and alleges loss.
This is a hypothetical situation, not a real customer outcome or a coverage determination.
Three facts to prepare
- Message date
- Exact remedy sought
- Escalation status
Use a brief, accurate summary. Separate confirmed facts from assumptions; keep passwords, identity numbers, private customer records and confidential documents out of an initial marketplace request.
A question to bring to the right professional
What does the wording require for this type of communication?
Use your incident process and applicable insurer or professional contacts for time-sensitive matters. Record confirmed facts, allegations and unknowns separately. Do not use a LunarQuote profile as claim notice, make a promised coverage determination or publish sensitive evidence while seeking help.
Sources and scope
- NAIC: cybersecurity and insurance
General commercial cyber context; the NAIC describes cyber policies as customized. This source does not decide coverage for an AI scenario.
- Travelers: technology errors and omissions risk examples
Insurer-authored context on technology service allegations and differences in policy wording. Product descriptions apply to that source; they are not LunarQuote offers or evidence of a partnership.
Sources supply the stated background, not a determination about the illustrative case. The example, checklist and discussion prompt are LunarQuote educational material. Source links checked October 5, 2026.
Your next step
Organize high-level concerns in a private profile. A specialist connection depends on verified availability and your consent; matching may be temporarily unavailable. A profile is not a quote, claim report or promise of coverage.
Create a business risk profile →