Hello Rianna,
To add more context coming off of Robert's response - the customer would most likely experience a longer wait but it should not disconnect their session nor put them in the back of the queue. The wait factor though, if long enough, might make your customers feel disappointed or impatient and make them end (abandon) their session.
Apart from agent behavior, I would say the Alerting Timeout value on your Queue Settings and Agent Utilization may play a part as well. If an agent does not answer an offered interaction within the Alerting Timeout duration, it will create that No Answer scenario. The situation might be that in-between working on multiple interactions - which would be dictated by Utilization - an agent might have missed the timeout window leading to the agent seemingly declining an offer. Sudden increase in interaction volumes may also attribute to this, so I would advise to check on your customer activity and look for spikes across intervals.
------------------------------
Nico Feliciano
Genesys - Employees
------------------------------