Short answer: Avast false positive forms, Business Hub quarantine dialogs, and community forum reply boxes are all plain text fields. Click Description or the message body, press ⌃+⌥+R (Mac) or Ctrl+Alt+R (Windows/Linux), speak file path, detection name, and business impact, press again. AICHE inserts text. Avast still runs scans; AICHE does not change exclusions or protection settings.
The Problem
Avast's most useful interactions all live behind a free-text box. The false positive form at avast.com/submit-a-sample has one Description field. The community at community.avast.com rewards long, technical posts in "Viruses and worms." Business Hub's Send for analysis dialog has an optional context box that admins almost always leave blank because typing it out takes too long.
The result is predictable. Thin submissions sit in the queue. "Avast keeps flagging my installer" gets the same treatment as 400 other vague reports that week. Detailed reports with the file path, what it does, the signing cert, and when the detection started skip ahead because Threat Labs has enough to work with.
The bottleneck is the keyboard, not the knowledge. You already know why the file is clean. Writing it down is the part that hurts.
What Changes
Speak the context instead. Click into Avast's Description field, press the hotkey, talk through the file's origin, purpose, signing details, and impact. AICHE transcribes, removes the "um"s and false starts, and inserts the cleaned text where the cursor was.
Speaking runs around 150 WPM. Typing runs around 40 WPM. The 200-word technical justification you skipped writing because it would take five minutes lands in 80 seconds.
How It Works
- Open the surface you need:
avast.com/false-positive-file-form.php, a community forum reply, or the Business HubProtection > Quarantinedialog. - Click into the Description or message text field.
- Press ⌃+⌥+R on Mac or Ctrl+Alt+R on Windows/Linux to start recording.
- Speak the full context. File path, what the file does, when the detection started, the Avast component that flagged it (File Shield, Behavior Shield, CyberCapture, Web Guard), why you believe it's clean.
- Press the hotkey again. AICHE transcribes and inserts the formatted text.
- Attach the file (under 50 MB) or paste the detection ID, then submit.
False Positive Submissions That Skip the Queue
The submission form at avast.com/submit-a-sample is short by design: email, file or URL, detection name, alert ID, and one description box. The description box is where the decision gets made. Threat Labs analysts triage by signal, and signal lives in details like "signed with our company code-signing certificate, SHA-256 on the cert is...", "in production on 50 endpoints since 2024", "detection started after streaming update on May 14", or "Behavior Shield flagged the install.ps1 step that registers the service."
That kind of paragraph is tedious to type while you're also coordinating an internal Slack about blocked deploys. Speaking it takes 30 to 60 seconds.
The same applies to Business Hub's quarantine workflow. In Protection > Quarantine, when you select a file and choose Send for analysis with the "False positive" flag, there's a contextual details dialog. Admins routinely leave it empty. Dictating two sentences about why it's a false positive, what business process it supports, and whether you've already added a path exclusion changes the turnaround on a Threat Labs review.
Community Forum Posts
The "Viruses and worms" category on community.avast.com carries 36,000+ topics, and the useful ones are long. Detection name, Avast version, OS, what was running, what changed before the alert, screenshots of the popup, links to VirusTotal results, and a clear question at the end.
That structure is easy to speak and hard to type cold. Click into the reply box, press the hotkey, walk through it the way you'd explain it to another sysadmin. AICHE returns clean prose. Pop in your screenshots and post. If you want the result more structured, enable Message Ready in AICHE settings so the output comes back with paragraph breaks and proper punctuation instead of one stream-of-consciousness block.
Avast Business Hub Admin Notes
The Business Hub console is heavy on text fields that get ignored. Policy descriptions. Exclusion rationale ("why is this path whitelisted on the finance VLAN"). Network Discovery device labels. Web Control category overrides. Patch deployment notes for the change-management log.
These fields matter at audit time. The auditor asks why C:\DevOps\deploy.ps1 is excluded across the production OU and the answer needs to exist somewhere other than your memory from eight months ago. Dictating one-sentence justifications into every exclusion as you create it is the difference between a clean SOC 2 walkthrough and a week of forensic spelunking.
Same workflow for the email-to-Business-Support flow when a sample is over the 50 MB cap. You email the detection ID with an explanation. Dictate the explanation.
Speaking File Paths and Detection IDs
AICHE transcribes literally, so paths and IDs need a small habit shift. For Windows paths, say "C colon backslash" and AICHE writes C:\. For detection names, slow down on the dashes and capitalization ("Win three two colon Malware dash gen"). For SHA-256 hashes and long alert IDs, type those rather than dictating - it's faster and avoids transcription errors on hex strings.
Turn on the Custom Vocabulary feature and add your common terms: your company name, the names of internal scripts and services, the path prefixes you use most, and your Avast Business subscription tier. Spelled correctly every time, no post-edit.
Common Questions
Q: Does AICHE work inside the desktop Avast app?
A: The desktop Avast One and Premium Security apps have very few free-text fields. Most user-facing text input lives in the web surfaces: the submission form, the support portal, the community forum, and Business Hub. AICHE works in any of those because it inserts into whichever text field has the cursor.
Q: Can I dictate into the Business Hub console on Linux?
A: Yes. Business Hub runs in the browser, and the AICHE Linux client uses Ctrl+Alt+R to trigger recording and inserts via the standard X or Wayland event path. Same workflow as on Mac or Windows.
Q: I'm reporting a false positive on a PowerShell script. Will AICHE mangle the code if I dictate it?
A: Don't dictate code. Paste the script content into the form or attach the file. Dictate the surrounding explanation - what the script does, why it's safe, where it runs. AICHE is built for prose and prompts, not literal code transcription.
Q: My audio gets cut off if my dog barks halfway through the report. What happens?
A: Recording is toggle-based, not push-to-talk. Press the hotkey to start, do whatever you need (handle the dog, take a sip of coffee, glance at logs), then keep talking. Press the hotkey again when finished. Nothing about the recording forces a continuous take.
Q: We're a SOC team. Can multiple analysts use this without leaking samples to a third party?
A: AICHE handles the speech-to-text layer only. It does not see Avast's submission form contents beyond the transcription it just inserted. Audio is discarded immediately after processing, within 1 second. For SOC-grade handling, review the privacy page before standardizing on it across the team.
Q: Does this work for the legacy Avast Business CloudCare console as well as the new Business Hub?
A: Yes. Both are web-based, both have text fields, AICHE inserts into either.
Q: I work in German but have to submit to Avast in English. Anything for that?
A: Turn on Auto-translation in AICHE settings. Speak in German, AICHE returns English text. Useful for European admins filing into Avast's English-language Threat Labs queue.
Result: the false positive report you usually skip because typing it out felt like 10 minutes of work lands in under two. The community forum post that would have been one terse sentence becomes a full incident writeup. Business Hub exclusions ship with justifications attached the first time around, not reconstructed at audit time.
Try it now: open the false positive form at avast.com/submit-a-sample, click the Description box, press your hotkey, and speak the next detection you need to report. Submit when you're done.