Can this work for government offices?
The service is more designed for smaller businesses than larger organizations and enterprises, but there are many government offices that find it to be a good fit. Here are some answers to a few additional questions we have heard from government entities that might be helpful:
- Our Terms of Use and Privacy policy are on our website, and we don't have an enterprise tier of support that would include things like signing separate legal agreements, filling out security questionnaires or going through other processes that might be normally involved with enterprise sales.
- The subscriptions are paid for by credit card (we keep our costs low by not invoicing for monthly service, which many government places have requested).
- The app isn't designed to handle multiple queues. Meaning, if you are trying to track different lines for various departments, you would generally need separate accounts/subscriptions. Here are some resources on how our admin tools work.
- The service isn't designed with CRM features or contact tracing features, if that is what you need. None of our reports allow for the exporting of phone numbers. It is designed this way as a security feature to protect the privacy of customers and ensure phone numbers are not used outside our system in ways that may not be authorized by customers.
- The service could slow down if you have longer lines where you would have 50+ on the list for longer periods of time. At larger amounts it could freeze, depending on your internet connectivity and the devices you are using, as each incremental person in the list can add additional load for the devices to handle.