Common questions, answered plainly.

Use Forms to create and share a hosted form. Use Widgets to add voice to a form on your own website. Use Extension to answer someone else’s Google Form or Microsoft Form by voice.

You need an account to create forms or widget keys and to connect the extension. Public hosted forms can be answered without signing in unless their creator requires it. Private forms require access through the correct signed-in email. Widget respondents follow the website’s own access rules.

Hosted forms and website widgets run in the browser without an app download. The extension must be installed in a supported desktop browser; store installation is coming soon.

Yes. Open a live demo to try answering by voice and typing. Use sample information rather than private answers in a public demo.

Hosted forms and website widgets work in modern mobile browsers. Voice requires microphone permission and an internet connection. The extension is for desktop Chrome and Edge, not mobile browsers.

No region is blocked. Voice performance is currently tuned for India, so people further away may experience slower responses or occasional interruptions.

AmphiVox is free: you are never charged for Forms, Widgets or the extension. For now, a voice session can run for up to 10 minutes, and the number of sessions running at once is limited.

Yes. Hosted forms keep their manual controls available, and you can type or correct answers during a voice session. Website widgets and the extension work alongside the original form’s controls.

Yes. The assistant can ask related questions together and capture other relevant answers you volunteer in the same turn. Review the filled fields before submitting.

Say a correction naturally or edit the answer directly on the form. Voice recognition can make mistakes; the visible fields are your place to check and correct them.

Valid answers supplied by the form are used so the assistant can focus on what is missing. A website widget must supply its current answers correctly. This does not guarantee that every website saves progress after you close its tab.

On hosted forms, file uploads, URLs, legal consent, and fields marked PII are completed manually. The extension also leaves picture-only choices, unsupported questions, and controls it cannot reliably fill to you. Follow the visible form’s instructions.

You can ask to skip an optional question. Required questions still need an acceptable answer before submission. Skipping does not erase an answer already present on the form.

On hosted forms, end the voice session and use Back to review earlier pages. Back and Next are disabled during the voice session because the assistant controls forward page turns. For extensions and other websites, use the original form’s own controls; earlier sections cannot be revisited by voice.

Check required fields, invalid values, manual questions, and earlier pages. On hosted forms, each page must pass validation before Next works, and the whole form must be valid before Submit works.

The assistant confirms answers and ends the conversation. A hosted AmphiVox form can then submit through its normal completion flow when valid. A widget’s website decides when and how to submit. The extension never presses Submit: you review and submit the original form yourself.

Hosted forms save eligible progress locally in the same browser for up to 24 hours after the last save, when browser storage is available. Clearing browser data or changing browsers/devices can lose it. Selected local files must be chosen again. Widgets depend on their website’s saving behavior; extension answers remain subject to the original platform’s behavior.

Check the answers already visible on the form. You can continue manually or start another session when available. Do not submit again unless you are sure the previous submission failed. If voice is busy, wait briefly and retry.

Sessions currently end after about 45 seconds of silence during your turn or after 10 minutes in total. Muting is not pausing. Start another session if you need more help; answers already written remain on the form.

Allow microphone access in your browser and operating system, choose a working microphone, and check mute, output device, and volume. Restart the session after correcting permissions. You can continue filling available fields manually.

Choose from the language and voice controls before starting. AmphiVox supports 45+ languages, including Indian languages and mixed conversations such as Hinglish. Changes apply to the next session. See the voice documentation for the current list.

Dedicated phone and address fields use their configured country context for validation; valid phone numbers use international E.164 format. Do not assume a plain text field on another website or an extension platform has all the same validation capabilities.

Start with a blank form or import screenshots or a PDF. Review the extracted fields and import notes, edit what you need, and publish when ready.

An import is an editable starting point, not a guarantee of exact reproduction. Review field types, labels, choices, rules, and pages before publishing.

You can preview the visible form and its pages before publishing. Voice testing uses a published form: publish, open your own link, and try it. Close or delete a form you created only for testing.

Yes. Add and reorder fields, organize them into pages, and configure required fields and supported validation. Available options depend on the field type.

Share its published link by message or email, or use its QR code on a poster or at an event. Respondents open it in their browser.

A public form can be open to visitors. Requiring sign-in identifies respondents but does not by itself create an invited-email list. Private forms restrict access to permitted signed-in users, using the creator’s allowed emails.

Ask them to check the email they signed in with. Check the allowed-email list and whether the form is closed.

You can restrict each signed-in respondent to one response. This identifies authenticated accounts, not every anonymous person or someone using multiple accounts.

Yes, from form settings. Closing blocks new hosted page visits and final submission. It does not immediately stop a voice session already running, and it does not deactivate a widget key.

Yes. Open the form’s editor, make your changes, and save. Test the updated form before sharing it again. If a website widget mirrors that form, update the website’s matching fields and pages too.

For AmphiVox storage, open the form’s Settings page: its Responses block shows how many submissions are stored and has an Export CSV button. For Google Sheets or Microsoft Excel delivery, view responses in that destination; those submissions are not also stored as AmphiVox responses. The one exception: if a delivery to your spreadsheet fails, AmphiVox tries to save that response in its own storage instead, encrypted.

Respondents upload manually. Files go to the creator’s connected Google Drive folder. A form with file fields cannot accept responses until that destination is connected. File size and extension restrictions depend on the configured field and are enforced by the server.

The creator should check the form’s delivery or Drive settings, permissions, and connection, then reconnect or correct the destination if needed. Respondents should follow the visible failure message and contact the creator. When a delivery fails, AmphiVox tries to save that response in its own storage instead, encrypted.

Yes, through its management controls. Treat deletion as permanent. Data already delivered to Google Sheets, Excel, or Drive is managed separately in those services; do not assume deleting a form erases those external copies.

A widget key connects your website integration to its configuration and approved websites. Create one in Dashboard → Widgets, then use its setup instructions for JavaScript or React.

Form-linked widgets use a form configured in AmphiVox while your website mirrors its fields and pages. Developer-defined widgets receive the schema from your code. Either mode can use JavaScript or React.

No. In both widget modes, your website owns final submission, storage, delivery, and file uploads. Linking a form supplies its schema; it does not add hosted-form response delivery.

Yes. Use the JavaScript SDK or React component/hook, with the built-in voice dock or your own voice UI. Custom controls must tell users they are speaking with an AI assistant before starting.

Check the key, its mode, the approved embedding origin, microphone permission, HTTPS, and your security policies. Follow the integration guide’s troubleshooting section for the reported error; localhost is available for secure-context development.

Configure the allowed websites on the key. Each embedding origin must match the allowed configuration. Check scheme, domain, and port for local development; do not assume a wildcard or another subdomain is allowed.

Your website does. It reports current fields and answers, handles the assistant’s page-turn request, reports failed writes or blocked navigation, and decides whether to submit after completion. Use the relevant guide for the full sequence.

Developer-defined schemas can change between sessions, not during a running session. You can delete a key from its widget settings to stop new sessions. Review the confirmation: deleting a key that owns an AmphiVox form also deletes that form; a separately linked form is retained.

Use the JavaScript or React integration guide to get started, and its API reference for exact methods, options, field values, and callbacks. The dashboard setup links open on your widget’s mode.

Store installation is coming soon. The extension product page and getting-started guide will show installation instructions when distribution is available.

Google Forms and Microsoft Forms in desktop Chrome and Edge. The form must be displayed in English; you can speak any supported language. Mobile browsers, Safari, Firefox, and other form platforms are not currently supported.

Yes, when the original form requires provider sign-in. Connect AmphiVox for voice access, and separately meet Google/Microsoft and form-owner access requirements. The extension does not bypass them.

Check that the extension is installed and enabled and that you are on a supported form’s answer page, not its editor, results, or confirmation page. Reload after installation. A browser without the extension cannot show its mic button.

Yes. The assistant follows answers you type or select on the original form during a session. You can correct fields yourself.

File uploads, link questions, picture-only options, unsupported questions, and controls the assistant cannot reliably fill remain manual. On a one-answer question with “Other”, you can say your own answer. Platform validation still applies. See the Google and Microsoft support sections for exact capabilities and limits.

Yes. Single-page and multi-page Google Forms and single-page and multi-section Microsoft Forms are supported, including branching, quizzes and pre-filled links. Math questions in a Microsoft quiz are answered on the form yourself. On a timed Microsoft form, press Click to start yourself first; the assistant does not track the time limit.

When the form shows a validation message, the assistant reads it to you and asks for a different answer. Otherwise, check the form for a required question that is still empty and complete it on the page. If still stuck, end voice, use the form’s Next control, and start again on the next page.

No. It fills the supported form during a voice session; you review and press the form’s own Submit button. It does not read unrelated tabs, browsing history, or unrelated sites.

The extension connection renews itself as you use it and expires after three days without use. Sign out everywhere or account deletion also ends it. Click the mic and reconnect; sign into the original form provider separately when required.

No. Microphone audio is streamed for speech recognition and is not saved as a voice recording. Conversation text and submitted responses have separate retention rules.

Diagnostic logs may include conversation text and collected answers for up to seven days. Optional feedback is retained for 365 days. Hosted responses in AmphiVox storage remain until the creator deletes their form. Responses sent to external destinations follow those services’ and the creator’s policies. Read the Privacy Policy for the complete details.

It makes that configured field manual: the assistant does not ask for or populate it. It does not redact arbitrary sensitive information someone voluntarily says into an active microphone. Review what you share.

No. You are speaking to an AI voice assistant. Built-in experiences disclose this before starting. Websites using custom widget controls must provide that disclosure too.

Explain the purpose of your form, who receives the information, and any notices or consent your workflow requires. Link your own privacy information where appropriate, alongside AmphiVox’s policy.

Ordinary Sign out ends your current website session. Sign out everywhere revokes your sign-in credentials for the website and the extension across devices, including this browser; propagation can take up to a minute. You will need to sign in again. A voice session already in progress is not cut off.

Yes, from Account → Profile. Review the deletion summary and confirmation first. Data in external services and records retained under the Privacy Policy are not necessarily erased by account deletion.

Email contactus@amphivox.com with the product, browser/device, symptom, and safe reproduction steps. Avoid sending private form answers, widget secrets, connection tokens, or other credentials. For access to someone else’s form, contact its creator.