Skip to content
English
  • There are no suggestions because the search field is empty.

Report a bug or give feedback

From any Lymera screen you can report a problem, request a new feature or share your opinion about the product. Your message reaches the Lymera team as a support ticket and you will receive follow-up by email. Any signed-in user can use it, regardless of role.

# Report a bug or give feedback

📘 What it is

From any Lymera screen you can report a problem, request a new feature or share your opinion about the product. Your message reaches the Lymera team as a support ticket and you will receive follow-up by email. Any signed-in user can use it, regardless of role.

📍 Where to find it

In the top bar of the Dashboard screens you'll see the link with a bug icon, Report a Bug or Give Feedback (on small screens only the icon is visible). It opens the page "Report a Bug, Request a Feature or Give Feedback".

🛠️ How to do it

  1. Click Report a Bug or Give Feedback in the top bar.
  2. You'll see Email and Company name already filled in (they can't be edited).
  3. Complete the fields:

- **Ticket name \: a short title, for example "The phone magnifier doesn't work". - Category \: Product issue, Billing issue, Feature request, Product feedback or General inquiry. - Impact (optional): from P0 (critical) to P4 (I would love it but I can live without it). P1 is "I have no workaround but I can wait"; P2, "I have a workaround"; P3, "It does not exist and it affects my productivity". - Describe the problem or request \: what happened, what you expected to happen and the steps to reproduce it. - Which Lymera module is involved or affected? (optional): for example CRM, Prospecting, WhatsApp. - Affected campaign and Link to the affected lead* (optional): they appear only when the category reports a failure, not for Feature request or Product feedback. The link must start with http:// or https://.

  1. Click Send report. The button is enabled when the ticket name, the category and the description are filled in.
  2. You'll see "Report sent!" with a note that they will look into it shortly and, for urgent cases, the email address you can write to directly.

Tips for a good report: include the URL of the screen, which company you had active, the approximate time, the exact steps and what you expected. If you have a screenshot, you can send it when they contact you by email.

❓ Frequently asked questions

How is my report prioritized? According to the impact you indicated and your Lymera plan. The support team reviews it and follows up with you by email.

Can I attach a screenshot? The form has no attachment field. When you receive the reply by email, you can respond with the screenshot.

I can't see the report button. It's in the Dashboard top bar. On small screens only the bug icon appears. If you use a content blocker, try turning it off for Lymera.

The Send report button doesn't become enabled. The ticket name, the category or the description is missing. Check that all three have content.

I get "Error sending. Try again." or "Network error. Check your connection and try again." Check your connection and send it again. If it persists, write to the support email shown in the confirmation or escalate with the information below.

Is this the same as contacting my Customer Success Manager? No. For contract, plan, quote or payment matters, talk to your CSM; the form is for product failures, feature requests and comments.

Will I see my report inside Lymera? No: follow-up arrives by email.

🔧 If something doesn't work

SymptomCommon causeWhat to check
Sending fails with a network errorUnstable connection or content blockerRetry; try another browser or network
Sending fails repeatedlyTemporary failure of the ticketing serviceWait a few minutes and send again
What you wrote was lostThe session expiredSign in again; copy the text before sending
Follow-up email doesn't arriveSpam or a different emailCheck spam and the email in your profile

When to escalate to a person: if the form doesn't send after several attempts. Gather the details for the team: company, user email, category and impact, URL where the problem occurs, time, steps to reproduce it and a screenshot.