Your first answer
A short quick start for operators: scan the machine's QR code, sign in once, and get one cited answer from Edmund — by tapping a suggestion, typing, speaking, or attaching a photo of the fault.
Each machine or line is one project in Edmund, and most machines carry a printed QR code. Scanning that code opens the right project straight away, so Edmund already knows which machine you’re asking about. You only need to sign in the first time — your account is set up for you before you start.
Get to an answer
Scan the machine’s code. Point your phone camera at the QR code on the machine. It opens that machine’s project directly, so you don’t have to find it in a list.
Sign in once. If you’re asked to sign in, use the login your administrator set up for you. After the first time, your phone usually stays signed in.
Confirm the project. Edmund opens the machine the code pointed to. Check the name matches the machine in front of you before you ask. (If you open Chat without scanning, Edmund asks you to pick the project first.)
Ask your question. If you’re not sure how to start, tap one of the Suggestions — ready-made starter prompts shown in the chat. Otherwise tap the input that reads Type your message for Edmund here (Napište zde svou zprávu pro Edmunda) and type it, use the microphone to speak it, or use the paperclip to attach a photo of the fault.
The chat input — paperclip for a photo, lightbulb for suggestions, microphone to speak, arrow to send. Read the answer. Edmund replies using that machine’s own knowledge. You can watch which source it searches, and a document or journal answer links each part back to its Source so you can check it. Keep asking in the same chat to go deeper.
A cited answer: the agent searches a real source and each claim carries a Source link. Rate it. Use the thumbs up or thumbs down on the answer — that signal drives the feedback loop that makes the next answer better.
If your first answer is thin, or Edmund says it doesn’t have that, the machine just doesn’t have enough loaded yet — it isn’t a mistake on your part. Tell whoever looks after that machine’s knowledge (the expert), and it gets better the next time you ask.
What makes a good question
In short: name the symptom, the machine state, and any fault code exactly as the panel shows it — and keep one problem to one chat. The full guidance, with a good and a bad example, is in Asking good questions.