Omnichannel CRM should preserve the relevant customer, issue and next action when a conversation moves between channels or people. Start by testing identity matching and a handover together. A connected channel is useful only when the receiving colleague can identify the right record, understand the context and continue the work without guessing which conversation belongs to which customer.
A person may use one contact detail on a website and another in a later message. They may also ask about a different issue from the one already attached to their record. Write those cases into the requirements before assessing an apparently seamless demonstration. The useful question is whether the system helps the team make the correct association and retain responsibility.
The original continuity test below uses fictional contacts and cases. Narrow product examples come from Microsoft’s Dynamics 365 channel and record-identification documentation, retrieved on 24 October 2026. Broader selection belongs with choosing a CRM and business systems.
What does adding a channel involve?
Microsoft’s channel setup pattern starts with an account and requirements at the channel provider. Microsoft then attaches the configured channel to a workstream. The channel overview describes these distinct steps. Record the intended channel, workstream and responsible configuration owner before discussing the customer’s complete journey.
Microsoft documents a handshake-data exchange between the application and channel provider. Keep the required configuration in the technical implementation record, with credentials handled through the authorised private route. The business acceptance sheet can identify the relevant connection and owner without reproducing secrets.
Microsoft says specific channel features have licensing requirements. Microsoft also notes that non-Microsoft channels need their provider subscriptions. Check the proposed combination directly before assuming that a product demonstration establishes availability for the intended account or market. Keep that admission question separate from the conversation-continuity test.
For the fictional exercise, choose only the channels relevant to the actual brief. A smaller, well-defined journey is easier to inspect than a demonstration covering every channel a vendor lists. Write the customer entry point and the expected receiving role for each chosen route.
How does the conversation find the right customer?
Dynamics 365 can use preconversation answers to search account or contact records. The record-identification guide describes matching through fields such as name, email and phone. Decide which fictional values will identify the test contact and retain the expected record identifier separately from its display name.
Microsoft limits this documented search to records with the active status code. Microsoft says custom status codes prevent this record-identification behaviour. Record those qualifications with the proposed configuration. A record that exists in the database may still need investigation if it does not satisfy the documented matching conditions.
When several records match, Dynamics 365 does not link a record to the conversation. Include that ambiguity in the test instead of demonstrating only a unique email address. Ask the receiving colleague how they would resolve the uncertainty and retain the decision required before associating the conversation with a customer record.
| Fictional continuity case | Expected review question | Evidence to retain |
|---|---|---|
| One matching contact | Is this the intended customer? | Matching input and linked record identifier |
| Several matching contacts | How is ambiguity resolved? | Unlinked result and responsible review action |
| Existing customer, different issue | Is the attached case relevant? | Customer identity and selected case |
| Conversation changes channel | What context reaches the next colleague? | Channel, record references and useful history |
| Escalation to a person | Can the receiver continue the work? | Summary, linked record and next owner |
This is an original acceptance matrix. Define the expected result for each row before observing the configured system.
Include a separate authorisation question in the brief: which information may the representative disclose after the record is identified? Define the evidence your process requires for that decision and ask how it is demonstrated. Matching a fictional contact and granting access to sensitive account information should each have a clear acceptance requirement.
Which issue should remain attached?
Dynamics 365 can automatically link a customer’s single active case to a conversation. The representative can manually change the linked case when the customer raises another issue. These documented behaviours make case selection a separate review point from customer identification.
Prepare a fictional contact with a known existing case, then ask about a different issue in the exercise. The receiving colleague should explain which case is relevant and how they establish that association. Keep the customer and case identifiers in separate columns so a correct customer match cannot conceal the wrong issue reference.
Ask what information the next person needs to act. A concise summary can identify the question, what has already been checked and the next responsibility. Review that content for usefulness rather than assuming that a long conversation transcript automatically supplies an effective handover.
Original two-channel continuity exercise
Create fictional Contact A and Contact B in a separate test environment. Give them deliberately similar names and distinct invented contact details. Prepare one existing case for Contact A and a second sample issue that should be handled separately. Record the intended matching inputs and case decisions before starting the conversation.
Run the unique-match case first. Ask the receiving user to identify the customer and issue, then explain the next action. Retain the matching input, actual linked identifiers and the information available to that user. Use the result as the baseline for the more difficult cases.
Next, run an ambiguous input that could match more than one record. Inspect whether a record is linked and ask how the user resolves it. Record the actual outcome and any additional information needed. The proposed process should make the uncertainty visible long enough for an authorised person to decide it.
Then move the fictional enquiry through the selected second channel or handover route. Ask another representative to continue the work using the context they actually receive. Capture missing information as a specific requirement, such as an absent issue reference or unclear next owner, rather than a general comment that the channels feel disconnected.
Finally, repeat the case-selection check for the different issue. The acceptance record should show the customer match, relevant case, useful handover information and person responsible for the next action. Keep platform, edition and configured channels with the observations so another reviewer can reproduce the exercise.
For a related channel decision, see WhatsApp Business. To discuss the actual customer journey and remaining continuity questions, get started with the test matrix and intended channel routes.
For the channel-identity test, include two people with similar display names and one person contacting the team through two channels. Ask the reviewer to explain each proposed match using the available evidence before combining records.
By Spout Team. AI-assisted drafting by Codex using the linked primary documentation.