Everything you need
before the conversation.

VoxaPulse is an AI-assisted live interpretation service for online meetings. Participants speak naturally, see the original speech and its translation as captions, and can hear translated audio with low delay. Google Meet continues to host the call; VoxaPulse adds a private translation layer through its Chrome extension.

No. VoxaPulse provides automated, non-certified translation. AI can misunderstand accents, names, numbers, terminology, overlapping speech, or context. Confirm important information directly with the speaker, and use a qualified human interpreter for medical, legal, financial, emergency, or other high-stakes conversations.

The extension shows the languages currently enabled for your VoxaPulse workspace. The organizer chooses one language for each side before starting. Availability may change as language quality is tested and improved.

Translation is designed to feel near real time. The production objective is p95 latency of 2.5 seconds or less, but this is not a guarantee. Network quality, speech clarity, phrase length, device performance, and provider availability can increase the delay.

The service preserves each participant’s audio route, but simultaneous speech is inherently harder to recognize and translate. For the clearest result, let one person finish a short phrase before another begins.

One person joins the organizer-language side and the other joins the guest-language side. Each speaks in their own language, receives the other person’s translated captions, and can listen to translated speech privately. Both participants must complete consent and device checks before the translation becomes active.

The organizer selects one shared language for each group and receives two invitation links and six-digit codes: one for the organizer-language team and one for the guest-language team. Each participant joins the correct side through the VoxaPulse extension. Everyone on a side speaks the same selected language and receives translation from the other side.

Yes. Anyone whose voice should be translated or included in the private same-language team mix must join the correct language side in the extension and grant the required permissions. Joining only the Google Meet call is not enough for participant-attributed translation.

A VoxaPulse session currently connects two language sides. Each side selects one language for the whole group. A meeting that needs three or more simultaneous languages requires separate language arrangements.

No. A guest installs the extension, chooses “Join with guest code,” enters the six-digit code and a display name, reviews the consent options, and joins. Codes are time-limited and grant access only to the assigned meeting side.

Install the VoxaPulse Chrome extension, sign in, open the Google Meet tab you want to translate, and open the extension. Choose the organizer-group and guest-group languages, review the consent and transcript options, then select “Start and create guest code.” Share the correct link or code with each language group.

Open the organizer’s Google Meet link, install the extension, select “Join with guest code,” and enter the assigned six-digit code and your name. Review and accept translation processing, choose whether to allow transcript storage, and continue. Translation starts after at least one participant on each language side is connected and ready.

Chrome must be allowed to run the extension, capture the selected meeting tab, and use the microphone. Audio playback must also be allowed. VoxaPulse shows connection and device status before and during the session so a blocked permission can be corrected.

The usual causes are that the other language side has not joined, microphone or tab-capture permission is blocked, the wrong code was entered, audio playback was blocked by Chrome, or the private media connection is still recovering. Keep the Google Meet tab open, check the extension status, and confirm that at least one participant on each side has joined.

VoxaPulse attempts to restore the participant’s private route. If a required team-audio route is lost, the extension falls back to the original Google Meet audio instead of silently leaving the user without sound. Captions or translation may pause until recovery completes.

After consent, the extension sends your microphone audio through an encrypted, participant-attributed media route for live speech recognition and translation. Each publication is tied to the participant and language side. The translated audio is returned to the intended opposite side. Raw meeting audio is processed transiently and is not stored by VoxaPulse.

No. Google Meet hosts the original call, while translated playback is delivered privately through the extension. VoxaPulse does not rebroadcast the synthetic translation into your microphone or make everyone in the Meet call hear the same translated track.

“My group + translation” plays original voices from your own language group together with translation from the other side. “Original Meet + captions” keeps normal Google Meet audio and turns private translated audio off. “Translation only” plays only the translated private track. You can also adjust translation volume.

The extension shows two caption lines: the other participant’s recognized speech and “Translation for you.” Captions update as complete phrases arrive and identify the relevant speaker or language side. They are displayed only in your VoxaPulse extension and may appear before or alongside translated audio.

Yes. Noise, accents, specialist vocabulary, names, numbers, weak connections, and overlapping voices can cause omissions or incorrect wording. Captions and translated speech come from the same automated process and should be verified when accuracy matters.

Yes. Every participant must explicitly consent to live translation processing before their audio is used. The organizer is also responsible for providing any notice and obtaining any additional consent required by local recording, workplace, or meeting rules.

VoxaPulse does not retain raw meeting audio. Audio is processed in real time to produce recognition, translation, captions, and private playback. Google Meet or another participant may have separate recording features, which are outside VoxaPulse and subject to their own controls.

Transcript storage is optional and requires consent from all required participants. If anyone declines, live translation can continue but the meeting transcript is not saved. A saved transcript contains text rather than raw audio and is normally retained for 30 days unless deleted sooner.

Yes. Authorized workspace users can open saved meeting transcripts and export them as TXT, PDF, or DOCX while they remain available. Because the transcript is AI-generated, review it before using or sharing it.

Primary VoxaPulse service data is hosted in the Hetzner FSN1 (Falkenstein, Germany) region. Contracted cloud, AI, identity, payment, support, and other providers may process information in the United States or other countries as described in the Privacy Policy. Customer-specific residency is available only when confirmed in a written agreement.

Use the privacy controls in your account or contact VoxaPulse support. Identity or authority may need to be verified before account, transcript, access, correction, export, or deletion requests are completed.

VoxaPulse deducts tokens for the translation work actually processed in each meeting rather than simply charging for wall-clock meeting time. Usage can vary with the amount of speech translated, source transcription activity, the language pair and processing requirements, the number of people speaking in each group, overlapping speech, and other service conditions. Plan time is a planning estimate, not a fixed token-to-minute conversion. The meeting usage record shows the measured customer debit, and later provider invoices do not revise that balance.

Starter includes 9,746 monthly tokens, 1 member account, and one concurrent meeting. Professional includes 99,000 tokens, 5 member accounts, and two concurrent meetings. Business includes 409,230 tokens, 15 member accounts, and five concurrent meetings. Enterprise includes 1,051,578 tokens, 30 member accounts, and 20 concurrent meetings. The organization owner is the primary account and is not counted as a member account.

A member account is an employee account used to create and manage translation meetings. The employee who starts a meeting becomes that meeting’s owner. Meeting participants are invited separately and assigned to one of two language groups, so they do not use member account allowances.

Plans are billed in USD. Applicable sales taxes are calculated separately during checkout based on the billing address. Tax does not increase the number of tokens credited to the account.

You can cancel renewal from billing settings; access continues through the current paid period and the subscription does not renew. Refund requests are reviewed manually based on the circumstances and applicable law. Canceling a checkout before payment creates no charge.

The current participant experience uses the VoxaPulse extension in Google Chrome with Google Meet. Each person who uses translation must run the extension in their own browser session.

Yes. Professional, Business, and Enterprise plans include multiple member accounts. Workspace administrators can manage team access, while meeting invitation codes remain separate and temporary.

Use the Contact page or your workspace support area and include the meeting time, language pair, and a description of the status shown in the extension. Do not send passwords, payment-card numbers, or confidential transcript text. Support aims to respond within two Canadian business days.