As first advice, use the "roles" or actor names to keep the diagram cleaner and not mix up stuff like authentication in identifying the system mission.
In particular, you can have a visitor actor that can login/logout (some people have other actors inherit from that one, but it stays cluttered I'd prefer explaining that all logged in actors can disconnect in the text since diagrams are never dry) , and avoid all those nasty includes to login, past the login, the user is recognized in one or several roles according to the security/access policy. An actor has available actions, ofc he is in that role to access them. Anyway, an "A include B" means each time you do A you must do B as a part of A, so the diagram is incorrect if you have a session notion. So you just accompany the diagram with a table ascribing to each actor name its business name/role and how to reach that level of recognition (e.g. you need to login and have that level of permission).
For the rest, secondary actors are "secondary", so not important to a use case presentation from client POV, they can be left out of a higher level presentation, though they are ineteresting to introduce for design/lower phases of the cycle.
Just focus on "a use case has business value for its primary actor, who triggers it to gain that business value"
some use cases of your diagram might actually be two separate use cases, e.g. access updates is not the same use case for the client (just his own status) and the reception (be informed of warnings ? a huge set of status in sight so search and scroll tools, and maybe admin status to solve issues)
A use case diagram is about how external people (actors, so they could also be machines) use our system. In a computer based interaction this means two primary actors don't actually touch the same use case unless there is some kind of symmetric chat involved (unlikely). For human face to face relations it's different, you do have two actors interacting, but over/under the counter w.r.t. to a computer system that would implement the exchange. In most cases, you just get a single use case, that the company employee touches in response to the user queries (on the phone, physical in front of desk). Or there is an online service for clients to pose questions which is another use case.
In any case, you need to better define the boundaries of your system imo, are your employees part of it in this modeling ?
Maybe not, so you focus in the diagram on what your business brings to the clients (the whole point of these diagrams), regardless of current internal organization (secondary actors on right, design/problem solving issues). Then we can separately study how to build an information/UI system to help our employees satisfy those needs, which are separate use cases since they handle a base of clients.