Plyo vs Ruby for gym inquiries

Decide when reception should step in

Ruby says you can forward all calls, selected calls or use its receptionists as backup. [1] Our recommendation is to consider that approach when your gym needs human call coverage around an existing team. Specify the moments you want covered: a coach teaching, the desk handling arrivals or the period after your staff leave.

Make a coverage map that distinguishes calls, website inquiries and texts. For each channel, identify who receives the initial inquiry and who owns a request that needs follow-up. Ask your staff which interruptions they want help with. A clear answer makes it easier to evaluate a service against the work you need done, rather than the broad label of receptionist.

Follow a website visitor through to the next step

Use the fictional Northstar Performance for a sample website journey. A parent asks about an assessment for Morgan, shares the athlete's sport and wants a time after school. Decide what you expect the conversation to accomplish. Is the goal to collect an inquiry for your team, to connect the parent with someone or to complete an appointment booking during the exchange?

Plyo's website chat answers parent questions and collects the parent's mobile number to book. Confirmations and reminders go by text. It identifies itself as the gym's virtual assistant in every first message and names the gym. It uses the athlete's name, age and sport once shared, answers the actual question first and asks one useful question at a time.

Ask to see the parent's experience after the website conversation ends. Check where the contact information went and who is responsible for the next message. Review the wording of the next step: a request awaiting staff action and a confirmed assessment need different explanations. Set that expectation before the demonstration so you can assess the result consistently.

Verify scheduling with your actual assessment calendar

Ruby's FAQ says its team reviews your preferred online calendaring system before scheduling appointments. [2] Bring the calendar you actually intend to use and ask for that review. Include the appointment type, eligibility rules and the instructions the parent should receive. A scheduling demonstration is most useful when it follows the same path your families will use.

Plyo requires GoHighLevel and uses the gym's live calendar availability. It checks the slot again before booking and says booked only after the calendar returns an appointment record. If the slot was taken, it explains that and offers the next open times. A calendar timeout never causes a second appointment. Those are useful behaviors to include in a review of your booking process.

Also test what happens when the parent changes plans. Plyo protects the original appointment until the replacement is confirmed and confirms cancellations only after a verified status. Choose the person on your team who will review unresolved appointment issues. Ask them to inspect the calendar after the demo, so the evaluation includes the view of the staff who will prepare for the assessment.

Give alerts a clear destination

Ruby describes taking a message, sending a caller to voicemail or transferring to another person when you are unavailable. [2] Decide which outcome you want for different inquiries. For a new family, be explicit about who should return a message. For a conversation already being handled by a coach, agree on where a new request should go.

Plyo alerts the gym's escalation contact by private text when a parent asks for a person, then waits for explicit hand-back. It also steps back when staff reply in GoHighLevel. Owners and staff each have private threads with booking receipts, alerts and approval requests. Text Plyo to try the parent inquiry demo and book a call with the team to discuss that handoff.

Frequently asked questions

Related

• compare
• plyo vs smith ai
• plyo vs hiring a front desk