The workflow to solve
Different applications may describe the same customer through different identifiers and relationships. That becomes an operational issue when an order is attached to an obsolete account or a service agent cannot determine which subscriptions belong to the caller.
A practical software boundary
Define the authoritative customer and account records, then document how each consuming application references them. The Central Product and Customer Repository and Telco CRM provide a product starting point for that discussion.
What the design should demonstrate
A useful delivery slice is one complete customer journey, with duplicate handling and relationship changes included. The acceptance evidence should show that the same customer context survives the hand-off between applications.
- Map source identifiers before merging records.
- Assign ownership to shared customer attributes.
- Preserve the relationship between accounts and subscriptions.
- Test account restructuring and contact changes.