Skip to main content

Glide customer care

Answers without the runaround.

Search practical guidance for Ride Glide, Drive Glide, Glide Fleet, payments, GNet, onboarding, and active trips. When an article is not enough, move into one human-owned support thread.

Immediate danger?

Call 911 now. Glide support is not an emergency service. For an urgent pickup or active-trip problem without immediate danger, use urgent trip support below.

Open urgent support form

Published guidance

Find the right guide

Published revision launch-2026-08-01 · source Keystatic

Showing 12 of 38 published guides

EnglishSafety

Emergency or immediate danger

Glide support is not an emergency service. Call 911 when anyone is in immediate danger.

Read the guide
  1. Move to a safe location when you can do so without increasing risk.
  2. Call 911 for immediate danger, a serious collision, fire, violence, or a medical emergency.
  3. After emergency help is underway, report the incident to Glide so the trip can be preserved and reviewed.
When we escalate: Never auto-resolve. Create an urgent safety incident and alert both authorized operators.

Source: Glide launch safety policy · revision launch-2026-08-01 · reviewed 2026-08-01T00:00:00.000Z

EnglishActive trip

Help during an active trip

Use the trip screen for current details and contact urgent support when a live pickup or ride is at risk.

Read the guide
  1. Open the active trip and confirm the pickup, rider, vehicle, and contact options shown there.
  2. Use masked in-app contact when it is available; do not post personal numbers in chat.
  3. Choose urgent trip support for a missed pickup, lost contact, vehicle issue, or trip that cannot continue.
When we escalate: Create an urgent ticket; target a human response within five minutes during published support hours.

Source: Glide active-trip support policy · revision launch-2026-08-01 · reviewed 2026-08-01T00:00:00.000Z

EnglishAccount

Sign in and recover account access

Use the same verified email or phone you used at signup and request a fresh verification challenge when needed.

Read the guide
  1. Confirm that you selected the correct Glide app and the same sign-in method used during signup.
  2. Request one new code, use only the newest code, and check that your device date and time are automatic.
  3. If access still fails, contact support from a verified email or phone so ownership can be checked.
When we escalate: Escalate after two failed recovery attempts or any suspected account takeover.

Source: Glide identity support policy · revision launch-2026-08-01 · reviewed 2026-08-01T00:00:00.000Z

EnglishBooking

Request and review a ride

Review the pickup, destination, rider, vehicle class, estimated terms, and payment method before confirming a fleet-operated ride.

Read the guide
  1. Enter complete pickup and destination details and choose the correct rider.
  2. Review timing, service level, price disclosures, cancellation terms, and payment method.
  3. Confirm once. The trip screen will show whether the request is pending commercial fleet provider matching or accepted.
When we escalate: Escalate duplicate requests, inaccessible pickup details, or any request that remains unclear after provider reconciliation.

Source: Glide booking experience policy · revision launch-2026-08-01 · reviewed 2026-08-01T00:00:00.000Z

EnglishGNet

How on-demand provider matching works

Glide uses GNet for on-demand dispatch into fleet-operated service and displays the state confirmed by the fleet without promising a match before acceptance.

Read the guide
  1. After a request is submitted, keep the trip screen open while GNet checks eligible providers.
  2. A pending request is not yet an accepted ride; wait for the confirmed commercial fleet provider and vehicle details.
  3. If no eligible provider accepts, Glide will show an unavailable or degraded state instead of a false confirmation.
When we escalate: Escalate contradictory statuses or requests stuck beyond the published matching window.

Source: Glide GNet dispatch policy · revision launch-2026-08-01 · reviewed 2026-08-01T00:00:00.000Z

EnglishPayments

Payment authorization, charge, and receipt

A temporary authorization can differ from a completed charge; the final receipt reflects the recorded transaction.

Read the guide
  1. Open Payments or the completed booking to find the receipt and transaction state.
  2. Check whether the bank labels the amount pending or completed before reporting a duplicate.
  3. Use support for a missing receipt or mismatch and include the booking reference, not full card data.
When we escalate: Escalate completed-charge mismatches, duplicate charges, or any request for live payment status from a public session.

Source: Glide payment operations policy · revision launch-2026-08-01 · reviewed 2026-08-01T00:00:00.000Z

EnglishBooking

Cancel a booking

Use the booking's cancellation action and review the displayed terms before confirming.

Read the guide
  1. Open the booking and choose Cancel when the action is available.
  2. Review any fee and timing disclosure tied to that booking before confirming.
  3. Keep the cancellation confirmation. If the trip is already active, contact urgent support instead of assuming it ended.
When we escalate: Escalate active-trip cancellations, missing confirmations, or disputed cancellation fees.

Source: Glide cancellation support policy · revision launch-2026-08-01 · reviewed 2026-08-01T00:00:00.000Z

EnglishSupport

Report a lost item

Start from the completed trip so Glide can contact the correct fleet or driver without exposing personal contact details.

Read the guide
  1. Open the completed trip and choose Report a lost item.
  2. Describe the item and where it may have been left without including highly sensitive contents.
  3. Use masked contact or the support ticket thread for arrangements; never travel to a private address without agreement.
When we escalate: Escalate medication, identity documents, keys, or safety-sensitive property for prompt human coordination.

Source: Glide lost-item policy · revision launch-2026-08-01 · reviewed 2026-08-01T00:00:00.000Z

EnglishOnboarding

Complete driver onboarding

Driver readiness requires verified identity, fleet membership, GNet and compliance status, documents, consent, notifications, and app setup.

Read the guide
  1. Sign in with the email or phone invited by your fleet and complete identity verification.
  2. Finish profile, consent, document, fleet, GNet, and compliance steps shown in onboarding.
  3. Enable required trip notifications and active-trip location access, then confirm the readiness screen is green.
When we escalate: Escalate unclear blocked states; Glide support cannot approve compliance without authoritative evidence.

Source: Glide driver onboarding policy · revision launch-2026-08-01 · reviewed 2026-08-01T00:00:00.000Z

EnglishOnboarding

Fleet application and onboarding

Fleets may apply nationwide; activation depends on business verification, market eligibility, GNet, compliance, payment, and subscription readiness.

Read the guide
  1. Apply with your legal business and primary operator details and preserve the confirmation.
  2. Verify the invited owner account, then complete fleet profile, service markets, GNet, compliance, payment, and subscription steps.
  3. Review the readiness screen for blocked items; application does not guarantee immediate activation or ride volume.
When we escalate: Escalate ambiguous identity matches, missing application links, or blocked evidence without overriding vendor decisions.

Source: Glide fleet application policy · revision launch-2026-08-01 · reviewed 2026-08-01T00:00:00.000Z

EnglishCompliance

Vehicle and fleet compliance

Bookability is market-specific and requires green fleet, driver, vehicle, GNet, and payment decisions even though application is nationwide.

Read the guide
  1. Open Compliance and select the state or market where service is requested.
  2. Review each official-source requirement and securely supply the requested evidence.
  3. Resolve expiring or rejected fleet, vehicle, insurance, permit, or driver items before accepting work.
When we escalate: Support explains requirements and evidence status but cannot turn a non-green market combination bookable.

Source: Glide nationwide eligibility policy · revision launch-2026-08-01 · reviewed 2026-08-01T00:00:00.000Z

EnglishTechnical

App crash or technical problem

Capture the app, build, device, screen, and correlation ID without sharing secrets or unnecessary personal data.

Read the guide
  1. Update to the newest production version available to your device, then restart the app once.
  2. Note the app name, build, operating system, current screen, time, and correlation ID shown with the error.
  3. Submit a technical support request. For an active ride, use urgent trip support instead of troubleshooting alone.
When we escalate: Escalate repeated crashes, affected payments, active trips, security issues, or widespread provider failures.

Source: Glide technical support policy · revision launch-2026-08-01 · reviewed 2026-08-01T00:00:00.000Z

AI-assisted · published sources only

Ask Glide Guide

Glide Guide searches only the published articles on this page and cites what it uses. It cannot see a live account, trip, payment, GNet, compliance, or location state in this public session. It abstains and hands off when human review is safer.

AI-assisted · citations included · human handoff stays visible

One support history

Talk to a person

Submit once and keep replies in the same thread. A ticket exists only after you receive a ticket number—we never show a fake success when support delivery is offline.

Honest response targets
  • Active trip: five minutes during published operating hours
  • Account, payment, or access: four business hours
  • Onboarding, billing, and how-to: one business day

Secure support request

Delivery is confirmed with a real ticket number.

By submitting, you agree that Glide may use this information to provide support under our Privacy Policy.