Two apps, two jobs.
Desktop is for office seats that live inside calls. The field app is for technicians working from the truck, basement, rooftop, or driveway.
Thorbis Desktop
For CSRs, dispatchers, owners, and office admins. Native phone shell, OS notifications, window memory, and call controls that stay reachable.
Open Thorbis→Thorbis field app
For technicians in the field. Photos, checklists, signatures, price book, and payments, with offline mode in development so work syncs when signal returns.
Explore the field app→It is not a different product. It is a better phone.
Everything in Thorbis works in your browser. The desktop app exists for the people answering and placing calls all day.
Calls survive everything
The phone runs in a dedicated background engine, so a page navigation, a full reload, an OAuth redirect, or a Wi-Fi blip never drops a live call. In a browser tab, any of those ends the call.
Native notifications + ring
Incoming calls, new texts, jobs, and payments ring and surface as real OS notifications even when Thorbis is in the background or closed to the tray. Click one to jump straight to the record.
Always-on dialer
An always-on-top call card stays reachable over any window, with answer, mute, hold, and transfer, so whoever runs the phones can take a call without hunting for the tab.
Hardened + auto-updating
A locked-down native shell (sandboxed, signed, integrity-checked) that updates itself in the background, and never installs an update in the middle of a call.
The call survives while the app keeps moving.
Office staff can open customer records, move through schedules, refresh data, and send payment links without tearing down the phone session.
Inbound call from Sarah Johnson
Linked to AC repair job #JB-2843
CSR opens customer timeline
Equipment, invoice, and notes stay one click away
Dispatcher moves the schedule
Dashboard navigation does not touch the live call
Warm transfer to lead tech
Context follows the call to the next person
ONE LIVE CALL · ZERO INTERRUPTIONS · 08:17–08:22
Feels like office software because it behaves like office software.
Tray presence
Close the window without closing the phone. Desktop stays available for incoming calls and urgent notifications.
OS alerts
Calls, messages, jobs, and payments surface through the operating system instead of hiding in a tab.
Keyboard-first desk flow
Search, open a record, mute, hold, transfer, and write notes without slowing the front desk down.
Window memory
The app remembers workstation layout so dispatch, CSR, and owner desks can each keep their preferred view.
Answer, search, transfer, and follow up from one persistent workspace.
The desktop app is designed around the front desk loop: caller context first, call controls always visible, and every follow-up attached to the record.
Caller identity and job context are visible before the call is answered.
Transfers include context so the next person does not ask the customer to repeat it.
Messages, payment links, and notes are created from the same record after hang-up.
Managers can still use the browser; phone-heavy seats get the native shell.
Use each surface where it is strongest.
Thorbis in the browser is still the full product. Desktop is the same product wrapped for the phone-heavy seats.
macOS and Windows, tuned for real office desks.
Install it where calls are business critical first.
Start with the desks that answer customers, route technicians, collect payments, and coordinate schedule changes.
Install Desktop on the main CSR and dispatcher workstations.
Sign in with the same Thorbis account used in the browser.
Allow microphone, speaker, and notification permissions.
Place a test call, navigate the dashboard, and verify the call stays up.
Pin Thorbis Desktop to the taskbar or dock for the team.
Native convenience without loose desktop habits.
Desktop follows your existing Thorbis roles and workspace access. Signed releases update in the background, with restarts held until the call state is safe.
Practical answers for deciding where Desktop fits.
Is Thorbis Desktop a separate product?+
No. It loads the same Thorbis account, data, permissions, jobs, customers, invoices, and communications. The native shell adds call resilience, OS notifications, and desktop window behavior.
Should technicians use the desktop app?+
No. Technicians should use the field app. Desktop is for CSRs, dispatchers, office admins, and owners who work from a computer and handle calls.
Can the office still use Thorbis in the browser?+
Yes. The browser app remains the full Thorbis experience. Use Desktop on seats where calls and notifications matter most, and use the browser everywhere else.
Does the app update automatically?+
Yes. Signed builds check for updates in the background and apply them when the app can restart safely. Updates do not interrupt active calls.
Where the desktop phone is headed.
Persistent desktop softphone
IN DEVELOPMENT · Q3 2026Answer and place business calls from a softphone that stays put as you move between jobs, customers, and tabs.
Softphone and personal-phone routing
IN DEVELOPMENTRoute business calls to mobile or desk phones with clear caller identity, so techs use their own phones without giving out personal numbers.
Physical phone support
PLANNEDUse desk phones and SIP hardware right alongside the softphone, so the front desk keeps the handsets it already relies on.
Updates should respect live customer work.
Native software needs a clear rollout posture, especially when the app supports calls and front-office handoffs.
STABLE
Default channel for customer-facing desks that need predictable updates.
PREVIEW
Early channel for internal review, pilot branches, and workflow validation before broad rollout.
EMERGENCY HOLD
Update restarts pause when an active call or customer handoff is in progress.
Put the native phone on the desks that answer customers.
Reserve early access, put Desktop on the desks that answer customers, and send technicians to the field app.