Compare two customer lists
Find records that appear in one or both lists before preparing a single view.
Illustrative idea, not a published runnable template. Grunt is prelaunch; live service is paused and live provider connections and outcomes remain unverified. The steps, providers, and outcomes below describe a concept.
When information is split across lists, a shared identifier can help reveal how records relate. Combine the sets, keep only new entries, or focus on records that already appear in both.
Actual availability depends on published steps, supported connections, permissions, and provider approval.
“Compare the lists using an agreed matching field and prepare the combined or filtered set the team needs.”
Clear tasks, with review where it matters.
Helps a team reconcile information from separate lists and focus on the records relevant to its next decision.
Matching depends on a reliable shared identifier. Check duplicate, blank, or inconsistently formatted values so unrelated records are not treated as the same person or item.
Select an illustrative task to explore its proposed role. No workflow runs here.
Identify the lists that need to be brought together and confirm what each one represents.
Use a shared identifier that distinguishes the same person, item, or event across both lists.
Choose whether the result should combine both sets, show only new items, or show existing matches.
Look for repeated identifiers, missing values, and records that could not be matched confidently.
Keep the resulting records together in a form the team can review or continue working with.
Identify the lists that need to be brought together and confirm what each one represents.
These are planning notes for the concept, not instructions for a currently available template.
Choose the two information sets and confirm they are appropriate to compare.
Select the shared identifier and decide how differences in spacing, case, or formatting should be handled.
Specify whether the team needs a combined list, new records only, or matches already known.
Check examples of matching, non-matching, and duplicate values before using the result.
Published templates and verified customer availability remain pending.
Explore the sample experience while launch details are being finalized.
View pricing status Explore the simulation