Heylog connector

Use your Heylog data for reporting, automation and AI.

Data Panda pulls your Heylog orders and driver events and lines them up with the rest of your transport stack. From one place, we turn them into dashboards, automations, AI workflows and custom apps your dispatchers, planners and customer service use every day.

About Heylog

The Vienna platform that brings the WhatsApp chaos with drivers and yards back under one roof.

Heylog is a Vienna company, founded in 2022 by Johannes Leitner, Stefan Muntean, Umut Kivrak and Bernhard Hauser, with a 3 million euro round from KUBIKx and Ninepointfive that same year. The team came at it from the dispatcher, driver and loader side, and the product reflects that. Drivers do not install an app. They keep using WhatsApp, SMS, Viber, web chat or a QR code at the gate, and the dispatcher gets one structured inbox in a browser instead of forty private threads on a personal phone, with automatic translation across 24-plus languages.

Heylog runs on two sides. On the transport side, dispatchers route every driver conversation through one platform with the order attached, so ETA updates, document hand-overs and proof-of-delivery photos sit on the shipment record instead of in someone's chat history. On the shipper side, loading docks use the same channel for digital driver check-in, ramp assignment, safety briefings and time-slot management, with customers like LKW Walter, Schmitz Cargobull, Nobilia, Semperit and ALKO already in production. The reason to pull Heylog into a warehouse is that the orders and the driver event log together describe how the work really moved, and that picture rarely makes it back into the TMS or the ERP on its own.

What your Heylog data is for

What you get once Heylog is connected.

Driver-comms reporting

Orders and driver events joined to the TMS, ERP and customer-service data the rest of the business already trusts.

Dispatcher response time per driver thread, per shift
Orders with a clean ETA update against orders that went silent
Digital proof-of-delivery completion rate per route and customer

Process automation

Turn driver events into the nudges customer service, planning and finance would otherwise chase by phone.

Forward an ETA update from the driver to the customer record in CRM
Open a service ticket when a shipment goes silent past its planned arrival
Attach the driver-uploaded POD to the order in the TMS or ERP

AI workflows

Use the order and event history to predict where today's plan will slip and which conversations need a dispatcher.

Score routes on the gap between Heylog ETA updates and planned arrival
Cluster driver-thread topics to find which messages a template could handle
Flag dispatchers whose response time is drifting against their shift target

Custom apps on your data

Small dispatch, customer-service and yard tools that sit on Heylog data instead of another inbox export.

Dispatcher cockpit with open driver threads, response clock and order status
Customer-service view with the live ETA and POD per shipment
Yard board with check-in time, ramp assignment and dwell per truck

Use cases

Use cases we deliver with Heylog data.

A list of concrete reports, automations and AI features we have built on Heylog data. Pick the one that matches your situation.

Dispatcher response timeMinutes between driver message and dispatcher reply, per shift and per dispatcher.

Orders with ETA updateShare of orders that received a Heylog ETA update before planned arrival.

POD completion rateOrders with a digital proof-of-delivery uploaded, per route and per customer.

Silent shipmentsActive orders without a driver event in the last X hours.

Channel mix per driverShare of WhatsApp, SMS, Viber and web messages per driver and per route.

Translation useThreads where automatic translation was triggered, by source language.

Dispatcher loadOpen driver threads per dispatcher across the day.

Yard check-in timeMinutes from QR scan to ramp assignment per facility and shift.

Dwell at the gateTime between driver registration and load start, per dock.

Document hand-oversFreight papers and safety briefings exchanged digitally per shipment.

Real business questions

Answers you will finally get.

Where in the day are dispatchers leaving drivers waiting?

Minutes between an inbound driver message in Heylog and the dispatcher reply, per dispatcher and per hour of the day. Operations sees which shifts have a real backlog and which dispatchers carry the long-tail threads, instead of guessing from the chat history that the morning is slow.

Which customers and routes do not get a clean ETA before arrival?

Heylog ETA updates per order joined to the planned arrival in the TMS, broken out per route and per customer. Customer service sees the orders that arrived without prior notice and the routes that systematically silence up two hours before delivery, so the next conversation with that key account starts with names, not with a feeling.

Are drivers really uploading proof of delivery, or are we still chasing paper?

POD-completion rate per order, per route and per customer over rolling weeks, against the share of orders billed without a digital POD on file. Finance sees the deliveries where the cash-collection clock is starting late because the paperwork is still in a glove compartment, instead of finding out at month-end.

Value for everyone in the organisation

Where each function gets value.

For finance leaders

Digital POD completion rate per customer next to the days-sales-outstanding on those same accounts. Cash collection stops being a separate complaint and becomes a number with the proof, the route and the dispatcher behind it.

For sales leaders

ETA-update rate per customer surfaced on the account record, so the account manager walking into a quarterly review knows where service held up and where it slipped, rather than getting it from a customer email on the morning of.

For operations

Dispatcher response time, silent shipments and POD completion on one dashboard per planning team. Dispatch and customer service read the same picture, so the morning huddle is about which routes need attention today, not about whose chat screenshot is right.

Ideas

What you can automate with Heylog.

Pair with TraxGo

Pair TraxGo positions with Heylog driver updates per shipment

TraxGo positions per vehicle and Heylog driver events on the same shipment land together in the warehouse, joined on plate and on order. Dispatch sees per route where the GPS shows the truck is parked and what the driver said in the chat at the same minute, so the conversation with the customer about a delay runs on a single picture, not on two portals open in different tabs.

Pair with Solvice

Compare Solvice planned ETAs against Heylog driver updates

The arrival window Solvice planned per stop joins the ETA updates the driver really sent through Heylog on that shipment. Planning sees per route where the driver flagged a delay before the slot was missed, where the slot was missed without a heads-up and where the original plan was simply too tight, instead of post-mortem analysis from a tracker export. Optimisation gets a feedback loop the planner can act on next round.

Pair with MS Dynamics 365 Business Central

Land Heylog shipment events on Business Central sales orders

Heylog driver events (en route, arrived, unloaded, POD uploaded) flow onto the matching sales order in Business Central, with the timestamp and the channel that produced them. Customer service answers a status question from the Business Central order record itself, and finance sees the POD-on-file flag before the invoice goes out, instead of chasing a screenshot from dispatch.

Pair with HubSpot

Push Heylog ETA updates onto the HubSpot customer record

When a driver sends an ETA update through Heylog on a shipment for a HubSpot customer, the update lands as a logged activity on the matching company record with the new arrival time and the route. The account manager opens the HubSpot account before a status call and reads the live picture from the truck, instead of routing the same question through dispatch every time.

Data model

Tables we make available.

These are the 2 tables we currently pull from Heylog into your warehouse. Query them directly in SQL, join them to the rest of your stack, or build reports on top.

Events List
Orders

Missing a table you need? We can extend the sync. Tell us what is missing and we will build it for you.

Your existing tools

Your data lands in a warehouse. Your BI tools read from it.

You keep the reporting tool you already have. We connect it to the warehouse where your Heylog data lives.

Power BI Microsoft

Fabric Microsoft

Snowflake Data warehouse

BigQuery Google

Tableau Visualisation

Excel Sheets & pivots

Three steps

From Heylog to answers in three steps.

Connect securely

OAuth authentication. Read-only by default. We sign a DPA and your admin keeps the keys.

Land in your warehouse

Data flows into your warehouse on your schedule. Near real time or nightly, your call. You own the data.

Reporting, automation, AI

We build the first dashboard, workflow or AI feature with you, then hand over the keys. Or we stay on for ongoing delivery.

Two ways to work with us

Pick the track that fits how you work.

Track 01

Self-serve

We set up the foundation. Your team builds on top.

Heylog connector configured and running
Warehouse set up in your cloud account
Clean access for your Power BI, Fabric or Tableau team
Documentation on what's in the data model
Sync monitoring so you're warned before reports break

Best fit Teams that already have a BI analyst or data engineer and want to own the build.

Track 02

Done for you

We build the whole thing, end to end.

Everything in Self-serve
Dashboards built to the questions your team actually asks
Automations between your systems
AI workflows scoped to real tasks your team runs
Custom apps where a dashboard does not cut it
Ongoing delivery at a pace that fits your team

Best fit Teams without in-house BI or dev capacity. You tell us what you need and we deliver it.

Before you book

Frequently asked questions.

Who owns the data?

You do. It lands in your warehouse, on your cloud account. We don't resell or aggregate it. If you stop working with us, the warehouse stays yours and keeps running.

How fresh is the data?

Near real time for most operational systems. For heavier sources we schedule hourly or nightly. You pick based on what the reports need.

Do I need a warehouse already?

No. If you don't have one, we help you pick one and set it up as part of the first delivery. Common starting points are Snowflake, Microsoft Fabric, or a small Postgres start.

Which Heylog data does the connector pull today?

The connector brings two tables into the warehouse: orders (every shipment Heylog tracks, with the customer, the assigned driver, status and the planned arrival) and the events list (every driver event recorded against an order, including check-in, ETA updates, document uploads and POD events). That is the slice that lets you join Heylog to the order in your TMS or ERP and to the customer in your CRM. The raw chat-message bodies are not part of this pull.

Drivers reach us across WhatsApp, SMS, Viber and the web. Does the connector keep the channel?

Yes. Heylog records the source channel on each event so the warehouse keeps it too. Reporting on dispatcher response time, ETA-update share and POD completion can break out per channel, which is how you find out whether the SMS-only drivers in a particular country are systematically slower to answer than the WhatsApp drivers on the next route.

We use Heylog for yard check-in at our distribution centre, not for transport dispatch. Does this connector still apply?

Yes. Heylog runs the same orders-and-events backbone for the yard side, so the connector pulls truck registrations, ramp assignments, time-slot bookings and dwell events the same way it pulls dispatcher-driver shipment updates. The reporting frame shifts from dispatcher-response and POD to check-in time, dwell at the gate and per-ramp throughput, but the data plumbing is the same.

GDPR-compliant

Data stays in the EU

You own the warehouse

A first deliverable live in four to six weeks.

We review your Heylog setup and the systems around it. Together we pick the first thing worth building.

Book a call See our other connectors