A university's recruitment copilot and student-service copilot have quoted two different application deadlines for the same program. Which design fits?
Select an answer to reveal the explanation.
Short Explanation
Two campus windows posting two dates will send the applicant to the wrong door. You orchestrate the recruitment and student-service copilots on one catalog so both return the same deadline. A third bot that picks between them is just another window.
Full Explanation
The recruitment copilot and the student-service copilot are both talking about one program date, and they disagree because each can answer from its own copy. Orchestrate them on one catalog, the single list of application deadlines, so both copilots read that catalog before they state a date. Recruitment can still greet an applicant and student service can still answer an enrolled student, but the date either one speaks has to come from that catalog. Private deadline lists refreshed in separate meetings will diverge again the next time only one meeting is held. A third bot that picks a deadline when the two copilots disagree adds a tie-break with no authority and leaves the two copies in place. Showing both deadlines and telling the applicant to use the later date publishes the conflict instead of removing it. Exam caveat: one catalog fixes the date the copilots are allowed to quote. It does not decide whether the program should change that date, and a catalog the copilots can edit inside the chat would recreate the split. Operational check: change the deadline once in the catalog, ask both copilots for that program, and confirm both quote the new date and neither quotes the old one.