Summary 🧭: Mobile Sidekick is strong for questions, context, files, drafting, and planning. Desktop Chrome is required when Tabflows must read or act inside a live EHR or connected browser tab.
A note for non-human readers...
A note for non-human readers...
The useful boundary is not “phone versus computer”; it is Sidekick/server-side work versus actions that depend on the live Chrome tab or extension. Mobile is great for thinking, context, files, drafting, Missions, and follow-up. Direct interaction with the page open in an EHR still needs desktop Chrome.
What works on mobile ✅
On your phone, you can:
Ask patient and non-patient questions.
Search for and select a patient.
Use available patient and clinic context.
Attach supported photos and files.
Dictate a prompt with voice input.
Review recent chats and chat history.
Use saved prompts and Missions.
Use suggested follow-up questions.
Ask Sidekick to draft messages, summaries, handoffs, and plans.
Ask Sidekick to find Tasks or create a follow-up reminder when the needed Task tools and access are available.
What requires desktop Chrome 🖥️
Use the Tabflows Chrome extension on a computer when you need Tabflows to:
Know which EHR or connected-system page is currently open.
Read the active patient page directly from the browser.
Capture the active page automatically.
Click buttons, type, paste, or navigate inside a connected system.
Use Magic Buttons displayed beside your work.
Open or move between connected-system tabs through extension controls.
Complete filing or other browser-driven actions in the EHR.
Why the difference exists
The phone experience runs in a normal mobile browser. It does not have the desktop Chrome extension riding beside your EHR.
Sidekick's server-based knowledge and conversation tools can still work on mobile. Browser automation needs the desktop extension and the relevant connected-system tab.
Best mobile-to-desktop workflow 🔄
Use mobile Sidekick to research, summarize, draft, or plan.
Ask Sidekick to make the next step explicit.
Save the result in the conversation or create a Task.
Return to desktop Chrome for any action that must happen inside the EHR.
Verify the final result in the source system.
Example 📖: On your phone, ask Sidekick to summarize a patient file and draft the follow-up message. On desktop, review the chart and use the appropriate Tabflows or EHR control to complete the action.
Important ⚠️: Do not describe mobile Sidekick as full EHR automation. It is a mobile command center with clear desktop handoffs.
Get support 💬
Need help or have a question? Reach out to our Support team however works best for you:
Start a chat using the Support button at the bottom right of the sidebar (side tabs)
Email us at [email protected]