Everything you need to know about Meetwise

Meetwise is a meeting intelligence platform that turns recorded conversations into transcripts, structured summaries, decisions and reviewable action items. Approved output can then be used in connected Microsoft and CRM workflows.

Meetwise Pro is the credit-card-sized recording device that accompanies the Meetwise platform. It is designed for in-person conversations and other situations where a separate recorder is more practical than a meeting bot.

Not for every workflow. The platform supports uploaded audio and software-based capture flows. Hardware availability, onboarding and the best recording method for your organization are agreed during a pilot or rollout.

Meetwise is designed for organizations whose teams need reliable meeting records and controlled follow-up, including advisory, finance, sales, consulting, recruitment, legal and care-related workflows. Suitability depends on your recording, privacy and compliance requirements.

No. Meetwise is primarily an organization workspace with roles, review steps and integrations. It is sold through a guided business process rather than a public consumer webshop.

Record or upload a conversation, let Meetwise transcribe and process it, then review the summary, decisions and action items. Only after review do users or configured organization rules prepare or send follow-up to connected systems.

Yes. Physical meetings are a central use case. Audio can be captured with a supported Meetwise Pro workflow, the mobile app or an approved upload process, depending on the pilot configuration.

Meetwise supports calendar-linked and software capture workflows, but availability can depend on the Microsoft tenant and pilot configuration. We verify the exact Teams, Outlook and meeting-capture setup before rollout.

The upload is queued for background processing. Transcription, speaker processing, summary generation and action extraction can continue after the browser is closed. The workspace shows the processing state and offers a controlled retry when a job reaches a final failure.

Meetwise can separate speakers and supports speaker matching and transcript cleanup. Results depend on audio quality, overlap, room acoustics and language, so important names, decisions and actions should always be reviewed.

Yes. Transcripts, summaries and suggested actions are generated assistance, not a guaranteed verbatim or legally authoritative record. Users should review important output before relying on it or sending it to another system.

Yes. Meetwise is built around reviewed output. Summaries, action items, recipients and connected-record selections remain visible as separate reviewable elements instead of being sent as one opaque AI response.

New recordings default to Personal. The recording owner can explicitly share with selected teams or the entire organization when that functionality is enabled for the workspace. Access is enforced across audio, transcript, summary, actions and dependent integration data.

No. Organization roles do not automatically expose another user's Personal recordings. Admin capabilities and company-visible content are kept separate from personal recording access.

Removing a member from a team, or archiving that team, revokes team-based access. Live organization membership and role checks are used rather than relying only on an old shared link.

Authorized users can permanently delete an eligible recording after an explicit title-confirmation step. Meetwise removes the private audio object before deleting derived recording data. Limited metadata-only audit information can remain for security and accountability.

The platform contains workflows for Microsoft services and multiple CRM providers. Availability differs by connector and customer: some connections are live-proven, while others remain private-pilot or roadmap functionality. We confirm the exact supported scope before a pilot.

Yes. Organization owners can configure automated workflows that send personalized follow-up emails, update CRM records and create tasks or calendar appointments after a meeting. Meetwise executes these actions according to the organization's configured rules; only missing or ambiguous context and configured exceptions are held for review.

That depends on the connector and the user's reviewed selection. A typical approved export can include meeting title and date, summary, decisions, selected action items, participant names and a Meetwise link. Audio is not part of the standard reviewed CRM note flow.

Meetwise removes or revokes its stored connection credentials where the provider supports that flow. Records already created in the customer's external system can remain there, while bounded delivery and audit metadata may remain in Meetwise for security and duplicate prevention.

No. Salesforce is currently a gated private-pilot connector and should not be treated as generally available. A pilot requires a compatible subscriber setup, permission assignment, connection validation and explicit organization enablement.

Meetwise offers two organization-level routes. The international route uses the American provider OpenAI for both audio transcription and the generation of summaries, decisions and action items. It is sometimes called the American route, but it is not a US-only service. The European route uses Mistral AI for both stages. The Meetwise application and European storage layer remain the same; the selected route determines which AI provider receives the audio and transcript text. The route is configured during onboarding and is not changed automatically.

For both routes, Meetwise uses Supabase in Frankfurt for authentication, database services and protected storage; Sliplane in Germany for the application, backend and processing orchestration; and Infisical's European environment for securely managing keys and secrets. Infisical receives no meeting content, and Sliplane does not keep a separate meeting archive. Optional Microsoft, Google or CRM providers are only involved when an organization enables those integrations and only receive the data needed for that workflow.

Mistral AI is the AI subprocessor for both transcription and summarization on the European route. Mistral's current public register contains 25 entries. Infrastructure and model providers include Microsoft, Google, Mistral Compute, CoreWeave, Scaleway, Megaport/Latitude, OVHcloud, Backblaze and The Constant Company/Vultr. Security and platform providers include Ory, Kong, Sentry, Cloudflare, CrowdStrike, Wiz and Mistral affiliates. Other or feature-specific providers include Lago, Stripe, Black Forest Labs, Brave, Foundry Labs/E2B, Resend, Twilio, Intercom and Gradual. Meetwise does not use Mistral's web search, image generation or code execution features for meeting processing. Mistral does not publish the exact subset used for each request or account, so Meetwise cannot promise a smaller account-specific list.

OpenAI is the AI subprocessor for both transcription and summarization on the international route. OpenAI's current public API register lists infrastructure providers including Cloudflare, Microsoft, CoreWeave, Oracle Cloud, Google Cloud, Amazon Web Services and Cerebras. It also lists service-specific providers including Snowflake, TaskUs, Intercom, Salesforce, Accenture, Confluent, Cinder and Okta, plus OpenAI affiliates in the United States, Ireland, the United Kingdom and Japan. Pylon applies only when premium support is chosen, and Fivetran applies to the Assistants API, which Meetwise does not use for this meeting route. Not every listed provider handles every request; OpenAI does not publish the exact provider used per request.

The selected AI provider receives the audio itself to create the transcript. The resulting transcript text is then sent to the same route to create the summary, decisions, title and action items. Supabase stores the audio and results according to the organization's retention settings. Sliplane orchestrates the process but does not create a separate archive, and Infisical receives only technical keys and secrets.

Meetwise stores meeting data in Frankfurt and runs its application environment in Germany. For the European route, Mistral states that its standard service is hosted in the EU. Meetwise cannot currently guarantee contractually that Mistral processing remains exclusively within the EEA in every circumstance; Mistral may use approved transfer mechanisms such as adequacy decisions or Standard Contractual Clauses. The international route uses OpenAI's global API route and is not an EEA-only service: processing may take place in the United States and other locations listed by OpenAI. System, usage and billing metadata can also follow different location rules.

On the European route, Zero Data Retention is active for the Meetwise organization at Mistral for audio transcription and summarization. Mistral does not retain the substantive API input and output after returning the result; technical usage and billing metadata may be excepted, and use for product improvement is disabled. On the international route, OpenAI states that API data is not used for model training unless the customer explicitly opts in. Its current documentation lists no provider-side retention for audio transcription, while chat-completion content may by default be retained for up to 30 days in abuse-monitoring logs. Flagged content may be subject to limited review under OpenAI's policies. Meetwise therefore does not describe the international route as Zero Data Retention unless that control has been separately approved and configured.

Meetwise uses HTTPS/TLS when audio and text are transferred. Meeting data are stored encrypted in the protected Supabase environment, with role-based workspace access and database-level access rules. Providers and their subprocessors may access data only where needed to deliver, secure or support the contracted service and under their applicable terms. Support providers receive meeting content only when it is deliberately shared for a support case; Infisical receives no meeting content.

Not as a standard production service today. Some models may be licensed for customer infrastructure under separate provider agreements, but a fully local Meetwise variant would require a separate implementation. It would need suitable licensed models, dedicated GPU capacity, secure storage, monitoring, redundancy, backups and operational support. Costs, responsibilities, speed and quality can only be assessed after the required capacity and models have been defined and tested.

Meetwise does not silently switch an organization from the European route to the international route, or vice versa, during an outage, peak load or maintenance. Processing is marked as failed or available for retry. If only summarization fails, an already completed transcript remains available. A change of route or provider is a deliberate configuration decision that can be made subject to prior review and communication.

The person or organization starting a recording is responsible for an appropriate legal basis and for informing participants when required. Meetwise provides recording technology; using it does not by itself make a recording lawful.

No. The published privacy policy states that Meetwise does not sell personal data and does not use meeting content for advertising.

Do not assume certification. Certification and some compliance claims remain subject to further substantiation and legal or customer review. Ask Meetwise for the current security evidence rather than relying on an unsupported badge or general statement.

Meetwise applies organization-wide schedules by data type. Raw cloud audio has a fixed period, 90 days by default. Transcripts and complete meeting results can each use a fixed period or the contract term plus 30 days; the meeting-result period also covers actions and recording-derived organization knowledge. Limited audit metadata, provider usage metadata and backups follow their own documented schedules. The periods documented with the customer govern the workspace configuration.

Submit the request through meetwise.pro/contact. Meetwise may need to verify your identity and coordinate the request with the organization that controls the relevant workspace.

Customer workspace users sign in with the Microsoft account registered for their organization. If access is not active, the workspace owner should verify the exact email address, membership and assigned role.

Workspace owners and administrators manage supported connections and organization-level settings. Individual users can still be required to review meeting output and delivery choices, depending on the configured workflow.

The website's Web Bluetooth flow requires Chrome or Edge on desktop or Android over HTTPS or localhost. Safari and Firefox do not support this flow, so iPhone users should use the supported mobile workflow.

Keep the original local recording until upload and processing are complete. Restore connectivity and use the available retry. If the failure remains, contact support with the workspace name, app build, device and approximate time, but never send passwords, tokens or unnecessary meeting content.

For product questions, book a call through the website. For product support, email support@meetwise.pro. Submit privacy or deletion requests through meetwise.pro/contact.