This is the public knowledge approved for the Vowise internal support pilot. Items marked Human must not be actioned or claimed resolved by the support assistant.
On the web, use the microphone control in Vowise. On mobile, use the main recording control or a supported Home Screen widget. On desktop, use the floating ball or the documented default global shortcut, Ctrl+Shift+R. A configured Vowise Shortcut can provide another entry on iPhone.
The Dictionary lets you add technical terms, names, and other vocabulary. Vowise can use those entries to improve recognition of words that matter to you. Manage Dictionary entries from Vowise settings.
Prompt Templates tell the AI how to structure or transform a transcription. For example, a project-summary template can organize action items and key conclusions. Available presets and custom options are shown in Vowise settings.
The desktop floating ball provides a quick recording entry while you use other apps. Click it to start or stop recording, open its menu for more options, and drag it to a convenient position.
Transcription uses 1 credit per 6 seconds of source audio, rounded up to the next 6-second unit, with a minimum of 1 credit. This equals 10 credits per minute. Eligible short clips under 7 seconds can be free when fast mode is enabled. Usage is based on source-audio duration, not transcript length.
Credit validity depends on the source and terms disclosed for each grant. Signup, trial, subscription, and promotional grants may use different validity periods. Unused credits may also be forfeited after account deletion or termination.
Use the Help Center, the contact form, or email [email protected]. Eligible signed-in internal pilot users can also open the secure Messenger on the Support page.
The Vowise Support Assistant is limited to Vowise public, approved support knowledge. It must not treat roadmaps, staging features, internal work items, or unverified claims as shipped product facts.
Do not send passwords, one-time codes, secret keys, full payment-card details, recordings, transcripts, journal entries, or unrelated personal data. Share only the minimum needed to explain the problem.
No. Refunds, charge disputes, billing corrections, and subscription changes require a human support teammate. The support assistant does not perform payment actions.
No. Account ownership, recovery, email changes, and access disputes require identity checks by a human support teammate.
Contact [email protected]. Deletion, export, correction, and other privacy-rights requests are handled by a person; the support assistant does not execute them.
Do not post secrets in chat. Email [email protected] with a concise description and safe reproduction details. Security and privacy reports are handed to a person.
Stop destructive retries, preserve the affected device and approximate time, and contact support. Suspected data loss or sync corruption always requires human investigation.
The support assistant should say that the fact is not confirmed and hand the question to a person. It must not guess that a roadmap or beta feature is generally available.
No. The pilot has no production Actions. The support assistant cannot refund, delete, export, change subscriptions, reset ownership, or modify Vowise data.
For eligible signed-in pilot users, Vowise sends a verified user ID, email, display name, and minimal platform context. It does not automatically send recordings, transcripts, journals, or payment details.
Vowise shuts down the Messenger session and clears Intercom cookies on the Vowise domain to reduce cross-account exposure on shared browsers. The next account receives a newly verified session.
The public Help Center, contact form, and [email protected] remain available. Messenger availability is not required to reach Vowise support.
No response-time SLA is promised during the internal pilot. If Messenger is unattended, use [email protected] so the request remains in the email fallback channel.
Yes. Support can capture the user need and context. Submission does not promise implementation or a delivery date; a teammate decides whether to create or link an internal product item.
