Choose a field sales CRM by testing territory ownership, a complete visit record and what happens when a disconnected device reconnects. Treat these as separate questions. A territory map does not prove offline access, and a record saved on a phone does not by itself show what the office can see.
Use a representative journey before comparing feature lists. Identify which customer information a salesperson needs away from the office, what they should capture during a visit and who owns the next action. Then ask the demonstrator to perform that journey with connectivity deliberately removed in a test environment.
Dynamics 365 Sales provides documented examples for territory structure and mobile offline work. The original worksheet below connects them into an evaluation scenario. It keeps the documented product boundaries visible while giving your team a practical way to investigate reconnection and competing edits.
How should territories reflect the work your team actually owns?
Dynamics 365 Sales territories can represent a geographical area. Sales territories can also represent an industry or product line. Start by choosing what the territory means for your organisation, using Microsoft’s territory setup guidance. A geographical patch and a specialist product responsibility may overlap operationally, so a map alone will not resolve every ownership question.
The territory form includes a Manager selection. Write down what that manager is expected to decide: allocation, reassignment, follow-up ownership or another defined task. Then compare that expectation with the available configuration. A populated manager field is a starting point for accountability, rather than proof that every lead is automatically routed.
Microsoft’s territory guidance says the same user cannot be allocated to multiple territories. Its guidance describes creating a larger territory containing existing territories when a user needs a wider area. Test that documented approach against your intended structure before importing a list of people who appear in several local spreadsheets.
The Parent field places a territory beneath a selected parent territory. Draw the proposed hierarchy on paper first. Ask the business owner to identify who handles a customer that moves between areas and who handles an opportunity requiring a specialist. Record the agreed answer even if it needs a separate assignment rule beyond the territory structure.
What can the salesperson use while offline?
Sales Hub on Dynamics 365 for mobile can be used offline during intermittent connectivity. Microsoft requires an administrator-associated mobile offline profile before a user works offline. These are explicit prerequisites in the Sales offline guidance, so request the proposed app and profile configuration during the demonstration.
Offline lookup fields can reference only downloaded records. This is a useful test case for field work. Include one customer that the profile has downloaded and another that it has not. Ask the salesperson to record the outcome against each, including the exact point where a required relationship cannot be selected.
Microsoft states that custom fields of all types are available offline. Availability of a field does not remove the need to test the related data and the action around it. A custom visit field that refers to a customer still needs an applicable customer record, an understandable entry process and a clear owner for incomplete information.
Microsoft’s offline action matrix includes Appointment records. Inspect the permitted actions for the actual record type used in the proposed visit design. Ask the demonstrator to show the capture route on the phone rather than inferring it from a desktop view. The matrix distinguishes record types and actions; it is more specific than a blanket “works offline” claim.
Business process flows are not supported in Sales mobile offline. Therefore, separate the salesperson’s offline capture task from any process-stage movement the office expects afterwards. Ask how a visit with a pending next step is recognised after reconnection, and retain the observed answer as part of your decision record.
Which evidence belongs in a field-visit record?
Define the smallest useful visit handover in business language. A suggested record includes the customer reference, visit purpose, recorded outcome, next action, owner and relevant time. Decide which items are essential for your workflow, and distinguish a planned appointment from evidence that a particular visit outcome was entered.
| Requirement | Source-backed starting point | Evidence to request |
|---|---|---|
| Territory structure | Geographical or industry/product territories | Agreed hierarchy and manager responsibilities |
| Offline access | Mobile app plus associated offline profile | Exact app, user and profile used in the test |
| Customer selection | Lookups use downloaded records | Available customer and missing-customer outcomes |
| Visit capture | Appointment appears in the action matrix | Supported phone action for the selected record design |
| Next-stage handling | Business process flows are unsupported offline | Reconnection procedure and owner for pending work |
| Competing changes | Separate acceptance requirement | Before-and-after records and conflict handling observed |
Avoid treating a timestamp or a saved appointment as proof of physical attendance. If attendance evidence is a business requirement, define it separately and ask what information is actually collected. The immediate CRM selection question is whether the record provides a reliable, owned follow-up without ambiguous or duplicate customer information.
Original offline-visit dossier: one customer, two edits
This hypothetical exercise uses salesperson REP-A, territory North and customer CUSTOMER-A. All names and events are fictional. Use a separate test environment and test data, with a reviewer in the office role and another person performing the mobile journey.
Prepare the departure sheet. Record the territory, manager, salesperson, selected app and offline profile. List the expected downloaded customer records. Capture the starting value of one harmless test field on CUSTOMER-A, such as an internal visit-planning note. This creates a baseline for the later comparison.
Remove connectivity and attempt the visit. Have REP-A open the downloaded customer and enter the agreed visit outcome through the selected record type. Record what can be saved, which related information is selectable and what is unavailable. Test the missing-customer lookup separately so its failure does not become hidden inside the successful case.
Give incomplete work an owner. Suppose the second visit cannot be linked to the intended customer while offline. Ask the salesperson to follow the proposed exception process without inventing a duplicate customer simply to clear the form. Capture who will resolve it and how the office can distinguish an unresolved lookup from a completed customer handover.
Introduce a competing office edit. While REP-A remains offline, the office reviewer changes the same harmless planning field on CUSTOMER-A. Keep both intended values on the worksheet. This creates a deliberate conflict to observe; the worksheet does not predict which value the product will retain or how the user will be notified.
Reconnect and compare. Restore connectivity and follow the demonstrated reconnect procedure. Inspect the customer record and visit information from both roles. Compare the resulting values with the baseline, the salesperson’s input and the office edit. Record any warning, pending state, duplicate or manual correction that appears. Ask the administrator to explain the observed behaviour.
Prove the next action is visible. Give the office reviewer only the resulting records and ask them to identify the owner and next step. If they need a verbal explanation from REP-A, write down the missing information. Resolve that gap in the record design before extending the test to more territories or devices.
What should determine the selection?
Use the dossier to distinguish demonstrated behaviour, unresolved questions and proposed configuration work. Retain the app, version, profile and user context with the results. A product comparison becomes much clearer when each shortlist entry has been tested against the same disconnected visit and competing-edit scenario.
For the wider selection decision, read choosing a CRM and business systems. Keep billing handovers in the separate CRM invoicing guide. To discuss the field workflow, get started with the territory sketch, completed dossier and the reconnection questions that remain open.
By Spout Team. AI-assisted drafting by Codex using the linked primary documentation.