Phone support is available on upper-tier packages, but not a default option with our VPS plans.\u00a0Our answer to real-time interaction is our livechat which is easily accessible via your Pagely dashboard. Throughout our experience in being the first to serve this market,\u00a0we've found our ticketing & chat systems<span style="font-weight: 400;">\u00a0are the best solutions for both parties to efficiently manage communication. This allows for smoother hand-offs and\u00a0ensures everything is well documented and accounted for.<\/span>\r\n\r\nThere's a general understanding that providers whom do offer phone support staff their phones with Level I technicians who serve as a proxy to creating a support request for Level II techs. This\u00a0creates\u00a0barriers to their core support squad and\u00a0ultimately extends the wait times for reaching a proper resolution. If it's a critical issue resulting in an outage, every second is paramount, affecting your brand's perception, potential sales and bottomline.\r\n\r\nWe eliminate this support tree by employing core engineer experts exclusively\u00a0whom\u00a0our customers can\u00a0interface with directly via\u00a0one of two standard channels mentioned above. Additionally, a dedicated Slack channel is a third option customers can purchase with us. Our <a href="https:\/\/pagely.com\/support\/">support page<\/a> lists all of our support avenues and availability.\r\n\r\nWe serve thousands of customers via these support channels daily which enable us to deliver our service at an affordable price in a scalable way. While having a phone number can be an initial comfort,\u00a0once customers are able to experience\u00a0our renowned WordPress-specific knowledge and remediation skills first hand, they can finally relieve their inherent worries around keeping their WordPress site steady.\r\n\r\nFor more information on our support philosophy, read what our CEO wrote in <a href="https:\/\/pagely.com\/blog\/mitigating-the-support-concerns-of-clients-without-resorting-to-the-red-phone-approach\/">this blog post<\/a>.