Help center Core configuration Integrations & migrations Configure Zoom meetings and phone processing Updated Thursday, October 29, 2026 · Marc Staine Zoom integration can connect calendar meetings, call logging and available meeting/phone artifacts to support work. Separate controls let you choose exactly which interactions and artifacts are processed. Applies to: Supportbench Core. Location: Settings → Integrations → Zoom. Requires Administer all integrations. Before you begin You need Administer all integrations and authorization to connect the intended provider organization. Obtain credentials through your approved provider process; keep them out of screenshots and support messages.Decide separately whether your team needs scheduled meetings, phone activity, inbound Case creation and each kind of artifact. An artifact is a provider-generated item such as a transcript, recording or summary; enabling its processing does not make the provider create one.Choose approved test records and people before sending messages, creating engineering work or making calls. Record the current connection identity and enabled options so the test has a clear expected result. Configure and verify Open Settings → Integrations → Zoom and choose Authorize Zoom for the intended account/user.Choose Sync hosts and select Default host with the provider capabilities needed for supported meeting actions.Review Active, Meetings and Calendar meetings. Configure meeting summaries, transcripts and recordings separately according to available provider artifacts and storage needs.Review Zoom Phone and Call logging separately from Inbound auto-case and its Queue, Category and Priority. Inbound auto-case can create an eligible Case even when Call logging is off.Review phone summaries, transcripts and recordings independently. Choose Save Changes and reopen to verify the selected processing options.Run an approved representative meeting or phone test and inspect the expected Case/Activity and available artifacts. Check Last webhook, Pending, Failed and Unavailable artifacts.Resolve the underlying connection/provider problem before Retry eligible work. Only eligible jobs are retried. Disconnect stops new processing while retaining settings and history. Settings reference Connection and operating controlsSettingWhat it controlsHow to chooseAuthorize Zoom / DisconnectConnects Zoom; disconnect stops new processing while retaining settings and history.Verify the intended account and user.Default host / Sync hostsSelects the host for supported meeting actions and refreshes available hosts.Choose a host with the intended provider capabilities.ActiveEnables the installed integration.Review the individual processing options before activation. Meetings and Zoom PhoneSettingWhat it controlsHow to chooseMeetings / Calendar meetingsControls meeting support and creating/updating Zoom meetings from the calendar.Enable the calendar path only when your team uses it.Meeting summaries / Transcripts / RecordingsSelects the available meeting artifacts to process.Enable only useful artifacts and review provider availability.Zoom Phone / Call loggingEnables phone support and recording phone calls as support activity.Separate call activity needs from case-creation needs.Inbound auto-case / Queue / Category / PriorityCreates and routes a case for eligible inbound calls without a related case.Choose monitored routing and test it with a representative call.Phone summaries / Transcripts / RecordingsSelects phone artifacts independently.Review the desired information and storage use. ProcessingSettingWhat it controlsHow to chooseLast webhook / Pending / Failed / Unavailable artifactsShows interaction and artifact processing health.Inspect the last error and distinguish unavailable provider data from retryable failures.Retry eligible workRetries work that the processing system considers eligible.Resolve connection or provider problems first; verify the next processing result. Behavior to knowInbound auto-case can create a case without a related case even when Call logging is off. Disabling call logging does not disable auto-case or enabled artifact imports.Recordings are imported within the configured storage limit. Recommended use Enable only the meeting and phone artifacts the team can use and retain appropriately. Review provider availability and your organization’s recording/privacy process before testing.Separate Call logging from Inbound auto-case in both configuration and acceptance tests. The latter can create an eligible Case even when call logging is off.Use Last webhook, Pending, Failed and Unavailable artifacts to choose the next action. Resolve a provider or connection problem before Retry eligible work; unavailable provider data is different from a retryable processing failure. Worked example: test a customer service review and an inbound support call separately Illustrative situation: Meridian Industrial schedules monthly service reviews and also receives equipment-support calls. The team wants calendar meetings for account reviews and a monitored Case for eligible new inbound support calls. These are different outcomes and should have separate tests.For the service-review test, Authorize Zoom, Sync hosts and select an eligible Default host. Enable Meetings and Calendar meetings as intended, choose any needed meeting summaries/transcripts/recordings individually, and Save Changes. Open the approved calendar test event, select Add Zoom meeting, choose the intended Zoom host, and select Save event. Verify the resulting meeting with that host.After the meeting, inspect only the artifacts the provider actually made available and your settings allow. Check the resulting support context and processing status. A missing transcript does not mean that the meeting connection failed; the provider may not have generated an eligible transcript.For the separate phone test, review Zoom Phone and Call logging, then Inbound auto-case with a monitored Queue, Category and Priority. Use an approved eligible inbound call without a related Case. Verify the resulting Case/customer association and final routing, including any ordinary workflows that run afterward.If Call logging is enabled, inspect the expected call Activity separately. If Call logging is off but Inbound auto-case is on, Case creation can still be expected for an eligible call. Check phone summaries/transcripts/recordings independently instead of assuming meeting options control them.When work is Failed, inspect the cause, correct the prerequisite and use Retry eligible work only when appropriate. When the provider artifact is Unavailable, confirm whether it exists and is accessible before retrying; repeated retries cannot manufacture a recording that was never supplied.Record each test outcome and the team responsible for missed calls or failed artifacts. Disconnect stops new processing while retaining settings and history; it is not a way to erase prior customer interactions. Troubleshooting ProblemWhat to checkThe intended host is missingUse Sync hosts and verify the authorized provider account and the host’s capabilities.A Case was created with Call logging offInbound auto-case is separate. Review its switch and routing; disabling Call logging does not disable it.A transcript or recording is missingCheck its individual option, provider artifact availability, storage limits and processing status.Retry did not recreate every artifactRetry eligible work acts only on eligible jobs. Distinguish unavailable provider data from retryable failures.Old data remains after DisconnectDisconnect stops new processing; it preserves settings and history. Related configuration Integrations → Use the data synchronization logOrganization → Configure agent roles and division accessPlan holiday coverage and understand its effect on SLA timingWork a case from first response to resolution Was this article helpful? Yes No Thank you for your feedback.