Nviti's Flutter staff app is separate from the customer chat PWA and embedded chat SDKs. Use the release provided for your organization and sign in to your authorized workspace. No public Play Store or App Store availability is established by this guide.
Watch the lesson
Navigation follows access
The configured order is Chats, CRM, Helpdesk, KB, Forms, Bookings, Orders, Products, Settings. Destinations you cannot access are omitted. Up to five available destinations appear directly; with more than five, four remain direct and More contains the rest. An account with only Chats, CRM and Settings does not need an empty More menu. Settings remains reachable even when it is the only destination.
| Destination | Visibility and use |
|---|---|
| Chats | Current chat permissions and company access; inbox, search, filters, conversation history, authorized handover/replies |
| CRM | Current subscription/local role/server entity-read authority; an empty permitted CRM stays visible |
| Helpdesk | Current permission plus accessible ticket data; see Mobile Helpdesk |
| KB | Current knowledge role/summary gates, including the supported author path to an empty library |
| Forms | Current permission and company-scoped form data |
| Bookings | Current permission and company-scoped booking data |
| Orders / Products | Current permission and company-scoped data |
| Settings | Account/workspace controls including appearance |
A cached screen or hidden tab is not the server's authorization decision. The app rechecks original account/company/session during asynchronous work; changing accounts must not display a previous workspace's delayed result.
CRM on your phone
Review customers, their permitted context, opportunities and follow-ups. Open supported editor/qualification/preferences/file/history controls only where offered. CRM and Helpdesk remain independent. Record creation, edits, qualification, preferences and file operations still use the backend's plan, field, ownership and capacity checks.
Private mobile deal drafts retain unfinished work through the app's supported draft flow. Offline or interrupted work must not be interpreted as a successful server save; review saved acknowledgements and the resulting record on reconnect. This is not a blanket guarantee of offline writes across CRM, tickets, bookings or forms. Do not retry a create blindly after an unknown outcome.
Conversations and daily work
The inbox supports company selection, search and filters. Conversation history combines the app's refresh/live-update paths; reconnect and review message status before repeating a reply. AI handover, sending, attachments and history remain permission-controlled. A visible message and a provider delivery receipt are different outcomes.
Read published knowledge articles, review submitted forms, inspect orders/products and switch booking Calendar/Agenda views. Status-filter icon slots remain consistent so selections do not shift labels. Long labels and date ranges wrap rather than relying on a fixed small width. KB is the compact bottom-navigation label; article headings keep their full names.
Appearance and keyboard use
Open Settings → Appearance and choose System, Light or Dark. The choice persists across relaunch; System follows the device theme. Theme-aware brand marks use the original dotted Nviti logo: green on white for light, white on green for dark. Android launcher appearance follows system resources and can be cached by the launcher independently of the app preference.
Forms and bottom sheets account for keyboard insets and scrolling; close the keyboard or scroll to reach a lower action. Large text can use the accessible destination selector. Report clipped labels or unreachable controls with the app version, screen, text scale and keyboard state.
Releases and demonstrations
The supplied Android build with KB/splash refinements predates the new Helpdesk action extension. The latter requires matching server deployment and a new app. The recorded 30-second preview and 90-second walkthrough use real Android footage, fictional data and isolated real Laravel APIs. They include pending Helpdesk functionality and are not proof of production delivery or Apple-store readiness.
For customer-facing PWA installation and SDK embedding, see Mobile access.