Customer 360 describes a combined view of customer information drawn from different sources. Start with a question that view needs to answer, then inspect what is present and what is missing.

Decide what the view needs to show

A service colleague preparing for a customer conversation may need different context from a marketer planning a campaign. Name the task before deciding which information belongs in the view. A longer list of fields does not explain how anyone should use them.

In Microsoft’s Customer Insights - Data documentation, unification combines customer sources into profiles. Its configuration includes choosing which columns to include, exclude or merge. That describes the named product’s process, rather than a universal setup for every customer view.

A fictional bicycle-shop view

Imagine a bicycle shop’s proposed view showing a contact record and a recent service booking. An older repair note is absent. These invented entries illustrate what the display can support and what someone still needs to investigate; they are not a tested software configuration.

Fictional view inspection
Item in the chosen viewWhat it supportsUnanswered question
Contact record displayedContact details are present.Are these the right customer’s details?
Service booking displayedA booking is shown.What work does the booking cover?
Earlier repair note absentThe note is not visible here.Is it available in the source?

The missing note does not establish that no earlier repair happened. Check the source and its relationship to this customer before deciding what the absence means.

Trace an unexpected result

Microsoft’s troubleshooting guidance recommends inspecting a customer card to verify which source records were deduplicated and matched. This is a product-specific inspection method, not evidence that a particular match is correct.

Write down the unexpected result and the unanswered question. Assign the investigation to someone who can inspect the relevant records.

Check the view in its working context

Ask the person who needs the information to find it in the place they actually work. Check whether the relevant record is available to that person, rather than assuming a demonstration proves everyone has access. Note any unresolved access question alongside the task it affects.

Where source or update information is available, retain it with the review. Decide how recent the information must be for the intended question. A contact preference and a service booking may need different checks; do not assign a universal refresh target without considering their use.

Use the view for the question it can support

Write down the question answered, the evidence used and the remaining gap. If the missing context matters to the next action, investigate it first. If a proposed addition has no clear use, ask what decision it would change before expanding the view.

Evaluate the work done with that information separately from the appearance of the profile. A populated screen does not by itself demonstrate better service or higher retention. Record the outcome you would need to observe instead of treating data consolidation as the result.