We have a Chatbot Platform which supports Agent Chat as well. Whenever end user requested for an agent we have to show the Estimated Wait Time(EWT) for the End user. But we are struggling to get this Calculation.
We have 10 agents who are handling the user requests.
Can anyone help me with the formula to calculate the Estimated Wait Time(EWT)?
Related
I have question regarding if it is possible in azure to make an alert if a End-To-End transaction duration exceeds a certain value like 30 sec. I can clearly see if a end-to-end transaction take longer then 30 sec in application insights. But I can't figure out how to make an alert that notifies me if any transacation exceeds a certain amount.
End-To-End transaction example
If anyone knows how to do this let me know.
Thanks in advance!
I am doing a project where I need to send device parameters to the server. I will be using Rasberry Pi for that and flask framework.
1. I want to know is there any limitation of HTTPS POST requests per second. Also, I will be using PythonAnywhere for server-side and their SQL database.
Initially, my objective was to send data over the HTTPS channel when the device is in sleep mode. But when the device (ex: car) wakes up I wanted to upgrade the HTTPS to WebSocket and transmit data in realtime. Later came to know PythonAnywhere doesn't support WebSocket.
Apart from answering the first question, can anyone put some light on the second part? I can just increase the number of HTTPS requests when the device is awake (ex: 1 per 60 min in sleep mode and 6 per 60sec when awake), but it will be unnecessary data consumption over the wake period for transmission of the overhead. It will be a consistent channel during the wake period.
PythonAnywhere developer here: from the server side, if you're running on our platform, there's no hard limit on the number of requests you can handle beyond the amount of time your Flask server takes to process each request. In a free account you would have one worker process handling all of the requests, each one in turn, so if it takes (say) 0.2 seconds to handle a request, your theoretical maximum throughput would be five requests a second. A paid "Hacker" plan would have two worker processes, and they would both be handling requests, to that would get you up to ten a second. And you could customize a paid plan and get more worker processes to increase that.
I don't know whether there would be any limits on the RPi side; perhaps someone else will be able to help with that.
How long does it take for the google assistant agent to timeout and end/leave the conversation?
I configured a chat bot with actions-on-google where
The GA would ask user to choose which product to buy from a List.
Then the user locked the phone's screen
After a few minutes, the user reactivates google assistant again
User selects one of the product from the list by scrolling up the history
The transaction proceeds
I expected the app to exit the conversation after a certain duration, which then start a new session.
The session stays alive for 10 minutes. So, if you resume conversation within 10 minutes then it will continue in the same session.
As per my testing on Google Assistant and Simulator, if the conversation is paused for more than 10 minutes then the conversation ends and app exits.
5 seconds.
Source: Google's documentation
("Your response must occur within about 5 seconds or the Assistant assumes your fulfillment has timed out and ends your conversation.")
If there is a 5 second limit to receive the response, is there a limit to how long the response can be? We want to access longer form responses and then (hopefully) process the text response
It's actually 10 seconds or that's what this says.
I don't know if it's the same time for legacy actions or conversational actions.
I'm using REST GET calls from a google script to build a temperature profile of my house during the day. The function triggers every 15min. last_connection (and the rest of the data) will sometimes be the same 3-4 calls in a row, other times can be different each time for several hours running, suggesting variable rates at which the thermostat sends data up to the server.
Does anyone know what governs the thermostat's connections to nest.com or if there is a way to force a connection in order to get an up to date profile?
The thermostat connects to Nest's cloud under the following circumstances:
A 'significant' even has occurred (ie the furnace turning on)
A timeout has occurred (ie a scheduled check in appointment)
A thermostat will be considered offline if it misses its check in window, there is more detail on why that would happen in Nest's Troubleshooting Offline Status in the Nest apps support article.
You can force a thermostat to come online by sending a change to it, for example changing the target temperature will necessarily force the thermostat to wake up so the new value can be set, while awake the thermostat will update the cloud service with updated information. Forcing a thermostat to wake as way to get updated data from the thermostat is not recommended as you will run into an API rate limit designed to protect the battery on the thermostat. Charging rates on thermostats are rather limited, wake it too often and it will go offline for a while, annoying the user.
Rest assured, if the ambient temperature or humidity changes by a 'significant' amount, the thermostat will wake up and update the cloud service. The thresholds of what signifies a significant amount are harder to predict as they are partially determined by charging rate. If you want to know why that can vary, Nest has filed a patent which goes into great detail.
I implemented Pusher API in a live chat recently.
I launched a Startup package of Pusher yesterday. After 4 hours of being live, I receive an email that my account is reaching the cap on usage.
I logged in and looked at the stats, to discover that the Messages per Minute were between 5,000 and 20,000.
I don't understand how this is possible. I have around 100-150 connections open.
Why is the message count so high?
Armin
Found the answer myself! :)
Here is the link for anyone who may have the same problem:
https://pusher.tenderapp.com/kb/accountsbillingplanspricing/how-is-my-message-count-calculated
Basically, if you have 100 users subscribed into a channel, and 1 message is sent, it counts are 100 messages being sent since each user would have to be notified.
Bottom line is to properly filter your channels.