|
|
| Line 1: |
Line 1: |
| The purpose of this page is to provide ideas and examples for how features in this PRD might look and operate. '''These ideas aren't requirements.''' | | The purpose of this page is to provide ideas and examples for how features in this PRD might look and operate. '''These ideas aren't requirements.''' |
|
| |
|
| ==Interface ideas for contributors==
| | #REDIRECT [[Support/Live Chat/UI]] |
| *Settings panel for contributors
| |
| **Filters to control when contributors receive chat notifications. (Filter on keywords, tags, wait times, OS, Firefox version)
| |
| **Chat limit to control the maximum number of chats before new notifications stop.
| |
| *Minimalist chat toolbar (facebook style) or sidebar (gmail style) listing #sumo, current chats, and queue status. Rollover buttons should provide access to the user's status (away, available), a list of online users (roster), and a minimal dashboard. Clicking the latter button should take the user to the full chat dashboard page.
| |
| **Clicking a chat button on the toolbar should open a chat overlay on top of SUMO. This should be a streamlined experience with multiple chats handled well, minimize/expand buttons on each chat, and tools for editing.
| |
| *Chat dashboard showing current chats in the queue, status for the day, commonly used tags, most active and climbing contributors, and stickied threads in the live chat forum.
| |
| **If a helper chooses a specific chat from the queue, he/she should immediately join it if it's available. If it's currently being offered to another user, the helper should join it if and when the offer is rejected or times out.
| |
| *Notifications system to alert users visually and audibly of chat offers, chat invitations, private messages, and of users who seem to be ignored. If a user says >4 messages or goes >4 minutes without an answer, the notifications should become annoying. (blinking, beeping, flashing)
| |
| **If a helper is set to "Available" and is in fewer chats than his/her chat limit, the notifications system should send notifications about individual chats waiting in queue. Each of these should have Accept/Reject buttons and a timer until the offer expires. While an offer is active, no other helper is able to take that chat.
| |
| *Canned responses should look like they do now with Openfire.
| |
| *Tags should be entered as they are now (/tag tagname), but with autocomplete. Tags that can be automatically detected (OS, Firefox version) should be applied.
| |
| *The chat interface should be in all SUMO tabs and should stay in sync in each one (up to ten tabs at a time)
| |
| **Not a requirement, but this is how we envision an ideal implementation looking
| |
| *A window/overlay/tab containing an individual chat session
| |
| **There should be buttons for inviting another agent, transferring/ending the chat, text formatting (bold/italic), canned responses, and viewing extended chat information (plugins, extensions, other AAQ details).
| |
| **Both contributors and users should have a "Transfer" button that allows ending a chat and posting it in the forum. The user should have the option of putting the entire chat log in the post (in a collapsed section, of course).
| |