Open CRM after signing into an authorized company in the Flutter staff app. CRM does not require an existing deal or case to appear; customers are already part of the module. Current subscription, local role and authoritative server read permissions still apply.
Watch the lesson
Review a customer and next action
- Open the customer directory, search and load additional results as offered.
- Open a permitted customer to review available contact details, qualification, preferences, opportunities, activities and source context.
- Open a linked record rather than duplicating an opportunity or task.
- Use the offered editor or stage/action controls, review the current values and wait for the saved acknowledgement.
- Refresh/read the resulting record after an interrupted request before submitting another create or transition.
The phone profile presents supported mobile projections, not necessarily every web profile tab. Entity-read permission does not grant write permission. Editing, activity completion and deal-stage moves are separately permission controlled. Required stage fields, company ownership, selected relationships and current versions remain server checks.
Forms and private unfinished work
Editors use current allowed fields and options. Qualification does not establish marketing consent or a paid sale. Preference controls record an actual channel/purpose decision with evidence. Notes and their history remain within the permitted visibility scope.
The deal draft flow uses acknowledged server draft identifiers and revisions with an account/company-bound local journal. It is not an unrestricted offline customer database. Recover the original acknowledged draft before editing when required; retained identifiers cannot authorize another account's draft. An unknown create/transition outcome requires review of its original receipt/record rather than a blind repeated mutation.
Files and support context
Use the permitted file action; an attachment count or prior URL is not download authority. Switching company, token or account while a request is pending invalidates its original result. Private downloads follow the API contract and native file handling, not an arbitrary web redirect.
Mobile CRM cases/context are distinct from the independent Helpdesk destination, which has its own permission and data gates. Do not grant CRM access solely to expose service tickets.
Availability and troubleshooting
An older app or backend may not expose every implemented editor/action. Confirm both versions and any rollout restrictions. If a control is missing, check entity/field permissions, current company, plan capacity and server state. Report the record reference and app version without copying tokens or private customer data into screenshots.
See Native mobile workspace, Private deal drafts and CRM access.