Prompting Guide: How to Get the Best Results from Aiventic
Learn how to ask Aiventic the right questions to get faster, more accurate repair guidance. Real examples from the field included.
Prompting Guide: How to Get the Best Results from Aiventic
Aiventic is built to help you troubleshoot, diagnose, and repair — but like any tool, how you use it matters. The better you ask, the better the answer.
This guide covers how to write (or speak) prompts that get you accurate, actionable guidance on every service call. Whether you're typing on your phone or talking hands-free while you're under a unit, these tips will save you time.
The Golden Rule: Give Context
The single biggest difference between a good prompt and a bad one is context. Aiventic can help with almost any repair scenario, but it needs to know what you're working on.
Every prompt should include:
- Brand — Who made the unit?
- Model number — Which specific unit is it?
- Serial number (when available) — Helps narrow down production runs, known issues, and part compatibility
- What's happening — The symptom, what the homeowner reported, or what you're seeing on-site
Think of it like calling a senior tech for advice. You wouldn't just say "the fridge is broken" — you'd tell them the brand, model, and what it's doing. Same idea here.
Real Examples from the Field
Here are real prompts from technicians using Aiventic, and why they work.
Example 1: Scotsman SCN60 — No Power Lights
The situation: Water pooling in the bottom, unit is running but no power lights are on.
The prompt:
"I'm working on a Scotsman SCN60. The homeowner states that there's water in the bottom and that the unit is running but no lights are on. Can you write me a guide on how to troubleshoot?"
Why this works:
- Brand and model are up front (Scotsman SCN60)
- Two distinct symptoms described (water in bottom + no power lights despite running)
- Clear ask — they want a troubleshooting guide, not just a guess
- Includes homeowner context — this is what was reported, not just what the tech sees
Example 2: Sub-Zero 680 — Leaking
The situation: Unit leaking from inside out, homeowner requesting periodic maintenance and a general check.
The prompt:
"I'm working on a Sub-Zero Model 680. The homeowner states that it's leaking from the inside out. Can you provide me a step-by-step guide on how to troubleshoot?"
Why this works:
- Brand and model clearly stated
- Specific symptom with directionality ("leaking from the inside out" — not just "leaking")
- Asks for step-by-step format, which gets structured output
Example 3: Scotsman DCE33 — Slow Ice Production
The prompt:
"Working on a Scotsman DCE33. Homeowner states it's taking too long to make ice. Can you help me triage?"
Why this works:
- Concise but complete — brand, model, symptom
- Uses "triage" which tells Aiventic you want diagnostic steps, not a full repair guide
- Gets straight to the point — no filler
Good Prompts vs. Weak Prompts
Here's the difference context makes:
Diagnosing a Problem
Weak: "Fridge isn't cooling"
Better: "Working on a Sub-Zero BI-36U, serial 4612XXX. Compressor is running but the unit isn't cooling. Evaporator fan seems to be working. What should I check next?"
The weak prompt could apply to any fridge ever made. The better prompt gives Aiventic the brand, model, serial, what's working, and what's not — so it can skip the obvious steps and get you to the real issue.
Identifying a Part
Weak: "What's this part?"
Better: "I'm looking at a component on a Wolf DO30 double oven — it's a round ceramic piece behind the burner assembly, about 2 inches across. What is it and what's the part number?"
Aiventic can identify parts, but it needs enough detail to narrow it down. Brand, model, location in the unit, and a physical description go a long way.
Getting Repair Steps
Weak: "How do I fix the ice maker?"
Better: "I need to replace the water inlet valve on a Sub-Zero BI-48SD. Can you walk me through the steps?"
When you already know what needs to be replaced, say so. Aiventic will skip the diagnostic and give you the repair procedure.
Triage vs. Full Repair Guide
You can steer the depth of Aiventic's response based on what you ask for:
- "Help me triage" — Gets you a quick diagnostic flow to narrow down the issue
- "Give me a troubleshooting guide" — Gets you a comprehensive step-by-step
- "Walk me through the repair" — Gets you the actual fix procedure
- "What parts do I need?" — Gets you a parts list with numbers
Use the right ask for where you are in the job.
Tips for Voice Prompts
When you're talking to Aiventic hands-free, keep these in mind:
Spell out model numbers clearly. "Sub-Zero B-I-4-8-S-D" is better than rushing through "SubZero BI48SD" — speech-to-text can fumble alphanumeric model numbers.
Pause between the details. Give it: brand... model... then the symptom. A natural pause helps speech-to-text parse the pieces correctly.
Don't worry about perfect grammar. Aiventic understands natural language. "Scotsman DCE33, homeowner says ice is slow" works fine. You don't need to write a sentence.
Describe what you see. If you're looking at something you can't identify, describe it physically — shape, size, color, location in the unit. "There's a black rectangular relay near the compressor, about 3 inches long" gives Aiventic enough to work with.
The Prompt Formula
When in doubt, use this structure:
"I'm working on a [Brand] [Model]. [What's happening / what the homeowner reported]. Can you [what you need — triage / troubleshooting guide / repair steps / parts list]?"
That's it. Brand, model, symptom, ask. Four pieces of information, and Aiventic handles the rest.
Common Mistakes to Avoid
Being too vague. "It's not working" could mean a hundred things. Describe what "not working" actually looks like — no power? Running but not cooling? Making noise? Leaking?
Skipping the model number. A Sub-Zero 650 and a Sub-Zero 680 are different units with different components. The model number changes everything.
Asking multiple unrelated questions at once. "Troubleshoot the leak AND tell me how to do periodic maintenance AND check for other issues" is three separate jobs. Ask them one at a time for better results.
Assuming Aiventic knows what you already tried. If you've already checked the compressor and the evaporator fan, say so. Aiventic will skip those steps and move to the next diagnostic.
Start Using These Today
The best way to get comfortable with Aiventic is to use it on your next call. Start with the formula — brand, model, symptom, ask — and you'll get solid results from day one.
The more context you give, the less time you spend going back and forth. And the less time you spend troubleshooting, the more jobs you finish.
About Justin Tannenbaum
Justin Tannenbaum is a field service expert contributing insights on AI-powered service management and industry best practices.



