Identifying Low Traffic Numbers
Low traffic numbers for VoiceAI are identified when the numbers receive minimal or no calls. Specifically, if there are fewer than two calls ever (excluding test calls before launch), the numbers are considered to have low traffic.
If the building is receiving no or low traffic you will be notified in a few ways:
- Clients who are live on voice, but not yet receiving traffic will receive an email letting them know that “VoiceAI Numbers Are Ready” with instructions to either publish or forward your numbers depending on your launch plan.
- In Voice Hub, you will have Action Items letting you know that you have low traffic on numbers. Additionally, you will see an amber status next to each vanity number, indicating low traffic.
If you are receiving traffic on some of your building’s vanity numbers, but not all you will see the building’s status as green and receiving traffic, but if you look at the Vanity Numbers page, you will see a breakdown of which properties are and are not receiving traffic in the “traffic status” configuration setting.
Why is it important to fix Low Traffic Numbers?
Getting traffic to your EliseAI vanity numbers is the first step to turning on VoiceAI. Without either publishing these numbers properly or forwarding traffic to these numbers, you have not fully configured your VoiceAI solution.
Troubleshooting and Resolving Low Traffic Numbers
There are a few main reasons why you may not be receiving traffic.
- If your launch plan is “Publish Numbers”:
Confirm that your Internet Listing Services (ILS) and property website administrator updated your published phone numbers to reflect the applicable EliseAI Vanity Numbers. Once they have confirmed the number has been updated, you can verify directly on the sites if you are seeing the correct number listed. Give the number a test call and confirm you are being routed as expected. Pro Tip: If you are configured to call the leasing office first, let the team know not to pick up or test the line after hours to ensure you are going straight to VoiceAI.
- If your launch plan is “Forward Traffic”:
Confirm that your phone provider updated your numbers to forward traffic to the EliseAI number. Please submit a follow up ticket or reference the instructions listed in this article about forwarding traffic. Once they confirm the numbers have been forwarded, give the number(s) a test call and confirm you are being routed as expected. Pro Tip: If you are configured to call the leasing office first, let the team know not to pick up or test the line after hours to ensure you are going straight to VoiceAI.
By following these steps, you can identify, troubleshoot, and resolve issues related to low traffic numbers for VoiceAI, ensuring that the system operates effectively and meets its intended goals.
Still not receiving Traffic?
If you’ve confirmed that your lines have been published or forwarded properly and are still not receiving traffic, check your Voice Hub configurations.
- See if you are electing to have your leasing office pick-up first in the Voice Hub. The “Who should pick up first” option would be set to “Leasing Office”.
- If that is the case, you will need to ensure that the “Leasing Office Number” is properly set up to receive calls. This number needs to be a direct line to the office that is not posted anywhere. AKA, this should not be a number that folks are using to call your office. This should be a dedicated line used only by EliseAI to dial your office. For more information about preventing call loops, see this article.
- Make sure that this direct leasing office number does not have a phone tree or any recording such as "thanks for calling... etc." A phone tree or recording will interrupt our pickup detection and the caller will end up connecting to that number instead of going to VoiceAI as overflow.