tiagostutz / chimpassist Goto Github PK

Add support for users and attendants leaving a offline message to each other, with the corresponding information clear.

The endpoint base address will be passed as an environment var. The chimp assist user will then implement his own statistics endpoints, but following the spec in README.md.

In the customer "info" tab, implement the call to the /chimpassist/:customerId/contactInfo,/chimpassist/:customerId/additionalInfo and /chimpassist/:customerId/statistics and render the information following the render options described in README.md.

If the chat is opened and the user changes his status, the list is updated but the chat not.
The chat should capture and handle this event either to update the status and messages

Documentar no README.md os endpoints e tópicos

In the customer info tab, on the Backoffice chat panel, put "plugin invoke hooks" for:

• customer contact info
• customer additional info
• online activity
• last 24 hours activity
• last 7 days activity
• last 30 days activity

The Chimp Assist user should provide services endpoint for each on of those, following the README.md described spec

The user sends a keep-alive with an assignment that the attendant is not aware of. The keep-alive is broadcasted to the attendant.
The session must be terminated or resumed. But sometimes it stays stalled

Implement on the server a "session supervisor" that will listen to chat messages and decide when it has to trigger a chat feedback collect on the frontend.
The ideia is that the feedback is triggered on the middle of the session, or when the user is idle for a short period, or after an amount of messages exchange, etc.
This will have implementation on the server and on the frontend; the attendant won't receive any feedback in the backoffice for now
Tip: use https://github.com/flaviostutz/ruller

When you open the Chat Station it will fetch last user's sessions. If the users connects to the last session, everthing will be fine, but if the users starts a new session it is duplicating the user on the Chat List pane.

If the user send a session-online event and there are no attendants online at that moment, it should keep retrying to start the session.

If the user started a session but had no messages it would not be present in MongoDB and this service will not bring them. Mix the sessions present on the MongoDB with the ones present on the local "hot" DB that may or not may have sessions with messages.

Implement a MQTT topic that receives commands on the BackOffice side and executes them. This way, third party components can send command to the BackOffice.
Example: an component that halts the attendant session if the total amount of time of that day has reached the limit.