AgentDesk · prototype

Composer by last thread

The composer follows the last thread, the stage, and the status. It does not offer every send. If the last thread is an engagement and it came by email, the composer is email with booking. Scenarios below were laid out by Opus and Fable, then reconciled on this page.

  1. 1. Who owns itDone is closed. AI statuses stay quiet. Escalated, an open call, and a manual slot edit open a composer.
  2. 2. Which channelEmail, SMS, group SMS, or Quo comes from the last thread. There is no channel menu.
  3. 3. Booking or notSlot fields sit inside the composer only when this thread is about setting or moving the interview.

Notes

Not accepted. Accept when this scenario is final and needs no note.

No notes on this scenario yet.

    Still open

    1. No-show. This page shows a slot form and no message. The other pass would reply on the last channel and book in the same form.
    2. Reply before the slot is set. Email-with-booking has one primary, Book and send. A send that does not book yet is not on this page.
    3. Writing after a call. Call outcome can hand off to SMS or email. Whether the AI resumes on that send, or waits for the applicant, is undecided.
    4. Group booking. The slot is shown on the applicant. Who else in the group is booked, and who is told, is undecided.
    5. Manual reschedule notice. The icon sets the slot and does not open a message. Whether a notice goes out, and on which channel, is undecided.
    6. Needs info with one number. The ladder stays waiting until email and phone are both present.