Agency relationship
Drivers use Lgrima through a transport agency rather than registering independently.
Safety and trust
Private transportation with clearer accountability.
Lgrima connects transportation requests with agency-managed drivers and keeps the selected offer, driver, vehicle, route, and trip communication together.
Agency-managed drivers
Confirmed driver and vehicle details
Support and reporting records
Safety depends on accurate information, responsible partners, and clear reporting.
How Lgrima approaches trust
Accountability at each stage of the journey.
Lgrima combines agency relationships, trip records, controlled communication, and operational support tools instead of relying on anonymous driver access.
Trip transparency
The selected offer keeps the agreed driver, vehicle, route, time, and cash price together.
Controlled communication
Trip messaging becomes available only after confirmation and during supported trip stages.
Reportable activity
Support records and operational issue categories help the Lgrima team review relevant concerns.
Agency-based transportation
Every operational driver is connected to a transport agency.
The agency manages driver access, assigned vehicles, and operational account activity.
Agency
- Creates driver records and sends invitations.
- Adds vehicles and assigns an approved vehicle.
- Can suspend or reactivate driver access.
Invited driver
- Accepts an invitation connected to the agency.
- Uses the vehicle assigned by the agency.
- Reviews compatible requests and sends one offer.
Traveler or Business user
- Creates the transportation request.
- Compares available driver offers.
- Selects the preferred driver and vehicle.
Drivers cannot register independently or add their own vehicles.
Transportation model
Built for organized tourism transportation in Morocco.
Lgrima is designed for transportation activity managed through tourism transport agencies, with drivers and vehicles connected to those agency accounts.
Lgrima is a tourism transportation marketplace, not a public taxi or instant ride-hailing service.
- Travelers submit the route, schedule, passenger, luggage, and service information.
- Compatible agency drivers may send offers; an offer is not guaranteed.
- The traveler or Business user chooses the preferred offer. Drivers are not assigned automatically.
- A specific vehicle or driver cannot be guaranteed before an offer is selected.
- The traveler pays the selected driver the agreed amount in cash.
Agency information
Agency identity, contact, city, address, authorization file, expiry, and account status can support review.
Driver information
Driver identity, agency relationship, spoken languages, license information, assignment, and account status may be recorded.
Vehicle information
Brand, model, year, plate, category, seats, images, registration record, and assignment are stored for fleet operations.
Operational status
Agency, driver, vehicle, and document status can affect onboarding, assignment, offer acceptance, or access.
Review and account status
Information and review states support operational decisions.
Lgrima uses account statuses and document records to manage incomplete, approved, rejected, expired, or suspended information.
- 01
Information submitted
- 02
Review pending
- 03
Approved or verified
- 04
Rejected with a reason
- 05
Expiry or renewal needed
- 06
Access suspended when necessary
Agency review
- An agency application enters a pending state.
- An administrator can approve, reject, suspend, or reactivate the agency.
- The transport authorization has its own review and expiry state.
Driver records
- Driver identity and license information can be held in the agency record.
- Driver account approval and suspension status are available to operations.
- This does not mean every license is independently checked against a government database.
Vehicle review
- New agency vehicles enter pending verification.
- An admin can approve or reject the vehicle record.
- Assignment paths block a new vehicle until approval.
Sensitive document images, CIN numbers, and license numbers are never shown on this public page. Lgrima does not claim criminal-background screening or government-database verification.
Confirmed trip
Airport transfer
Youssef A.
Atlas Transport · Marrakech
4.9
Dark gray minivan · 7 seats
Demonstration vehicle
- Service
- Airport transfer
- Pickup
- Marrakech Airport
- Destination
- Medina riad
- Schedule
- 18:30
- Party
- 3 travelers · 4 bags
Before the journey
See the driver and vehicle connected to the offer.
Offer details can show the agency, privacy-safe driver name, rating when available, spoken languages, vehicle characteristics, and the proposed cash price. After selection, the confirmed trip keeps the route, schedule, driver, vehicle, and price together.
Driver
First name with surname initial, profile image when enabled, rating, trip count, and spoken languages where available.
Vehicle
Photo when available, brand, model, year, color, category, seats, plate, and supported features.
Trip
Service, pickup, destination, schedule, party information, confirmed price, and current status.
Not public
CIN, driver-license number, home address, full surname, and personal profile phone number are not public offer fields.
Trip communication
Communication opens after the booking is confirmed.
Lgrima enforces trip messaging on the server for confirmed, arrived-at-pickup, and in-progress trip states.
Before selection
The traveler reviews offers. Direct trip chat is unavailable and personal profile phone numbers are not offer fields.
After confirmation
The selected driver and vehicle are linked to the trip, and in-app messaging can be created for supported status rules.
During the trip
Messages remain associated with the trip so pickup coordination and relevant details stay in context.
Drivers should use messaging and support controls only before driving or after stopping safely.
Contact privacy
Personal contact details are not public profile information.
Lgrima separates public driver presentation from trip and support information. Access depends on the user role and booking flow.
- Public driver displays use first name and surname initial.
- Trip messaging is connected to confirmed and active trip states.
- Client-facing offer and trip queries do not return unused driver profile phone numbers.
- Business users should share only the guest information needed for transportation.
- Support staff may access account context required to handle a conversation.
- All public examples on this page use fictional demonstration data.
Private profile
A personal profile phone number is not a public driver-offer field.
Trip-linked communication
Messages are authorized against the trip participant and status.
Role-based context
Travelers, drivers, agencies, and support roles receive different operational information.
Use the minimum needed
Avoid placing unrelated personal or financial information in notes or messages.
Report a problem
Support conversations are available; trip issue records are defined.
Client and Partner users can open support conversations. The backend also defines trip-related behavior, vehicle, safety, app, and other issue categories for operational review.
Behavior
Conduct, communication, or professionalism concerns.
Vehicle
A mismatch, condition, or capacity concern.
Safety
Unsafe conduct or a serious trip concern.
App
Trip status, chat, location, or notification problems.
Other
A concern that does not fit another category.
Current support path
Use the support area connected to your Client or Partner account, or use the public Help Center and contact page when app access is unavailable.
- Keep the relevant trip and time available.
- Describe what happened clearly and concisely.
- Include only the context needed to understand the concern.
- Do not publish sensitive information or report details publicly.
Trip report entry-point status
The issue-ticket categories and statuses exist in the backend, but the dedicated report sheet is not currently connected to the Client or Partner trip screens. This page therefore does not promise that every user can submit these categories from every trip.
Urgent safety concerns
Emergency records support the Lgrima operations workflow.
When a supported authenticated flow creates an emergency event, Lgrima records the trip, reporter, event type, optional location and message, and makes the event available to the administrative emergency workflow.
Panic
Accident
Breakdown
Safety concern
- The reporter must be an authenticated participant in the trip.
- An event is created with active status.
- Available trip and optional location context can be attached.
- The other trip participant may receive an emergency notification.
- A configured internal email is queued for the Lgrima team, and an admin can mark the event resolved.
The in-app record is not a replacement for local emergency services.
Lgrima does not automatically contact police, ambulance, fire, gendarmerie, or local responders. When immediate physical assistance is required, contact the appropriate local emergency service directly when it is safe to do so.
Before and during your trip
Simple steps for a more confident journey.
Use the confirmed trip information and your own judgment throughout the transportation experience.
Before selecting
- Review driver, vehicle, capacity, timing, and price.
- Compare the complete offer, not only the price.
- Choose the service type that matches the journey.
Before entering
- Compare the arriving vehicle with the confirmed details.
- Check the driver information shown in the app.
- Confirm the destination and practical pickup point.
During the journey
- Avoid distracting the driver and use a seat belt where available.
- Do not share unnecessary personal or financial information.
- Report serious concerns only when it is safe to use the app.
Cash payment
- Use the confirmed offer as the reference amount.
- Keep enough cash available; change is not guaranteed.
- Use support if a disagreement cannot be resolved safely.
Airports and riads
- Provide accurate flight, hotel, or riad information.
- Some Medina streets may not be accessible by vehicle.
- Confirm the practical meeting point through supported trip chat.
For hotels and businesses
Keep guest transportation connected to the Business account.
Business accounts help organizations create, select, and follow guest transportation requests through one managed experience.
- Use the correct guest pickup, destination, and schedule.
- Add accurate passenger, luggage, language, and reference information.
- Review the driver and vehicle before selecting an offer.
- Give the guest the confirmed driver, vehicle, and pickup details.
- Coordinate cash payment according to the organization’s process.
- Keep booking management and support connected to the Business account.
- Do not place unnecessary sensitive guest information in open notes.
For transport agencies
Agencies remain responsible for the drivers and vehicles they manage.
The Agency Portal connects operational access, fleet information, driver invitations, documents, and agency account activity. Lgrima does not replace the agency’s legal responsibilities.
Keep agency information current
- Provide accurate identity and contact information.
- Submit and renew transport authorization information.
- Correct incomplete or rejected information.
Manage driver access
- Invite only legitimate agency drivers.
- Keep driver identity and license information current.
- Suspend access when a driver should not operate.
Manage the fleet
- Keep vehicle and registration information current.
- Assign the correct approved vehicle.
- Update or renew vehicle documents where supported.
Respond responsibly
- Review account activity and operational status.
- Respond to support and safety concerns.
- Follow applicable laws and transportation requirements.
Transparent expectations
Technology supports safer decisions, but it cannot remove every risk.
Lgrima provides information, account relationships, trip records, communication controls, and operational tools. Travelers, drivers, agencies, and businesses still have responsibilities.
What Lgrima can provide
- Agency-linked driver accounts and assigned vehicles.
- Driver, agency, vehicle, route, schedule, and price information.
- Offer selection and confirmed trip records.
- Server-controlled trip messaging for supported statuses.
- Support conversations and administrative emergency records.
- Account, document, vehicle, and suspension status controls.
What Lgrima cannot promise
- Guaranteed availability of an offer, driver, or vehicle.
- A risk-free journey or perfect identity verification.
- Automatic emergency-service dispatch.
- Real-time human monitoring of every trip.
- A guaranteed support response time.
- Guaranteed road conditions, driver conduct, or dispute resolution.
- Automatic insurance or roadside-assistance coverage.
Frequently asked questions
Questions about safety and trust on Lgrima.
Straight answers based on the current product and operational workflows.
Choose the right support path
Need to report a concern?
Use the support path connected to your account, trip, or role. Do not publish report details or personal information publicly.
Traveler or Business user
Open Client support and keep the relevant trip available. If app access is unavailable, use the Help Center or contact page.
Find Client supportInvited driver
Open Partner support, keep the active trip available, and contact the agency manager when the issue concerns agency operations.
Find Partner supportAgency manager
Use the Agency Portal to review the driver, vehicle, document, or account context and the agency support channel.
Open Agency PortalAffiliate
Use the Affiliate Portal or the public contact route for referral-program support.
Open Affiliate PortalImmediate physical danger
Contact the appropriate local emergency service directly when immediate physical assistance is required. Lgrima’s in-app records do not automatically dispatch responders.