Jump to content
Vodia PBX forum

Scott1234

Members
  • Content Count

    39
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Scott1234

  • Rank
    Advanced Member

Recent Profile Visitors

879 profile views
  1. Awesome ! will it require a PBX update or is it all ZoHo side with being published.
  2. No we normally have buttons setup with nice easy to remember names for login / log out functions or agents are just permanently logged into groups. So they have no need or want to remember a number code. Using the group name would be far more intuitive option for a user like how hunt groups and agent groups work when they dial up the phone. Maybe the settings controls for this could be embedded into the 'Outbound Calling' tab of the agent group setup. To allow for customisation of the call back name.
  3. Hi, I feel this to be strange behaviour and put forth for your consideration for tweaking the operation. When using the call back feature if the agent hangs up the call first and or does not let the menu play out to the 'press #' to check the rest of the list the system will keep calling back even if there is no more calls in the list. Can it not just assume the operation as being closed if no further calls are in the list no matter who hangs up? Also, at the moment when a call back operation happens the caller ID comes up as *55xx(xx = agent group number) and wont present any group name identification. Would it be possible to display the agent group name maybe annotated with 'CALL BACK' or some thing similar such as "CALL BACK (XYZ AGENT GROUP name)" so end user has some idea of what type of call back it might be verses seeing the star code only? Thanks
  4. Just posting again to show this is super important and so it does not fall away into the abyss, any kind of ETA for this ? ZoHo have now added phone bridge into other Zoho products as well, Zoho One, Zoho Recruit and Zoho Mail along with CRM. It's a great selling feature to customers to be able to say the PBX can integrate and support the full Phone Bridge feature set.
  5. I would have thought agent group vs auto attendant to distribute would be good but the issue is it needs to be super simple for the end use, the request mainly comes from small business so it's not large call flow volume. The use case here is super simple, example being. Office is closed for x-mas party etc, admin staff want an easy way (Star Code) to re-direct all incoming calls to the Domain i.e user DID's + main business lines to a specified exit point that might only be known on the day/hrs before so manual input would work best. That way they don't have to rely on the staff forwarding their phones. It would be nice for it to use the agent group type feature set as its base of operation to take advantage of call queueing with multiple exit points if desired and the press 1 to connect option for agent exit point hunting. Most times these would be mobile exit points so you don't want mobile voice mail to answer the call. But for it to work like that it would need to be simple i.e, starcode -> domain redirection menu -> input destination/s -> set on/off/clear etc. Which would intern login a virtual extension to a virtual agent group with basic settings as mentioned above. My thinkings
  6. Hi Team, Did a search but could not see any discussion. I don't see any doco on the "Call redirection" setting under domain settings yet. I am wanting to know if there is a hidden star code not yet published where the user can dial it to set the forward destination for the whole domain like with the *80+hunt/agentgroup option.
  7. I don't see Vodia in the Phone Bridge Providers list on ZOHO, I am guessing the way phone bridge works has changed since you built? What can we do to get it in the list ? I really need to get it going for a large client.
  8. I am trying to get this to work, it connects and I get the green tick on the user level login on the pbx. But nothing is logged in Zoho or any pop up's, thoughts?
  9. I understand what you are saying, but what I am saying is this has changed in operation from previous versions. Which is effecting how my customer agent groups are working. Can you confirm if it's changed ? like i said previously all additional agents would ring when this stage was hit and thats the function I need back.
  10. Sorry I thought my first post was clear, I all ways find it hard to convey stuff here to be as simple as I can the previous versions did the following and had done so for years. Agent group, 'After hearing ringback for (s)' ... include the following additional agents Previously this would ring all additional agents defined in this box at the same time so the call gets answered quickly. But now it's been linked to follow the agent selection settings, meaning it might only be doing 1 agent every 5 seconds or what ever your settings are set to instead of blasting the whole group once the timer had got to that point.
  11. I know I have my other agent group topic; I am going to test that today at some point since going to the latest version, been super busy. Something that has 100% changed with the latest version, but changed somewhere from 57.3.2 was the logic of the setting After hearing ringback for (s) not sure if it was intentional? Example, • Customer may have any number of logged in agents at any one time • Customer has a number of extra agents as part of the, All agents for this ACD including the main agents, these extra agents typically never login. • Customers were using the 'After hearing ringback for (s)' to call the extra agents in, previously this setting would allow for all extra agents defined here to ring at the same time so the call got answered quickly, now it follows the logic set out in the Agent selection settings. I thought the previous logic made sense as if I wanted the 'After hearing ringback for (s)' section to follow the agent selection logic I would have just programmed them in as logged in agents to follow the ring order, now if I want to add in a lot of agents in one go I have to divert off to another agent group that has them all logged in, this makes it more messy as before I could contain it all in one group. Maybe an extra option is needed to control how that works now? or remove it from that logic. Thoughts?
  12. I will give it a test laster and let you know .
  13. I have messed around with the Zoiper stuff for a while and no matter what I do when I provision from a QR code it populates everything correctly except the username field, its all ways inputting "4789" as the 'Account name' and 'user name' in the phone app (iOS). If i update the username manually it connects no worries. I have also deleted the oem Zoiper profile and tried a bunch of stuff there with no success. Any ideas?
×
×
  • Create New...