Ruby Virtual Receptionist Services vs. Zendesk Chat

Ruby Virtual Receptionist Services is well suited for a business that needs call screening and message-taking services. The service is expensive but if the user is willing to put a lot of time and effort into planning and scriptwriting, as well as call handling instructions, it may work well. Also, if there is not much information that must be captured by the receptionist, I feel this may be a better fit.

Incentivized

Zendesk Chat is suited for all the support teams that provide real-time assistance. Like if someone wants to block the debit/credit card, it is a high-priority case that needs real-time assistance. Whereas issues like close my account, and invoice request doesn't need real-time assistance, where Zendesk tickets support will be perfect.

• Call-out request "personal assistant services."
• Ruby Receptionist app.

Incentivized

• Extremely fluid chat interface allows for easy communication.
• It can be used directly on a website page or as a widget.
• Allows the end user to translate the chat into their own native language.
• Notifies you with pending chats via on-screen notifications and sound effects.

• Clarity in billing.
• Shortened hold times.
• Less transfer time from call to receptionist (between English and Spanish).
• Better training of receptionists to prevent certain things from being said to clients - decreases client confidence.

Incentivized

• Linking with a telephone, so the agent is only working on 1 channel at a time
• More simplified way to create and use templates
• Link users who may have provided us a new/different email from what we have on file for them

Due to staffing issues, we have temporarily stopped offering chat as an available channel. We're also interested in the best ways to integrate chat with our FAQs and AI to provide quick responses, either during off-hours or prior to speaking with a live agent. I've also found that reporting is rather limited where some of the interesting and useful data made available and visible during the chat cannot be pulled post-chat; it would be great to pull a high-level report so we can analyze this data.

Getting assistance and/or troubleshooting anything with Zendesk can be quite frustrating. In my years of experience with Zednesk, I have almost never found the answer to my question without going through multiple articles, ultimately getting frustrated and reaching out to our contact for more assistance. So for a consumer, the support is not as relieving as Zendesk Chat is to our customers in getting the questions answered by us.

Incentivized

We switched over from Answer First to Ruby Receptionist because we wanted a more full-service answering service. We wanted to be able to call out using our business number as well as text in and out. We also really liked the "call-out request" feature as it freed up our time and allowed Ruby to handle minor client communications, etc.

Incentivized

I prefer Zendesk Chat (formerly Zopim) over Talkdesk, as it provides customers with written proof of their conversation and customers are able to rate the conversation once it is done. Also, it's easier to find a previous conversation in Zendesk Chat (formerly Zopim) than in Talkdesk.

Incentivized

• Increased efficiency.
• NEGATIVE ROI.

Incentivized

• Positive impact - Compared to our old system, this newly updated system provides features and functionality that has increased our agent productivity and provided customer insight like we've never had before. This has resulted in fewer hold times and higher customer satisfaction.
• Negative impact - Our reporting team still struggles with obtaining the right information from time to time with the chats. This leads to loss of productivity and more resources dedicated to reporting.
• Positive impact - Due to Zopim's embed, we are able to more successfully place them on the appropriate self-service portals and pages, reaching a larger audience, and being more readily available to answer our client's questions. This has resulted in an increase in our self-service portal usage, driving down the phone and email support channels, which in turn reduces support costs.

Incentivized