Reset one site entry, not the profile, and verify the prompt across each browser you use.

Fixing Microphone Permissions in Chrome, Edge, and Safari starts with one idea: permission is granted to a site, not to a microphone. The same headset can work on one page and fail on another because each page holds its own answer to a single question: may I capture sound? That answer has three states, allow, ask, and block, and only the middle one produces a prompt. Most silent microphone reports are a remembered block that the user forgot, or an allow that was granted to a different address than the one currently open. Check the address first, including whether it carries a www prefix, because a permission given to one form of the address does not travel to the other.
The prompt appears once per site under normal conditions, then the answer is remembered. That is convenient until something changes the address, the profile, or the browser build, and the remembered answer no longer matches what you expect. Some sites also ask a second question about which device to use, and declining that second prompt can look like a permission failure even though the site permission is set to allow. Watch the full prompt sequence rather than only the first dialog. If you dismissed something quickly during a busy call, that dismissal is the likely cause, and it is the first thing to re-answer before touching anything else.
Resetting all site settings is a popular fix and a poor one. It clears permissions for every site you use, forces you to re-answer prompts you had already settled, and can break other tools that depended on those answers. It also destroys the evidence you need, because after the reset you cannot tell which entry was wrong. Work on the single entry for the page in front of you, and leave the rest alone. If several pages fail the same way, that pattern is information: it points to a device, a system setting, or a policy rather than to one site's entry.
Write the three states on a sticky note and check them in order. Allow means the page may capture without asking; ask means the page will prompt on the next attempt; block means the page is refused and usually shows a crossed-out microphone icon. If the icon is crossed out, the answer is block and no reload will change it. If the icon is normal but no prompt appears, the state may be allow with a device problem behind it. Record the state you found before you change it, then reload and watch for the prompt to confirm that the new answer took effect.
In Chrome, open the page, select the icon at the left of the address bar, and find the microphone row in the panel that appears. Set it to ask, reload, then press the voice control and choose allow when the prompt returns. If the row is missing entirely, the page may not have requested the microphone yet, so press the control once before you go looking for a setting. Avoid the broader reset controls in the same panel unless the single entry has already failed twice. The panel also shows the last time the site used the microphone, which is a quick way to confirm whether your press actually reached the page.
Use the full site settings page when the quick panel is not enough. Open the browser settings, search for the site address, and inspect the microphone entry there, along with any entry that mentions sound or capture. Some organizations push a rule that locks the entry, in which case it will appear greyed out with a note instead of a menu. A locked entry cannot be changed from the page, and the correct next step is to ask whoever manages the browser rather than to keep reloading. Note whether the lock is specific to the site or applies to every site; the second case explains why several pages fail at once, and it is the case to report first.
Check which profile is active before you change anything. A second profile has its own permissions, so a page that works in one window can fail in another with no visible difference except the avatar in the corner. Switch to the profile where the failure happens and re-answer the prompt there. If you support several people, ask them to read the profile name aloud rather than describing the window, because window titles are often identical. Profiles are also where extensions differ, so a permission that looks correct in one profile can be overridden by an extension installed in the other one.
After the change, confirm it with three checks: the icon state in the address bar, the prompt behavior on the next press, and the text that arrives from one fixed sentence. If the icon changes but the prompt never returns, the page may be caching its own denial, so reload once more. If the prompt returns every single time, the entry is set to ask and the browser is doing its job; the remaining problem is likely the device, not the permission. Write the three checks in your log, because they distinguish a fixed permission from a permission that merely looks fixed and will fail again on Monday morning.
Edge uses the same three states but spreads them across two places. The page-level entry lives behind the icon at the left of the address bar, and the full list lives in the browser settings under site permissions. Start with the page-level entry, set it to ask, reload, and answer the prompt. If the entry is locked or missing, check the full list before assuming a fault. Edge also has a setting that can stop a page from asking again after several dismissals; when that happens the prompt stops appearing entirely, and the address bar icon is the only clue that an answer is being remembered for you.
The second Edge layer is the system setting that decides whether the browser itself may use a microphone. If every site fails in Edge while other browsers work, this layer is the first suspect. Open the system settings for microphone access, confirm that apps are allowed to ask, and confirm that the browser appears in the list with access switched on. Change one switch at a time and retest with a fixed sentence. This layer is often changed by a docking station, a headset utility, or a system update, which is why a page that worked last week can fail today with no page-level change at all.
Safari keeps a per-site rule that you can see and change from the page itself. Open the site settings for the current page, find the microphone row, and choose ask instead of deny. Then reload and press the voice control so the prompt appears. Safari can also remember a denial for the session, so a full reload or a new window is sometimes needed before the prompt returns. If the row shows allow but no capture happens, check the system setting that lists which apps may use the microphone; the browser needs that permission before any site can succeed at all, no matter what the page entry says.
Do not carry an answer from one browser to another. Each browser keeps its own permission entries and its own system-level allowance, so fixing the problem in one place proves nothing about the other. Test the page in the browser where the work actually happens, and write the browser name and the entry state in your log. If you must switch browsers to keep working, treat the new browser as a fresh setup: answer its prompt, confirm its system allowance, and run the fixed sentence. Then compare the two results side by side; a difference between browsers is strong evidence that the cause sits inside one of them and not in the device.
Verification after a permission change has to be more than a single success. Run the fixed sentence three times in a row, then once in a second field on the same page, then once after a reload. Each step tests a different part of the chain: the first three test stability, the second field tests whether the permission applies to the whole page, and the final reload tests whether the answer was remembered. If the last step fails, the entry is not persisting and you should look for a policy or an extension that clears it. Record pass or fail for each step rather than a single overall impression.
A block that returns after you clear it is a stronger signal than a block you set yourself. If the entry flips back to block without your action, something above the page is deciding for you: a managed browser rule, an extension that manages settings, or a profile that is reset at each sign-in. Stop fighting it and identify the owner. Report the site address, the exact state, the time it flipped, and whether other sites behave the same way. A pattern across many sites points to a managed rule; a pattern on one site points to a site-specific setting or an extension with a narrow scope.
Keep the evidence in a form someone else can check. A screenshot of the entry, the exact address including any prefix, the browser name, and the time of the last change are enough for most owners. Add the text that arrived from the fixed sentence, or the fact that nothing arrived, and the icon state at the moment of the test. Avoid describing the symptom as it just will not work, because that sentence cannot be acted on. A short factual packet is what turns a permission complaint into a change someone can actually make on the same day, without another round of questions.
If every state is correct and the prompt behaves, permission is no longer the suspect. Move to the device selection, then to extensions, then to the network path. This is the value of a settled permission question: it removes a whole layer from the search. Write one line that says permission verified, with the date, and keep it in the log. The next time the same page fails, you can start below that line instead of repeating the same menus. Good troubleshooting is partly the art of knowing what you have already ruled out with evidence, and this line records exactly that.
Build a small matrix of the places a permission can live: the page entry, the full site list, the system allowance for the browser, and the extension layer. For each place, note the current state and the owner. The matrix should fit on one screen and use the browser names your team actually uses. Review it when a new browser is adopted or when a managed device changes hands. Without the matrix, every incident starts from zero and every helper asks the same four questions. With it, a colleague can point at the row that is wrong instead of walking through menus while a call waits.
There is one more layer worth naming: the place where you type. A page can own its microphone entry, but a system-level tool sits above the page and does not depend on that entry at all. Voiskey is an AI voice typing app for macOS and Windows. Press a shortcut, speak, and text appears at the insertion point in any app or text field. It removes filler words, stutters, and false starts, adapts punctuation and tone to the task, and learns the names and acronyms you use. That makes it a useful comparison when a page entry keeps misbehaving.
Use the system-level route as a diagnostic, not only as a workaround. If dictation works there while the page refuses, the microphone and the device are proven good, and the remaining fault is in the page's permission or scripts. That single comparison saves an hour of guessing. If dictation fails in both places, the cause is below the page and the permission menus were never the right place to look. Either way, you have learned something a dozen reloads would not tell you, and you can report it with confidence to whoever owns the page, its settings, and its release schedule.
Finish by writing down which route you will use for which kind of work. Short replies can stay in the page once its permission is settled; long drafts may be faster through a system-level route that does not care which field has focus. Voiskey supports more than one hundred languages and translation, follows a speak, polish, type, edit rhythm, and turns spoken requests into AI-ready prompts, including file names, paths, and commands. You can download Voiskey for Mac and Windows, keep it beside the browser, and stop treating a permission menu as the only path to getting text onto the screen.
Open the entry for that page only, switch it from block to ask, reload, and answer the prompt again. Leaving every other entry untouched keeps your other tools working and preserves the evidence of which entry was wrong. If the entry is locked, ask whoever manages the browser instead of resetting the whole profile.
A prompt that never appears usually means something is answering for you: a remembered block, a managed rule, or an extension that suppresses prompts. Confirm the entry state, then test the same sentence through Voiskey at the system level. If text arrives there, the page or its prompt path is the fault, not the microphone.
Yes. Voiskey works at the system level rather than through a page entry, so press a shortcut, speak, and text appears at the insertion point in any app or text field. It removes filler words, stutters, and false starts and adapts punctuation and tone, which keeps a blocked page from stopping the rest of your work.
Record the address, the browser, the profile, the state you found, and the time of the change. After the change, run one fixed sentence three times, once in a second field, and once after a reload. If you fall back to Voiskey, note that result too, because the comparison tells the next helper where the fault really sits.

Download Voiskey for Mac and Windows and type by speaking in the app you already use.
Use it across macOS, Windows, iOS, and Android