Root > Introduction > Support


Previous pageReturn to chapter overviewNext page   

All EurekaLog versions are covered by full and unlimited support.




There are several ways to contact EurekaLog's team:


support sending form:
using our support system directly



What to write?

It is very important part, as it may greatly speed up/slow down processing of your request. First, simple rules about choosing options for your ticket (if you use support sending form): select appropriate category for your request.


If you have question about prices, warranty, licenses, upgrades, your registered previous account/e-mail, etc, etc - you should place it to "Sales" category.
If you have question about EurekaLog usage, how to do XXX, does it support YYY, problems, bugs, etc, etc - you should place it to "Support" category.
If you think that you have found a bug in EurekaLog - you should place it to "Bug Reports" category.
If you have some idea on how we can improve EurekaLog - you should place it to "Feedback" category.
Place your question in "General" category only if it is really a general question. Like "Are there any plans for EurekaLog for PocketPC"? In other case, your ticket will be redirected to other category, and you just lose your time waiting.


Other important part is the message itself.


PLEASE, specify your versions and editions of EurekaLog, IDE and Windows. BTW, it is good idea to reinstall EurekaLog, using the latest available RC version. That's because your issue may be already fixed. You may also send a request and check a new version while request is processed.


Of course, your message should be quite clear about what you want us to do.


Other piece is demo or steps to reproduce. Many of our clients think: "gosh, it is so simple, just do XXX and you'll see what I mean". Except when we do this on our machines - nothing happens. That's because client uses some option or event handler. So it is a good idea to reproduce your issue in just empty VCL application with one TButton and "raise Exception.Create('Test');" in its OnClick. If you try to do that, you may often unable to get test application behave like desired. And if you look deeper - you may notice differences between test application and your application (options, events, etc), that caused your issue. That way you'll be able to solve it by yourself (BTW, we recommend to use import/export buttons to transfer your EurekaLog's settings between projects). Doing a little work before sending question can save you days of conversation.


Of course, there can be cases, when you're unable to reproduce your issue in new application. In that case just mention it: "I wasn't able to reproduce it in a test project" and don't forget to attach your project's settings, screenshots, etc - anything, that can give a hint.


Hint: instead of screenshooting every page of your EurekaLog's options, you may just export your settings to .eof file and send it to us (there is "Export" button in EurekaLog's options dialog).


Well, it is totally fine to state your requests as "I've assigned exception event, but it is not getting called. What am I doing wrong?", but be prepared to long conversation in that case.



Using native languages?

If you don't speak English, then you can write in your native language. EurekaLog staff will use some translator to translate your request and answers to appropriate language. But it is not recommended. If you only know English a little, you may say your request as you can in English and repeat it on your native language. That's because it's hard to understand machine translations. So if your request was short-formulated and was badly translated by auto-translator - we'll simply not understand you. So attaching your request in bad, but still "human-produced" English may greatly help.


Some of you may write in native language even if you're capable of speaking English - if you know, that someone from EurekaLog team speaks on that language too. Well, this is still a not so good idea. As your request may be answered by different people, and sometimes we discuss certain issues together, so it is good to keep conversation in English, so everyone can read it (without need to use machine translator).


So there can be cases of some misunderstanding. If you think that somebody don't get your actual request - please, try to explain in other words or in more details.



I'm not getting any response?

Unfortunately, sometimes this happens. Really, we may miss your reply and so your thread may be forgotten, but we can assure you, that this is really a rare case. In most other cases there is lost e-mail or similar case. If you have not received expected reply in reasonable amount of time (say, a week) - send your message again!


If you use e-mails, then there can be chances that reply was marked as spam or was rejected due to suspicious attachment. Please, check you trash/spam folder (or similar) in your e-mail client. Do not hesitate to send reply again, if you suspect that your reply can be lost.


Please note, that we use GMail for delivering e-mails, so be sure that your messages do not contain illegal attachments (you can  rename files or pack them into 7z-archive).


If you use our support system (note, that your e-mails are redirected to our support system too) - then it is the best case, as you can check status of your request in any time. First, note, that every time your request is registered, you should get automatic response like this:


Thank you for contacting us. This is an automated response sent to you in order to confirm the receipt of your message. We will attend to your ticket as soon as possible. We've listed the details of the ticket you created below for your records. When replying, please keep the ticket's ID in the subject to ensure that your replies are tracked correctly.


Ticket ID: your-ticket-ID-here

Subject: your-subject-here

Department: Delphi-Support

Priority: Low

Status: Open


You can check the status of or reply to this ticket online at:

Please use the following credentials when accessing your account with us:


Email: your-e-mail-here

Password: your-password-here


If you don't receive this reply (and it is not in your "spam" folder) in few hours - resend your request immediately! You may also try to use different contact method.


So, if you didn't receive any reply for long period of time - you can check the entire history at Just enter your e-mail and password, which were provided in automatic reply. You'll see all your and staff replies, so you can check if all replies were delivered correctly.


If you think there is a problem with delivering on our side - do not hesitate to make complaints.

Send feedback... Build date: 2023-09-11
Last edited: 2023-03-07
The documentation team uses the feedback submitted to improve the EurekaLog documentation. We do not use your e-mail address for any other purpose. We will remove your e-mail address from our system after the issue you are reporting has been resolved. While we are working to resolve this issue, we may send you an e-mail message to request more information about your feedback. After the issues have been addressed, we may send you an email message to let you know that your feedback has been addressed.

Permanent link to this article: