MOQO Product Review – Q3/2026

September 10, 2026

In this article you will find all highlights, recordings, and useful links regarding the presented features, as well as answers to the most important questions raised by the community.

On September 8 and 9, 2026, the MOQO Product Review for the third quarter took place. For the first time we ran it as two separate sessions, one in German and one in English, following the feedback from the MOQO Summit. Under the motto "You decide what matters, MOQO handles the rest", we presented four developments that take manual work off your desk.

The sessions covered digital refuelling straight from the app, the expanded Customer Support Engine with self-service support instructions, the first live phase of MOQO AI, and the rebuilt developer documentation.

In the fourth quarter of 2026, the product team is focusing on the following:

Drive, refuel, drive on. No fuel card, no PIN, no trip to the counter.

Drivers find a station in the app, pick the pump, and drive on without a fuel card in the vehicle. You activate the feature per vehicle in the portal, and every transaction comes back with station, licence plate, mileage, and booking ID, so it maps cleanly against the ryd portal. Setup runs in three steps: a form in the portal triggers the framework contract with ryd, which needs an operational contact and an authorised signatory. Once ryd confirms, the feature is switchable per vehicle on a monthly basis.

The fee is 3 € per vehicle per month and runs through your regular MOQO invoice. Fuel costs are billed by ryd directly, with an agreed spending limit. For September, the fee is waived for your first ten vehicles. During the hypercare phase, please route all support requests through MOQO first, including anything that looks wrong in the ryd portal.

One condition from the field: the vehicle must report its fuel level to the platform. And the rollout works best car by car, station by station, not as a big bang.

–

Q: When will a digital charging card be available?

A: There is no timeline yet. Many providers, particularly municipal utilities, operate their own charging infrastructure and want to keep using their own cards. The driver journey for charging is also more complex. MOQO and ryd are in discovery on this, with no roadmap commitment.

Q: Is digital refuelling available outside Europe, for example in the US?

A: No. ryd is focused on Europe and has no charge point operators or US expansion planned.

Q: How does the 12-month ryd contract relate to my vehicles in MOQO?

A: The ryd contract is a framework agreement. The MOQO feature is switchable per vehicle per month. If it was active in a month, it is billed for that month, with no pro-rating by day.

Q: Is it checked whether the sharing vehicle is actually the one being refuelled?

A: Not automatically. It becomes visible through the fuel-level delta, for example when 50 litres are paid for but the vehicle's tank shows less. Anti-fraud rules and spending limits apply. No such case has occurred to date.

Q: Can fuel and charging costs be passed on directly within a booking?

A: Not yet, and it is a sensible request, especially for van rental. The concept has to be designed before it can be built.

Your own answers, maintained by you, with no ticket and no waiting.

Provider-specific instructions replace the previous form-based process. You create and edit them yourself under Settings, in any number, and Fin reads them directly to answer driver questions with your own information. In the demo, the question "where is the key?" first returned a generic answer. After one support instruction was created, the same question returned the location per licence plate, and Fin added the reminder to put the key back after the trip on its own.

Support instructions do not override platform settings, and the general driver Academy remains the basis for generic topics. If you would like help setting yours up, Luisa offers 1:1 calls.

–

Q: Does the MOQO hotline have access to support instructions?

A: Not currently, and neither does Fin Voice on the phone. Both are planned.

Q: Is there a specific format for writing support instructions?

A: The Academy article explains the approach. Beyond that, Luisa is happy to go through your instructions with you in a call.

Support where the question comes up, on every channel.

Support entry points now sit natively in the app on every relevant screen, from booking creation through cancellation to driver licence verification, with the booking context passed along. The previous web embed is gone, and with it the friction it caused. Incoming chat requests have more than doubled since the change, three quarters of them arrive from iOS and Android, and customer satisfaction moved from 30 to 50 percent.

On the phone, Fin Voice answers first. It picks up every call immediately, handles several calls in parallel, and has taken around 16,000 calls since mid-June, resolving roughly 30 percent of them end to end. Everything else goes to the human call centre with a structured handover rather than a queue. If you already use MOQO Customer Service in the Call Center Upgrade, Fin Voice is live for your drivers at no extra cost.

You can try it yourself: +49 241 94223094 (English) and +49 241 94223091 (German).

–

Q: Can I see which chats Fin held on my behalf?

A: Not yet. It is frequently requested feedback and we are working out the best way to give you that view.

Q: How far is my data used by Fin?

A: Fin accesses customer bookings through authenticated data connectors and answers specific questions live. Wider access to platform data is planned.

Q: Does the Support Engine cost extra?

A: Yes. Fin in chat starts in the Essential package, and the phone channel including the human call centre sits in the full Customer Service package. Please contact us for current pricing.

Talk to the platform in your own words.

An "Ask AI" interface is now live inside the MOQO platform. Ask which vehicles are out of service, why one is in maintenance, or how many open damages a vehicle has, and you get an answer with links back into the portal. It runs in your production environment, it is secure, and it is free to use during the beta.

Phase one covers fleet and booking data. Phase two brings predefined tasks that MOQO defines globally and you switch on and off. Phase three lets you work with the AI in projects and set your own rules. The first working agents are planned to go live within this year.

Two honest limits: larger statistics and analyses over longer periods do not work reliably yet, and the AI cannot yet carry out tasks. Please ask for both anyway. There is deliberately no Academy documentation during the beta, because we want to find out from your questions what this should become. If you spot an error in the data, tell the AI directly in the chat.

All attendees were given beta access. If you would like access and were not at the session, get in touch.

Rebuilt documentation with a request builder.

The API documentation has been rebuilt and is generated directly from the platform's own API specifications, covering the Graphiti read API, the Driver API, and the Aggregator API. It includes a request builder that lets you test queries straight from your browser, and an AI reference file per API for use with your own tooling.

This is most relevant if you build your own tools or process data in bulk: exporting invoice documents with download URLs, archiving, collections handling. Partners such as Lanterne and Bilkollektivet already build on it.

This was our fourth Product Review and the first split into two sessions by language. There were no parallel workshops this time. Instead, each feature block closed with an open Q&A, and the questions from both sessions are collected above.

The German session ran twenty minutes over. We are shortening the introduction and the quarterly recap for the December edition so that more of the time goes into the features themselves.