A university finance copilot tells a student one balance, and the customer service copilot tells an advisor a different balance for that same student. What should the design share across the two apps?
Select an answer to reveal the explanation.
Short Explanation
When two apps describe the same student, you want them to use the same balance. Share the student and the balance so both copilots answer from the same figures; sharing only the name leaves each app with its own number.
Full Explanation
Customer Service and Finance are describing one student account, so contradictory balances indicate that the copilots are not sharing the record that matters. Share the student and the balance so both copilots answer from the same figures. A private prompt in each copilot may make each one insist on its existing calculation, but it does not reconcile the numbers. Sharing only the student name while Finance and Customer Service keep separate balances preserves the split that caused the contradiction. A billing article that explains how balances are calculated but reads neither live app can explain the policy, yet it cannot provide this student’s current balance. The shared balance should be the figure Finance treats as current for the student, and Customer Service should read that figure rather than keep a separate copy. Fluent explanations of a calculation do not help an advisor who sees the wrong number. Exam caveat: sharing the student and balance does not require retiring either copilot; each app can keep its own conversation as long as both use matching figures. Practical check: choose one test student, compare the balance stated by both copilots, and confirm that it matches the finance figure for that student.