Baldev — WebXpress’s AI Voice Agent
Not a person, and not two different agents — one named, configurable calling platform for driver safety calls and internal ops escalations. We are the only logistics SaaS shipping this in production, built with our partner Vysedeck on twenty years of platform context.
Demand-generation and rate-seeking calls are not Baldev’s job — that capability is being built into Priya’s freight-intelligence voice work, once she has voice.
A real call, made by Baldev
Recorded in production. The Control Tower triggered this call to verify a driver’s status after an extended stoppage. Hindi audio.
In this recording, Baldev still introduces himself as “the WebXpress Control Tower” — the self-introduction script is being updated to name him directly. Everything after that opening line is how the call actually runs: he asks the driver about their location and the status of the consignment, confirms the next leg of the journey, and closes the call. The full conversation is captured in the WebXpress record. A polished bilingual transcript is on the way.
One agent, two applications
Baldev is configurable. Each application below is a distinct workflow built on the same configurator, not a separate agent.
Driver Caller
Triggered by
- •Excess stoppage
- •Stop in a risky geo-fence
- •No POD after delivery
- •Seatbelt off above 20 km/h
- •Repeated harsh braking
Baldev places the call, asks the right question for the shipment stage, records the driver’s response, and writes back to WebXpress. If the response is doubtful or ambiguous, it flags for human review with the full transcript.
Why it mattersA single dispatch desk runs 50 to 200 trips a day. Routine check-ins eat a dispatcher’s morning. Baldev handles those at scale so the team focuses on genuine distress.
Ops Caller
Calls people inside
- •Hub manager about a delayed vehicle
- •Branch ops lead about a stuck loading bay
- •Team leader about an SLA-at-risk consignment
Calls people inside the logistics organisation. Internal messages often get ignored; phone calls get answered. Baldev makes sure the right person knows in time.
Why it mattersMost delays inside logistics organisations are escalation failures, not visibility failures. Someone knew. Nobody acted. Baldev closes that gap.
Baldev’s Configurator
Both applications share one configuration layer. Operations teams can tune triggers, scripts, and downstream actions without engineering.
Application
Pick from Driver Caller, Ops Caller
Triggering event
GPS event, geo-fence, SLA risk, manual queue, scheduled batch
Tolerance thresholds
Do not call below an X-minute stoppage; ignore daytime fuel-station idles, etc.
Script + response list
Define what the agent asks and the structured response options
Action per response
If driver says “traffic” do A; if “breakdown” do B
Call-window restrictions
No calls after 9 PM, no calls on declared holidays
API + JSON payloads
Push outcomes to WebXpress, ERP, CRM, or any downstream system
AI in logistics is hard work
The hard parts are the same as logistics itself — Indian compliance, multi-language coverage, voice quality on rural mobile networks, knowing when to escalate to a human, capturing the outcome cleanly back into the system of record. WebXpress is taking these on because the platform underneath already understands logistics.
Baldev is in active deployment with select customers today. We will publish measured outcomes as pilot data is validated.
See Baldev in your operation
A working session over your real shipment data. We will show how Driver Caller or Ops Caller maps to the friction in your dispatch desk today.