-
Notifications
You must be signed in to change notification settings - Fork 10.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Livechat popout window for chat with website visitor #519
Comments
Ill be more than happy to test it! |
Is someone working on this already? |
Please, take a look at https://rocket.chat/livechat-demo.html using an anonimous browser window :) |
Anyway that I can test the backend of this livechat demo? |
@skyred the backend is the rocket.chat itself.. |
@skyred If you want to test the server like @sampaiodiego said its rocket.chat its self. Or are you wanting to test the receiving end of the live chat, as in actually getting messages etc? |
I want to test this either
|
1 is not possible without re-building. Default configuration of our build does not include the livechat package - and there is no way to 'enable feature' after a build for docker images For 2 -- @sampaiodiego... is it possible to route messages to a specified registered user for these sort of tests? |
actually, only online users with
|
1 Cloud team manger/admin set operator flag for team users at the plan? |
So, I made myself an operator, livechat is set up. But when someone writes to me on livechat, I cannot see the message. |
@ic5y the current command to make an user an operator is the following: db.users.update({
username: 'SOME_USERNAME'
}, {
$push: {
"roles.__global_roles__": {
$each: ['livechat-agent', 'livechat-manager']
}
},
$set: {
operator: true
}
}) |
hm, the new livechat interface comes up, but when a guest sends a message, i got an internal server error :/ |
please try access the /livechat URL in an anonymous window (or another browser).. there is a bug when using a session created before. |
okay thanks! its working now :) |
Just found this issue. Interesting, and can't wait to see it ship.. |
We will turn it into a standard feature this week! Stay tuned! |
Any updates here? |
Yes, it is almost there. :) Will be included on the next release, on monday. |
Live chat is so cool, but the demo doesn't work. |
it's working @llinzzi , I just tested .. did you get some errors? what happened to you? |
@sampaiodiego it works for Chrome, but not work for Safari.
|
ohh.. ok.. have to check it so. |
for those who are interested in livechat features, I'm working on livechat manager that you can check at #1683 any feedback are welcome |
This package is now part of the default distribution. |
Yay! And I thought it was for Monday 😳 |
Will there be such a functionality like "triggers" and other cool things like Zopim has? Whole backend management for handling customer who is online on your web page? Thanks for info. Great product! |
yes @david-strejc .. please follow the issue #1824 |
* Test appx build * Build appx * Add appx logo * Update yarn.lock * Remove appveyor cache temporarily * Update package.json * Attempt to fix sign error * Update electron builder * Just build appx * Change to x32 * Build only for appx * Use vs 2017 * Build everything (hopefully) * Build appx and nsis * Add appx assets * Fix color on appx * Add store logo and change saved artifacts * Restore cache in appveyor.yml
* Test appx build * Build appx * Add appx logo * Update yarn.lock * Remove appveyor cache temporarily * Update package.json * Attempt to fix sign error * Update electron builder * Just build appx * Change to x32 * Build only for appx * Use vs 2017 * Build everything (hopefully) * Build appx and nsis * Add appx assets * Fix color on appx * Add store logo and change saved artifacts * Restore cache in appveyor.yml
…ool-agent-name [Livechat] Fix agent joining on pick from guestpool
We started the package called rockectchat:livechat
See /packages/rocketchat-livechat
We should have many interfaces
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.
The text was updated successfully, but these errors were encountered: