Whereby Meeting Plugin for RISE CRM

Whereby Meeting Plugin for RISE CRM Overview & Scheduling Architecture

Whereby Meeting Plugin for RISE CRM is a CodeIgniter-based extension package, engineered for agencies and development teams operating RISE – Ultimate Project Manager & CRM to schedule and manage Whereby video meetings natively inside the CRM workspace. The module removes the operational bottleneck of coordinating client calls across external third-party applications by registering Whereby as a meeting provider through URL-based room links. In production agency workflows, it functions as the scheduling layer that binds date and time planning, invitee selection, and notification dispatch into a single CRM-resident routine, eliminating context switching between the CRM and separate conferencing tools.

Technical Specifications & Deployment Matrix

Meeting Scheduling Engine & Execution Pipeline

The core mechanism registers Whereby as a meeting provider inside the RISE CRM meeting module and binds URL-based room links to scheduled calendar events.

Execution begins when an administrator creates a meeting record through the CRM interface. The package captures the meeting definition — title, target date, and designated time slot — and passes it through the CodeIgniter controller layer for validation before persistence. Once validated, the record is written into the existing CRM data structures, and the invitation routine compiles the participant list, which can include both client contacts and internal staff members. The scheduling pipeline then dispatches notifications to every assigned invitee, so each participant receives the meeting details without manual coordination. Because room access is handled through Whereby room URLs, no heavyweight real-time media infrastructure runs inside the CRM itself; the plugin delegates the conferencing layer to Whereby and retains only scheduling, assignment, and notification logic within the CodeIgniter runtime.

Architectural & Functional Highlights

• Whereby Provider Registration: Adds Whereby to the RISE meeting provider options using simple URL-based room links, keeping the integration layer thin and avoiding complex configuration routines or third-party application dependencies.
• Multi-Participant Assignment: Supports simultaneous invitation of clients and internal staff members on a single meeting record, allowing mixed internal-external sessions to be scheduled from one form.
• Native Meeting Scheduler: Provides date and time selection with instant notification dispatch to all invitees, ensuring every participant is informed the moment the event is committed.
• Plugin-Section Installation: Ships as an uploadable archive that installs and activates directly from the RISE CRM plugin management screen, with a success message confirming correct deployment before activation from the options dropdown.

Agencies evaluating scheduling tooling on other platforms should note that architecture parity exists outside the CodeIgniter stack; for standalone WordPress deployments, the Appointment Scheduling System – Online Meeting & Booking Management – Calendly Clone delivers comparable booking and meeting coordination as an independent codebase rather than a RISE-resident module.

Production Implementation & Operational Resilience

Deployment follows the standard RISE extension path. An administrator logs into the CRM, navigates to Settings followed by the Plugins section, and uploads the distribution archive obtained with a valid purchase code. When the installation routine completes without errors, a success message is displayed, and the module is activated from the plugin options dropdown. This activation flow means the package inherits the CRM’s existing authentication, session handling, and permission boundaries rather than introducing a separate access layer.

Operationally, three prerequisites define the environmental boundary. First, the host CRM must run RISE v3.x or higher; the package is not a standalone script and will not execute outside the RISE runtime. Second, a valid Whereby API key must be configured before meetings can be provisioned. Third, the server should run PHP 7.x or 8.x, with end users accessing the interface through IE11, Firefox, Opera, or Chrome. Because conferencing media is handled by Whereby’s own service, server load on the CRM host is limited to scheduling and notification workloads, which keeps the footprint of the plugin lightweight on shared or agency-grade hosting.

Secondary development is constrained by the plugin’s scope: customization is practical at the level of meeting workflow configuration within RISE, while the conferencing behavior itself is delegated to the Whereby service and should not be modified at the codebase level. For teams running decoupled WordPress properties alongside a RISE deployment, the Zoom Meeting Manager exists as a separate standalone solution that manages and sells Zoom meetings from a WordPress site, operating independently of this CodeIgniter extension.