How to Run Coaching Workshops Without Hopin

Decide how to run coaching workshops without Hopin by choosing a suitable live room, designing a complete practice sequence and organizing the preparation and follow-through around it. The important output is something participants can examine, revise and use. A busy event interface does not establish that a workshop produced usable work.

Coachful is our #1 recommendation for the surrounding coaching workflow: preparation resources, participant work, actual feedback, sessions and agreed next actions. Use a live-delivery setup that meets the group's real interaction and access requirements. Do not assume that a coaching workspace supplies every event-production function or automatically provisions another provider's rooms.

The product formerly called Hopin Events is now RingCentral Events. RingCentral's August 2023 acquisition announcement concerns the Events and Session product lines, and current owner documentation describes group discussions and workshops in its Sessions area. Compare the current product fairly; it is not inherently incapable of a small workshop.

This guide develops a three-hour handoff workshop, a completed group output and an actual bounded trial. All named people, events, organizational data and results in the case are fictional. The workshop learns something useful while leaving a missed response and further capacity decision visible.

Choose the event setup around the learning task

A workshop needs a different design from a presentation. Participants need time to inspect a problem, try an approach, receive a response and revise their output. A lecture with a final question box may be useful teaching, but it does not provide the same practice opportunity merely because the event is labeled interactive.

Start with a small output. For a handoff workshop, “a revised handoff proposal with a trigger, minimum information, owner, response deadline and unresolved authority question” is clearer than “better collaboration.” It tells the facilitator what to teach, participants what to produce and the sponsor what remains a proposal.

Keep three roles distinct. Teaching explains a principle or example. Coaching invites participants to examine their assumptions and choices. Decision facilitation supports an authorized choice. A participant completing a strong exercise has not necessarily acquired the right to commit another department's time.

Current RingCentral Events guidance describes Sessions that can be configured for different interaction modes. Confirm the actual plan, permissions and requirements before comparing it with another setup. This article makes no invented claim about competitor prices, universal savings or missing workshop capability.

Design participation, information and authority together

Ask who is attending, what material can be discussed and what each person can influence. For a mixed-company group, a fictional shared case may be more suitable than an employee's confidential escalation record. For one organization, a real example still needs appropriate permission and an agreed audience.

Tell people what is being recorded or reported. A sponsor's request for themes and proposals differs from a request for named judgments about who resisted change. Do not describe a small-group contribution as anonymous if a distinctive role or example would identify the person.

The ICF Code of Ethics addresses agreements and information exchange for ICF professionals. Set the actual sponsor and participant boundaries before the event. A platform's export feature does not decide whether disclosure is appropriate.

Plan access before choosing an activity. W3C's accessible-events guidance covers usable materials, participation barriers, processing time and access to spoken and visual information. Ask about needed arrangements without demanding a diagnosis. A rapid spoken round, drag-and-drop board or compulsory camera can exclude a participant even if the main room opens correctly.

Offer meaningful alternatives: written contributions examined by the group, a slower route or a supported main-room exercise. An alternative that everyone ignores is not equivalent participation. Explain how its content will enter the shared output and decision process.

Complete the fictional workshop brief

Facilitator Saira and co-facilitator Ben work with nine existing coaching participants from a fictional organization. Sponsor Imani wants a clearer handoff from customer support to operations. The private workshop is included in an already agreed engagement, with no new public ticket or payment. It takes place on 8 June 2027 from 09:00 to 12:00 UTC.

The output is one testable proposal for nonurgent requests in a single queue. The group cannot change the company's urgent-incident route, promise immediate responses or commit operations capacity. Operations manager Arun must approve a trial. Imani agrees that the workshop report will contain the selected proposal, questions and subsequent authorized status, with no recording or ranking of individual attitudes.

Saira uses Coachful for original preparation and follow-through. The live room is the organization's already licensed external meeting service, whose administrator has verified nine participant seats, two actual host roles, usable captions, keyboard participation, text input and the intended room controls. Saira does not claim these capabilities as native Coachful breakout functions.

The joining note names the date, UTC time, private audience and actual live-room link, the preparation worksheet, the no-recording arrangement and the alternative participation route. Ben handles access questions at workshops@ben-support.example, a reserved fictional address, from 08:30 to 12:15 UTC on the day. Personal coaching topics go through each participant's individual coaching conversation instead of that administrative mailbox.

The host checks provider recording, transcription and caption-processing arrangements in advance rather than assuming “no recording” means no processing of any kind. The participants are told the applicable arrangements. Saira and Ben do not promise to prevent every possible personal copy.

Prepare a case with enough detail to work on

The original fictional exercise concerns a customer support agent who sends operations this message: “Client needs help with the report urgently. Please sort it.” The support record says the report is due on Friday, but the message omits the specific question, customer impact, requested decision and person responsible for replying.

Operations sees three possible tasks: correct a report, explain a result or approve an exception. The sender assumes that sending the message transfers responsibility; the receiver assumes it is an incomplete inquiry. The case gives no evidence of an actual emergency. The workshop must preserve the separate urgent-incident route rather than use ordinary queue practice for every risk.

The groups receive the same readable text case two days before the workshop. Each participant confirms access or receives an agreed alternative. The preparation question is: “Which missing fact prevents a responsible next action, and who would need to answer it?” No participant has to upload a real customer file or disclose a personal employment concern.

In the technical rehearsal, one account can enter the main room but not a breakout through its permitted device. Ben records the limitation and tests a main-room written route with that participant. The live plan retains group work where usable, with a full main-room fallback if a broader routing problem would leave people waiting.

Run the complete three-hour sequence

The intervals total 180 minutes. The design does not require all nine people to perform a full individual role-play aloud. Each person can contribute to the shared analysis or written revision, and the facilitator checks what was heard. Additional individual practice would require another staffed allowance.

All nine participants attend the main room. At 09:50, routing fails for two more participants. Ben spends two minutes on the agreed check, then Saira switches the whole cohort to the prepared main-room exercise instead of spending the thirty-minute block repairing optional rooms. The remaining twenty-eight minutes of that block begin with individual writing, followed by comparing proposals through the spoken or text route each person chooses.

The original aim survives, but the format changes. Saira explains that they will test one shared handoff in depth rather than claim three independent group outputs. Ben reads submitted text only with the contributor's permission and checks that the speaker's meaning is retained. The break still starts at 10:20.

Show the first proposal, real response and revision

The first shared proposal says operations will “respond immediately” to any support escalation. Saira asks what response means. Participant Luis says a support sender needs to know someone owns the request, but does not always need a solution at that moment. Participant Mae, who works in operations, says she cannot commit her whole team to instant resolution.

During rehearsal, Luis sends a more specific fictional request: “The client must submit Friday's report. They need confirmation of which approved report version to use. Please identify an owner and tell me when they can answer. I have not promised the client a same-day solution.”

Mae replies in role: “I can accept triage if you include the deadline, impact and the question, but I cannot promise today's answer without checking the analyst's availability.” Luis checks: “So acknowledgment and owner assignment can be an earlier step than resolution. The customer deadline needs to travel with the request.” Mae confirms that summary.

The revised proposal applies only to nonurgent requests received in the selected queue. It asks for the case reference, impact, exact question, relevant deadline and sender contact. For complete requests received by 13:00 UTC on a working day, operations would acknowledge ownership by 16:00 that day. Later complete requests would receive that acknowledgment by 10:00 the next working day. Working days are Monday to Friday; actual resolution timing is stated separately after triage.

Incomplete requests receive a clarification request and remain visibly incomplete; an automatic receipt is not ownership acknowledgment. The proposed measurement will show completeness as well as the acknowledgment rate, so missing information cannot disappear from the report. The existing urgent route remains unchanged.

Obtain the actual trial authority and capacity answer

At 11:45, participant Noor accepts responsibility for sending the proposal to Arun. Her request names the single queue, nonurgent scope, information fields, response deadlines and the need for staffed coverage. She asks for an answer by 10 June at 15:00 UTC. The cohort receives a status update by that time even if approval has not arrived.

Noor actually sends it after the workshop. Arun replies on 9 June: “I will not approve that response promise across all queues. For this one queue, I can provide a ten-working-day trial from 14 to 25 June with Mae covering first review and Deni as named backup. Each has a protected daily check slot. They will log incomplete requests separately. The urgent route stays as it is.”

He identifies the ordinary queue-review work displaced by those slots and confirms that its owner accepts the reduced review schedule for the trial. Noor confirms the narrower scope with Arun; he authorizes that exact trial on 10 June at 11:00. Saira's 15:00 update reports the approval, boundaries and review date of 28 June. It does not say that the workshop approved a permanent policy.

Mae and Deni receive the agreed instructions and confirm their actual roles before 14 June. The selected queue starts using the revised request fields. A proposal has now become an authorized trial through named answers and coverage, rather than through facilitator enthusiasm or a completed worksheet.

Read the actual trial result, including the miss

Ten requests enter the trial queue. Eight contain the required information and two are returned for clarification. Those two are still incomplete at the closing snapshot. Completeness is therefore eight of ten, or 80%. They are not omitted from the overall workload just because the ownership deadline applies to complete requests.

Seven of the eight complete requests receive an ownership acknowledgment within their applicable deadline. One arrives at 12:50 UTC and receives its acknowledgment at 09:20 the next working day, missing the same-day 16:00 promise. The acknowledgment result is seven of eight, or 87.5%. Reporting seven of ten would answer a different question and conceal the completeness distinction.

At the 28 June review, Mae explains that a clash with another accepted duty left the check slot uncovered on the missed day. Deni was also unavailable and no replacement had been agreed. The written backup arrangement had not produced actual coverage at that point. The team records the miss rather than recoding the request as incomplete.

Arun declines to extend the trial unchanged. He asks the service owner to decide whether to move the conflicting duty or adopt a slower promise before any further trial. That decision remains pending. Noor sends this actual status to the cohort and sponsor: the limited trial is complete, most complete requests met the ownership deadline, one coverage failure remains and no permanent response promise has been approved.

This is a mixed but usable result. The group produced and tested a clearer handoff; it did not establish faster issue resolution, customer satisfaction improvement or a permanent operational gain. Positive workshop feedback would not supply those missing outcomes.

Count the facilitator work and complete the feedback loop

Saira's planned allowance is 150 minutes of design, thirty of rehearsal, 180 live delivery, forty-five of follow-through and thirty of administration: 435 minutes. Ben has thirty minutes of rehearsal plus 225 minutes of event support from 08:30 to 12:15, including the live session: 255 minutes. The combined plan is 690 minutes, or eleven hours thirty minutes, within a twelve-hour allowance.

Actual follow-through takes Saira fifty-five minutes and administration forty, so her total becomes 455. Ben uses his 255-minute allowance. Combined actual work is 710 minutes, or eleven hours fifty minutes, leaving ten minutes of the 720-minute ceiling. Ben's live time is not added again on top of his support window.

Saira saves internal review notes on Noor's submitted trial account, then sends the actual agreed feedback through Noor's private client conversation: “The record separates proposal, approval, ownership acknowledgment and resolution. Keep the incomplete requests and missed coverage visible. The next action is an authority decision about coverage or the promise, not extending the pilot yourself.” Noor replies that she has read it and will wait for that decision.

The sponsor receives the agreed group report and confirms it addresses the workshop request. It contains no recording, private coaching notes or ranking of resistance. The substantive workshop feedback and trial review are complete; the next operational decision remains open and is not hidden inside an unlimited coaching commitment.

Configure the surrounding Coachful workflow deliberately

1. Define the private event and actual audience. A calendar entry, Program membership, community access and a resource grant perform different jobs. Check the actual participants and entitlements.
2. Create the real session. From the expanded calendar use Schedule, Group Session and Continue, then finish the event form. Entering a title alone does not create the session. Use the supported external-link option for the actual tested room.
3. Assign the original preparation. Check each intended participant can open the real worksheet and joining instructions. Do not rely on descriptive benefit text as an access grant.
4. Keep live-room controls explicit. Test the provider's actual host, captions, routing and recording arrangements. No automatic external breakout provisioning or recording transfer is promised here.
5. Plan summary handling. Coachful recaps are automatic by default when produced. Use Sessions, settings gear, Session AI and Session recaps to configure Approve before sending as appropriate; check session-type overrides. Review any actual recap and choose Send recap or Keep private. This is separate from the external room's recording settings.
6. Return feedback through a client-visible route. Coach review under a worksheet is private to the coach team. Send the actual agreed reply through the appropriate client conversation; do not mistake saved internal notes for delivered coaching.
7. Track the authorized next action. Preserve actual decisions, incomplete evidence and pending status. Do not assign another team's consent as a task the participant can complete on its behalf.

The demo images illustrate surrounding event and follow-through screens, not the fictional trial data or external room. Related guides cover group-coaching onboarding and continuing mastermind work. Compare the Coachful features with the actual workshop sequence.

Troubleshoot without losing the intended output

Routing fails. Use the tested meaningful alternative and explain the changed output. One shared deep exercise is not three completed breakout reports.

The group promises another team's resources. Record a proposal and obtain the actual authorized answer. A participant's job title alone is not proof that they can commit the team.

The sponsor asks for named judgments afterward. Revisit the agreed purpose and audience before sharing more. Do not convert a workload objection into a performance label.

The trial looks good only after excluding failures. Publish the actual denominators and statuses. Incomplete requests, missed acknowledgments and unresolved service decisions answer different questions and all matter.

Frequently asked questions

What happened to Hopin Events?

RingCentral acquired the Events and Session product lines in 2023; the event product is now RingCentral Events. Check the current product and plan rather than relying on old naming.

Does Coachful replace every event-platform function?

This guide recommends it for the coaching workflow around the workshop. Use an actual tested live setup for the interaction required, without assuming native breakouts, integrations or production capabilities.

Must every workshop use small rooms?

No. Choose the format that serves the task and supports actual participation. A written or main-room alternative should influence the output, not merely occupy excluded participants.

Can a workshop approve a new company rule?

Only through the appropriate authority. The case separates a proposed handoff, an authorized trial and a later decision that remains pending.

What should I measure after the workshop?

Measure the defined output and real trial criteria, including access problems, incomplete work, misses and workload. Attendance and positive reactions do not establish improved operational performance.