3 results found
-
Allow Default Meeting Type at Router Level
Having a default meeting type set for each queue means that queues have to be duplicated for each meeting type even though the rules are the same. It would be much less overhead if the meeting type could be configured at the Router level so that queues could be used with multiple different routers. With dozens of queues, duplicating them for every meeting type isn't scalable at all. Having a default meeting type for the queue would be fine as long as it could be overwritten by the meeting type set at the queue level (if one is set).
9 votesYou can achieve this using our newly released feature to pass Meeting Type via Router URL and via JS API.
-
Specify meeting type when booking a meeting through ROUTER url
Smart booking links https://help.chilipiper.com/hc/en-us/articles/360053021254-Smart-Booking-Links makes it possible to specify the Meeting Type as a URL parameter for meetings.. but not for Routers. The Router meeting link should accept the Type parameter and then over-ride the default meeting type.
7 votesWe now allow passing of meeting type via the Router URL and via options in the JS API :)
-
Visual map
Having some type of way to visual routes similar to LeanData
1 vote
- Don't see your idea?