Use cases

Drivers scan various documents: CMRs, delivery notes, pallet receipts, photos of accidents or damages. These documents are automatically synchronized with the instantCMR backend. Users with access to the instantCMR Hub can review and manually download these.

As your company grows, manual processes can become cumbersome, creating a need for automation. With minimal effort, you can automate the export of these submissions using the instantCMR API.

Here’s how the process works:

1. Document Submission: when a new document is submitted, the instantCMR backend creates a Dubdosu entity. This entity contains metadata about the driver, notes and links to attached images. Dubdosu is then added to a message queue, which has been set up by our backend team for you.

2. Queue Management: the entity remains in the queue until your backend makes a poll request to the provided endpoint. The instantCMR backend then retrieves the first few items from the message queue and returns them in the response.

3. Processing Entries: your backend should process the entities, download the images, and register them in your system.

4. Acknowledgment: after processing, your backend needs to acknowledge the transmission by sending another request to the instantCMR backend. The instantCMR system will then mark the entities as processed and remove them from the message queue.

By following this process, you can efficiently manage document submissions, ensuring that they are seamlessly integrated into your transport management system.

Dealing with many tours and optimizing vehicle usage, processing the flow of incoming documents becomes increasingly challenging. This necessitates a higher level of organization. In instantCMR terminology, trips consist of a list of stations that need to be visited by the driver and document requests to be fulfilled. While our hub provides many features to work with data arriving from trips, you cannot currently create them within the UI itself; this functionality is unlocked by implementing deeper integration with our system.

Here’s how you can manage trips through integration:

1. Define a Trip: specify the stations to be visited and document requests that need to be submitted by the driver. Attach additional guides, documents, or route plans to the trip.

2. Create the Trip: your system sends a PUT request to the instantCMR backend to create the trip in our system. instantCMR will synchronize the trip information with the corresponding driver's mobile phone, and the driver will be immediately notified about the tasks to be completed.

3. Trip Execution: as the driver follows the steps within the trip, documents continuously flow into the instantCMR backend.

Getting notified about trip updates is similar to the case of handling arbitrary document submissions.

1. Document Submitted: when the submission arrives, the instantCMR backend creates a Dubtrip entity. This entity corresponds to the trip you created and contains the current status of the trip with all the submitted items and metadata. The Dubtrip entity is added to your message queue, the same way as we discussed at arbitrary document submissions above.

   The process is exactly the same when the trip is modified by a hub operator. For example, when he or she fixes a mislabeled submission and associates it with the document request it really belongs to, the trip entity gets updated and a corresponding Dubtrip message is dispatched.

2. Queue Management: the entity remains in the queue until your backend makes a poll request to the provided endpoint. The instantCMR backend then retrieves the first few items from the message queue and returns them in the response.

3. Processing Entries: your backend should process these entities, making updates to the trip in your system, download the images, and register them on your side.

4. Acknowledgment: after processing, your backend needs to acknowledge the transmission by sending another request to the instantCMR backend. The instantCMR system will then mark the entities processed and remove them from the message queue.

Absolutely — here’s a use case written in the same natural, explanatory tone and structure as your “Receiving document submissions” example:

In a busy transport operation, clear and timely communication between drivers, dispatchers, and support staff is essential. With the instantCMR Chat API, you can integrate real-time messaging directly into your applications, ensuring that everyone stays connected while maintaining full control over message delivery and synchronization.

Here’s how the process works:

Chat Room Creation: When a new communication channel is needed — for example, between a dispatcher and a driver assigned to a specific delivery — your backend creates a chat room using a unique roomxtid. This identifier ensures that each conversation remains distinct, even when multiple deliveries are in progress simultaneously.

Member Management: Each chat room can have up to 100 participants, identified by their userxtid. Members can be added or removed as needed. For instance, if a mechanic needs to join the conversation to assist with a vehicle issue, they can be temporarily added. Once removed, they will no longer see the chat or its messages.

Message Exchange: Participants can send messages to the chat room in real time. Each message includes the author’s userxtid, message content, and an automatically assigned sequence number (etagpost). This sequence ensures that messages are delivered in the correct order, even if multiple users post simultaneously.

Synchronization and Delivery Tracking: The Chat API tracks which messages have been successfully delivered and which have been read by each participant. Your backend can update these states using the owetagdtuSync and owetagdtuRead fields. This allows your system to display delivery and read receipts — for example, showing that a driver has read the dispatcher’s latest instruction.

Conversation Titles and Versioning: Chat rooms can have titles (e.g., “Delivery #492 – Berlin Depot”) or dynamically list members when no title is provided. Each update to the chat room — such as a new message or a change in membership — increments its etagroom, ensuring that clients can synchronize safely without overwriting newer data.

By integrating the instantCMR Chat API, you can provide your users with a reliable and auditable communication channel — one that’s fully synchronized, secure, and built for the realities of modern logistics operations.