Installing the Desktop App (Windows)

Overview

The Intempt desktop app runs on Windows as a native Tauri app. It gives sales reps live coaching from Blu during calls, pre-call briefs, and automatic CRM updates after each call. This guide covers getting the Windows installer, running it, signing in, and the permissions the app needs.

The Windows build ships as a 64-bit (x86_64) installer. There's no separate ARM build.

📘 Good to know

The Windows build is newer than the macOS one, and a few audio features differ. On Windows the app runs noise suppression and voice detection on your mic instead of the echo cancellation used on macOS, and in-browser meeting-URL detection is still being hardened. Recording, transcription, and the rest of the app work the same way.

How it works

The Windows app is packaged with NSIS, so the installer is a standard Windows .exe setup program. It installs the Intempt app, which renders inside Microsoft's WebView2 runtime.

WebView2 is the only webview the Windows app uses, and it needs version 109.0.1518.78 or later. Most up-to-date Windows 10 and Windows 11 machines already have a newer WebView2 runtime through Windows Update.

The installer is code-signed when Intempt's signing pipeline is configured for the release. A signed build opens without an "unknown publisher" warning.

Getting started

Download and install

1. Get the Intempt Windows installer. It's an NSIS .exe setup file.
2. Run the installer. Double-click the .exe. If Windows SmartScreen shows a prompt on an unsigned or freshly downloaded file, choose More info, then Run anyway.
3. Follow the setup steps. The installer walks you through install location and finishes on its own.
4. Launch Intempt from the Start menu or the desktop shortcut.

📘 Media pending

📘 Good to know

If the app won't open and nothing happens, your machine may be missing the WebView2 runtime. Install the Microsoft Edge WebView2 runtime, then launch Intempt again. Windows that's current on updates almost always has it already.

Sign in

The first time Intempt opens, you land on the sign-in screen. Continue with Google, Apple, or Microsoft, or sign up with your corporate email.

If you use email, enter it and Intempt sends you a one-time code. Enter the code to continue. You can resend the code or switch to a different email from the same screen. If your organization requires multi-factor authentication, you'll see one more code step after that.

📘 Media pending

First-run setup

After you sign in, you'll go through two steps before you reach the app:

1. Workspace. Enter your company's website to create your workspace.
2. Brand Intel. Blu scans that website and shows what it found before you start.

See Onboarding (workspace setup) and Onboarding: brand intel and your plan for what happens on each step.

Permissions

Windows doesn't show a per-app recording prompt the way macOS does. The app treats system-audio capture as allowed and reads the far side of a call through WASAPI. Your microphone is governed by Windows Settings > Privacy & security > Microphone, so make sure microphone access is on for desktop apps.

Grant and review access from Settings inside the app, on the Permissions tab, before your first recording.

📘 Media pending

📘 Good to know

The exact download link and release channel aren't published in the app's source, so this guide describes the file you'll receive rather than a fixed URL. Get the installer from the link your Intempt contact or admin shares with you. A Tella walkthrough of the Windows install is planned.

Where to go next

• Desktop App Overview for a tour of the app's windows.
• Onboarding (workspace setup) to finish setting up your workspace.
• Recording & Capturing Meetings on Desktop to record or upload your first call.
• Installing the Desktop App (macOS) if you also run Intempt on a Mac.