Underwriters at a bank must review agent tasks that are waiting, and they do that work inside the loan's model-driven app. What should the design give them?
Select an answer to reveal the explanation.
Short Explanation
Put the in-basket on the underwriter's own desk, not in a mailroom down the hall. You give them an agent feed inside the loan app for the tasks that are waiting. A mailbox full of emails makes them leave the app to do the review.
Full Explanation
An agent feed is the place inside a model-driven app where a person reviews tasks an agent has queued. These underwriters already work in the loan app, so the design gives them that feed there, rather than a pile of messages somewhere else. Waiting tasks are work items, and the feed is how the model-driven app presents those items to the person who must act. A shared mailbox that delivers each task as its own email pulls the review out of the loan app and into an inbox they must sort by hand. A nightly spreadsheet on a file share outside the app is a delayed export, and a task that arrives at night has already left the app the underwriter is using. A policy chat that answers lending questions and does not present the waiting tasks helps with rules and does not give them the queue. Exam caveat: the feed is for review of agent tasks, not a replacement for the loan record itself; the underwriter opens the task from the feed and works the loan in the app. Operational check: queue a test task from the agent and confirm it appears in the loan app's agent feed for an underwriter, and that it does not appear only as email.