VoIP.info Current device research

Jabra Evolve3 85 business Bluetooth headset

Evaluate the Evolve3 85 by exact MS or UC SKU, Link 390 or native-Bluetooth path, host application, management owner, firmware and user acceptance rather than treating pairing as deployment proof.

Reviewed 2026-10-14Jabra's current Evolve3 85 product page, April 28, 2026 RevB datasheet, RevA user manual, current support and release notes, January 21, 2026 launch notice and management overview reviewed September 28, 2026; no headset, host, adapter, radio, application, management service, battery, firmware, audio, privacy control or call testedIntermediateDocumentation based · not lab tested

Documented specifications

Open IP Phone Compare →

Jabra · Jabra announced Evolve3 85 on January 21, 2026 for availability from March 1, 2026. At review, the support page listed firmware 1.1.10 dated April 8, 2026 and Jabra Direct 8.2.23201 dated August 24, 2026. Regional inventory, the purchased SKU, approved firmware, warranty entitlement and remaining support period were not established.

Evolve3 85: manufacturer-sourced facts
SpecificationDocumented value
Variants and included pathsUC and Microsoft Teams variants are listed with USB-A or USB-C Link 390 adapters; black or selected warm-gray SKUs and optional wireless-charging-pad bundles have distinct order codes Source ↗
Host connectionsBluetooth 5.3, a supplied Link 390 adapter, native Bluetooth and a 3.5 mm cable are documented; the USB-C connector is described for charging, not as an independently documented wired-audio path Source ↗
Analog-cable boundaryWith the supplied 3.5 mm cable connected, the headset microphone and Bluetooth are disabled; a connected smartphone uses its own microphone, and the analog cable does not charge the headset Source ↗
Bluetooth and multipointThe datasheet lists up to eight paired devices, two simultaneous Bluetooth connections and a manufacturer range up to 30 m; the manual says calls can arrive from either connected device Source ↗
Audio and fitOver-ear form, 220 g published weight, 32 mm speakers, digital MEMS microphones, adaptive ANC, HearThrough, sidetone, on-head detection and busylights are listed Source ↗
Battery and chargingUp to 25 hours talk with ANC and busylight off, up to 21 hours with them on, up to 120 hours music with ANC off, charging up to 180 minutes, fast charging and SKU-dependent wireless charging are manufacturer conditions Source ↗
Software and managementJabra lists Plus, Direct and Xpress support and says Evolve3 75/85 were supported at launch in Plus Management, Plus Mobile, Direct and Xpress; centralized and individual-user tools remain different administrative paths Source ↗
Current support snapshotFirmware 1.1.10 dated April 8, 2026 fixed several rare call, battery, freeze and update cases; this dated release is not declared the correct build for every managed fleet Source ↗

Unlisted fields remain unverified. Platform compatibility and remaining support life require confirmation for the exact ordered model.

Keep the call account and application on the host

Evolve3 85 is a host-connected audio and control device, not a standalone SIP endpoint. The computer or mobile device owns the account, signaling, contacts, network and emergency-calling behavior. Record the exact host, operating system, application build, selected microphone and speaker, account and approved connection path. A Bluetooth connection, music stream or visible call button does not prove two-way speech, DTMF, hold, mute synchronization or answer and end behavior in the intended application.

Pilot each required workflow with a remote listener: incoming and outgoing calls, answer and reject, mute from both headset and application, simultaneous notifications, host sleep and wake, radio or adapter reconnection and recovery after restart. Preserve the application-specific result rather than transferring a Google Meet, Teams or Zoom certification to every browser, softphone or PBX client.

Preserve the MS or UC SKU and physical connection

The datasheet lists separate UC and Microsoft Teams order codes with USB-A or USB-C Link 390 adapters, color choices and selected wireless-charging-pad bundles. Record the complete order code and included accessories before deployment. A dedicated Teams control and platform markings are variant-specific; they do not change which host owns the call.

Treat Link 390, native host Bluetooth and the supplied 3.5 mm cable as separate paths. The manual describes USB-C as charging and documents wireless audio through Link 390 or native Bluetooth; do not assume wired USB audio without model-specific proof. On the analog cable, the headset microphone and Bluetooth are disabled, the connected smartphone uses its microphone and the cable does not charge the headset. That makes the analog connection a constrained fallback, not an equivalent managed-call path.

Control multipoint, sensors and privacy

Jabra lists eight paired devices and two simultaneous Bluetooth connections. The manual says the headset can accept calls from either connected device and assigns voice-assistant behavior to the last connected device. Inventory paired hosts, restrict pairing and clear old associations before reassignment. Test which device wins when calls or media arrive together; multipoint is not a capacity promise that two business calls can be mixed or recorded correctly.

The manual explicitly notes that microphones may record private conversations and that on-head sensors can reveal presence. Decide whether on-head detection, voice assistant, Apple Find My, Google Find Hub and management telemetry are permitted. Document reset and offboarding steps for both headset and management records. The manual's 128-bit secure-Bluetooth statement describes the headset radio pairing path; it does not establish protection inside the host application, across the IP service or to the far end.

Separate personal settings from fleet management

Jabra lists Plus, Direct and Xpress, and says the Evolve3 75/85 launched with Plus Management, Plus Mobile, Direct and Xpress support while individual desktop use transitions to Plus Desktop when available. Assign one firmware and configuration owner. Keep personal sound settings, local updates, adapter firmware and centrally deployed policy distinct so one user's app cannot silently become the fleet authority.

The support page listed firmware 1.1.10 dated April 8, 2026 at review. Its notes include rare auto-answer and call-end, battery, freeze and update fixes. Record headset and Link 390 versions and re-run call control, mute, multipoint, sensor and charging acceptance after any update. A current vendor download is not automatically an approved enterprise release, and the reviewed public material does not prove downgrade, staged rollout or configuration-lock behavior for a particular tenant.

Bound battery, range, hearing and AI claims

The published 25- or 21-hour talk figures, 120-hour music figure, 30 m range, charging times, voice-pickup accuracy, ANC and hearing-protection names are manufacturer claims or specified test conditions, not a result in the buyer's room, radio environment or application. Test speech pickup with nearby talkers, comfort across the intended shift, sidetone, maximum-volume policy, busylight visibility, charging ownership and battery endurance under the approved settings.

Voice-assistant and AI-readiness language does not prove transcription accuracy, confidentiality, application integration or an authorized data path. Define whether voice assistants and generative-AI features are allowed before acceptance. No headset, host, adapter, radio, application, platform certification, management service, privacy control, hearing outcome, range, battery endurance, firmware, availability, price, emergency route, audio quality or live-call behavior was tested for this guide.

Place Evolve3 85 inside a host-and-control acceptance plan

The business wireless headset category keeps Link 390, native Bluetooth and the analog fallback as separate paths. Use the control diagnostic when headset buttons, application state or remote mute evidence disagree.

Sources & applicability

Primary references for the technical details above. Operational examples and planning checklists are VoIP.info editorial guidance.

Examples require adaptation to your topology. No live PBX or hardware testing is claimed.