Micromobility
Fleet AI Deck
Synkora
A day in the life of a fleet business
The fleet already moved before your team opened the dashboard

Synkora gives the operator a command layer, the rider a more reliable trip, and the owner a clearer path to margin.

6:12 AM brief 11:30 event spike 2:00 compliance risk 5:30 margin review Rider availability Owner margin
click to advance
The Fleet Business Problem
The day starts before the standup
Synkora
Picture Monday, 6:12 AM

# What will hurt us today?

The answer is scattered across vehicles, batteries, trips, weather, city permits, ranger queues, support tickets, and event calendars. The bottleneck is not data. It is turning the day into decisions.

06:12

37 low-battery vehicles, 64 idle scooters, and 12 geofence alerts need triage before commute demand starts.

11:30

A stadium event and rain forecast change the rebalancing plan before the city feels undersupplied.

17:30

The GM asks which zones made money, which vehicles drained margin, and what to change tomorrow.

Fleet health
Morning triage is manual.

The team needs a ranked dispatch plan, not four dashboards and a CSV.

Rebalancing
Demand changes by the hour.

Events, rain, commute patterns, and idle zones should update the plan automatically.

Compliance
City risk is always local.

Fleet caps, parking rules, geofences, and reporting dates vary by permit.

Economics
Margin is hidden until month end.

Revenue, charging, maintenance, redeploy labor, and depreciation live apart.

The hook: operators move faster, riders find vehicles, owners see the economics.
click to advance
Who Benefits
One loop, three wins
Synkora
Do not pitch only operations

## Every AI decision loop should improve the rider experience and the owner economics.

Operator
Less manual firefighting.

The ops team gets the next best action: charge these units, move this cluster, recover these exceptions, draft this report.

Benefit: faster decisions, fewer missed tasks
Rider
More reliable vehicles nearby.

Better charging, rebalancing, and maintenance means riders see available vehicles where demand actually appears.

Benefit: availability, trust, fewer bad trips
Owner
Cleaner margin visibility.

The owner sees which vehicles, zones, tasks, and city rules create profit or destroy it before month-end review.

Benefit: utilization, margin, risk control
The sales story: better operations creates better rider experience, which creates better unit economics.
click to advance
Synkora Positioning
The fleet business command layer
Synkora
The promise

# Recurring decisions become AI loops

Synkora is not another fleet dashboard. It is the layer that reads your systems, reasons with your rules, explains the recommendation, and asks before acting.

For the operator, it is a command center. For the rider, it is availability. For the owner, it is margin, utilization, and risk control.

Morning brief Scheduled

Agents run before standup and send the operator a prioritized day plan in the dashboard or Slack.

Live action room Tools

The same agent can inspect vehicles, trips, maps, tasks, riders, areas, reports, events, and weather.

Approval and audit Governed

High-impact moves become human-approved work orders with traceable reasoning and usage history.

The business experience: brief operations, protect riders, show owners the financial impact.
click to advance
Synkora Platform Strength
Why this needs more than a chatbot
Synkora
The operating layer around AI agents

## One platform connects fleet ops, rider support, city compliance, and owner economics.

Fleet connectors
Vehicles, trips, riders, tasks

Micromobility tools inspect fleet state and create operational work.

Rider support
Refunds, fees, failed rides

Agents triage rider issues, explain charges, and escalate exceptions.

Knowledge base
Permits, policies, SOPs

RAG keeps answers grounded in city rules and company policy.

Channels
Slack, WhatsApp, Teams, widget, API

Ops teams and support teams work where they already live.

Governance
Approvals, audit, observability

High-impact actions are reviewed, logged, measured, and traceable.

Ownership
Self-host, BYO LLM, multi-tenant

Owners control data, model keys, quotas, billing, and tenant boundaries.

External context
Weather, events, maps, tickets

Agents combine live demand signals with local context and routes.

MDS / data health
Feeds, anomalies, compliance exports

Monitor data freshness, missing records, bad zones, and city reporting quality.

Scheduled intelligence
Morning briefs and nightly plans

Agents run continuously, not only when a user opens a chat box.

click to advance
Exact Agent Flow
How Synkora executes work
Synkora
Make the product understandable in 20 seconds

## A Synkora agent is a governed loop, not a prompt.

01 / Trigger
Schedule, chat, webhook, Slack

Example: 6:12 AM fleet brief or rider support message.

02 / Context
Tenant, agent config, KB, policy

Load city rules, refund policy, SLA, model config, and credentials.

03 / Tools
Fleet, maps, events, tickets

Call micromobility, Mapbox, weather, events, Zendesk, DB, and files.

04 / Intelligence
Summarize and rank

Compute low battery, idle vehicles, fees, MDS anomalies, demand gaps.

05 / Explain
Show the reason

Return cards, maps, recommended actions, sources, and confidence.

06 / Approval
Gate money and operations

Refunds, ranger tasks, reports, tickets, and rebalancing wait for approval.

07 / Action
Create work

Update task, issue refund, create ticket, send Slack, draft city report.

08 / Trace
Observe and learn

Log tool calls, approvals, usage, cost, outcomes, and future context.

rider says: "I was charged a parking fee but I ended inside the zone"
agent: trip + GPS + zone + policy -> approve refund or escalate
click to advance
Agent Interaction Surfaces
Same agent, many front doors
Synkora
Make the platform feel real

# Synkora shows up where each user already works.

Riders use mobile and WhatsApp. Operators use dashboard, mobile, and Slack. Owners get email and executive Slack briefs. The same agent runtime powers all of them.

Synkora Ops
# fleet-alerts 08:45
S
Synkora Fleet Agent
37 low-battery vehicles and 12 geofence exceptions detected before commute peak.
Recommended: create Charge Route A and Recovery Route B. Estimated rider availability impact: +42 vehicles by 9:30.
Create ranger tasks
Open map
Message #fleet-alerts
R
Rider 8842
I ended in the parking zone but got charged a fee.
I checked your trip GPS, parking boundary, vehicle lock, and policy. GPS drift likely caused the fee.
Refund request is ready. You will get an update in this chat.
Type a message send
This is the uniqueness: one governed agent brain, multiple role-specific interfaces.
click to advance
Rider Interaction Flow
Mobile app + WhatsApp support
Synkora
A bad ride should become an instant recovery moment

## The rider does not care which system failed. Synkora checks all of them.

14:08 5G 81%
Otoride Trip live
End ride blocked

Vehicle is inside Parking Area P-14, but GPS reads 9m outside. Timer is still running.

End ride
Get help
Ride Map Wallet Help
14:09 5G 80%
Support
I cannot end the ride and I am getting charged.
I checked trip state, vehicle lock, GPS trail, parking area, wallet, and fee policy.
Billing is stopped. The parking fee looks invalid because of geofence drift.
Can you refund the overcharge?
Refund approval is ready. You will see the receipt here.
Ask Synkora...send
Ride Map Wallet Help
14:10 5G 79%
Wallet Resolved
Ride ended

Synkora confirmed lock event and corrected the parking-zone mismatch.

Overcharge$2.40
Parking fee$3.80
Refund Approved
Rider trust signal

Ticket closed, wallet credited, P-14 geofence flagged for ops review.

Ride Map Wallet Help
click to advance
CEO + Operator Interfaces
Email, Slack, mobile app, dashboard widget
Synkora
Gmail
Primary Search mail 06:30 AM
Synkora Daily Fleet Health: rider trust up, MDS clean...6:30 AM
City Ops Permit data export accepted for last cycle 6:12 AM

### Daily Fleet Health: rider trust up, MDS clean, margin leak found

Synkora brief for CEO: fleet is operationally healthy, but University West is margin-negative after refunds, parking-fee reversals, and idle time.

92%MDS health
+31%Demand
23 Rider issues
$4.20 Margin
Open Synkora
Reply in Slack
9:41 5G 92%
Operator
Rebalance plan

Move 40 scooters to Stadium North. Pull 18 from University West before rain.

Low battery route

12 vehicles under 20%. 31 min pickup path sent to Ranger Team 2.

Approve
Directions
Tasks Map Agents More
9:41 5G 88%
Agent Chat live
Find low-battery vehicles near downtown.
Found 12 below 20%. Four are blocking high-demand blocks.
Give me directions and create the pickup task.
Task created. Route sent to Ranger Team 2 with stop order and ETA.
Open route
View task
Tasks Chat Map More
People understand Synkora when they see the interfaces: email, Slack, WhatsApp, mobile, dashboard, approvals.
click to advance
Synkora Dashboard + Widget
Fleet health, prediction, demand, rider issues
Synkora
Exact workflow inside the web dashboard

# The operator resolves a rider ticket without leaving Synkora.

The dashboard gives fleet health, predicted demand, MDS health, and rider issue queues. The embedded agent widget handles the support ticket and explains the action.

app.synkora.ai/micromobility/command-center
raju@synkora
Synkora
Micromobility Command Live
91%Fleet health
96%MDS health
+34%Demand spike
23 Rider issues
Ticket #RID-8842 Rider charged parking fee after ending inside Parking Area P-14. GPS drift suspected. Overcharge and fee refund ready for approval.
Agent widget
Operator: resolve ticket #RID-8842. Was this parking fee valid?
Synkora checked trip, vehicle lock, GPS trail, parking polygon, rider wallet, pricing, and refund policy.
Finding: rider ended inside P-14. GPS drift triggered the parking fee and overcharge.
Action: refund $3.80, credit $2.40 overcharge, notify rider, flag P-14 geofence.
Approve
Escalate
This shows Synkora as a real product surface: dashboard + data + ticket + agent action + approval.
click to advance
Stakeholder Storyboard
Use cases that expose platform strength
Synkora
Pitch this as one fleet business day

# Six scenes. One platform story.

Each scene is easy for an operator to understand, visible to riders through availability, and valuable to owners through utilization, margin, and risk control.

01 / 6:12 AM
Morning Ops Brief

Ops gets the first dispatch plan. Riders get charged vehicles before commute demand.

02 / 8:45 AM
Ranger Dispatch Agent

Ops approves work. Riders avoid broken or unavailable vehicles. Owners reduce wasted labor.

03 / Realtime
Rider Trust Agent

Resolve end-ride failures, refunds, parking fees, overcharges, and support escalations.

04 / 11:30 AM
Demand Spike Agent

Ops moves supply before demand. Riders find vehicles near hotspots. Owners capture revenue.

05 / 2:00 PM
City Compliance Agent

Ops answers the city. Riders keep access. Owners protect the operating license.

06 / 5:30 PM
Margin and Fleet Mix Agent

Owners see margin by vehicle and zone. Ops knows what to repeat tomorrow.

The wedge: solve ops action and rider trust, then prove owner margin.
click to advance
Rider Trust Workflows
Instant support and governed refunds
Synkora
Rider trust is where the brand is won or lost

## Handle rider problems instantly, but keep money decisions governed.

End ride issue
"I cannot end my ride."

Check trip state, lock telemetry, GPS, parking zone, and create an emergency support path.

Refund
"The scooter failed."

Verify trip duration, vehicle health, fault signals, and approve policy-based credit or refund.

Overcharge
"Why was I charged extra?"

Explain ride time, parking fee, no-parking penalty, pause time, and wallet adjustment.

Parking dispute
"The app says parking is invalid."

Check zone rules, photo evidence, GPS drift, geofence boundaries, and city parking rules.

Safety and trust
Bad trip becomes a recovery moment.

Escalate safety issues, update support tickets, and feed repeated failures back to fleet ops.

Owner control
Refund leakage stays visible.

Track refund reasons, fee disputes, vehicle fault clusters, and rider trust trends by zone.

Example governed action

Refund $3.80 parking fee because GPS drift placed the rider outside the valid zone. Log reason and flag geofence for review.

Escalate
Approve
click to advance
Scene 01 / 6:12 AM
Morning Ops Brief
Synkora
The first hook for operators, riders, and owners

# The first dispatch plan is ready before standup.

The agent scans live vehicles, batteries, idle time, maintenance flags, geofence alerts, IoT faults, and task queues while the team is still coming online.

Operator: first dispatch plan. Rider: more charged vehicles at commute time. Owner: fewer dead assets sitting in the street.

842 Live vehicles
91% Operational
37 Charge first
64 Redeploy
6:12 AM priority queue
Charge route A
37 low battery
Redeploy idle units
64 idle 4h+
Recover zone exceptions
12 outside zones
Maintenance hold
18 in service
First approval of the day

Create a charging pickup route for the 12 lowest-battery vehicles before commute demand starts.

Edit
Create
click to advance
Scene 02 / 11:30 AM
Demand Spike and Rebalancing
Synkora
The next incident is demand, not hardware

# Pre-position supply before the city notices

At 11:30, a stadium event, rain forecast, and live supply gap change the plan. Riders need vehicles near the hotspot, and owners need that demand captured.

06:00
Transit hub still thin

Morning movement left three adjacent zones short for lunch traffic.

+28
17:00
Stadium exit spike

Event context creates directional demand near exits after 17:00.

+40
22:00
Residential surplus

Pull units from zones likely to stay idle after the rain starts.

-18
Benefit chain: operator approves the move -> rider finds a vehicle -> owner captures the peak.
click to advance
Scene 03 / 2:00 PM
City Compliance and Reporting
Synkora
The city emails before the afternoon rush

# Answer permit risk with facts, not panic

Synkora retrieves city rules from the knowledge base, checks live fleet counts and zones, then drafts the response with evidence attached.

Permit cap watch

Compare deployed vehicles against city caps before the business receives a violation notice.

76%
Zone exception cleanup

Use maps and parking-area tools to identify violations and generate relocation work.

18
MDS data health

Detect stale feeds, missing trips, bad status changes, and reporting anomalies before city submission.

92%
Benefit chain: clean MDS data -> fewer city surprises -> stronger rider access and permit trust.
click to advance
Scene 04 / 5:30 PM
Owner asks for the day back
Synkora
The close of the business day

# What changed today?

After the brief, tasks, rebalancing, and compliance checks, the owner needs a clean answer: did riders find vehicles, did utilization improve, and where did margin leak?

Platform strength exposed: chat UX, structured fleet cards, maps, charts, generated reports, multi-channel delivery, and traceable recommendations.

Fleet Ops Agent
Live
What changed after today's actions, and what should we do tomorrow?
The morning charging route recovered 29 vehicles, the stadium move prevented the largest supply gap, and University West is still margin-negative after ranger labor.
+40 Recovered
-18 Still idle
$4.20 Avg margin
Prepare tomorrow plan?

Draft 6 AM dispatch plan, margin summary, and city compliance brief for review.

Edit
Approve
Ask about riders, vehicles, zones, margin, tasks, or reports...
click to advance
Why Synkora
Why the story requires a platform
Synkora
What the whole business just saw

## This is not one clever chatbot. It is an operating system for mobility outcomes.

01
Fleet ops automation

Scheduled briefs, live rebalancing, ranger tasks, and maintenance workflows.

02
Rider trust automation

End-ride issues, refunds, overcharges, parking fees, and support escalation.

03
MDS and data health

Freshness checks, missing trips, bad states, city exports, and anomaly alerts.

04
Multi-channel deployment

Dashboard, Slack, WhatsApp, Teams, widget, REST API, and scheduled jobs.

05
Governed actions

Human approvals, audit logs, observability, traces, and cost visibility.

06
Owner-controlled platform

Self-host, BYO LLM keys, tenant isolation, quotas, billing, and API-first control.

Positioning line: Synkora improves operations, rider availability, and owner economics in one governed loop.
click to advance
Pilot Story
How to sell it to the business
Synkora
Recommended pilot narrative

# Sell the first 14 days as one business story

Do not pitch abstract AI. Pitch the loop: operators act faster, riders find better vehicles, and owners see the margin impact of every approved move.

Morning brief Rider support MDS health Owner margin
01
Days 1-3: connect the operating surface

Configure vehicles, trips, riders, tasks, fleets, support, payments, parking zones, reports, maps, and channels.

02
Days 4-7: ship ops + rider trust

Deliver fleet health, low-battery triage, end-ride support, refund review, overcharge explanations, and approvals.

03
Days 8-11: add demand + city health

Use weather, events, historical demand, service areas, MDS feed health, and map output to prevent surprises.

04
Days 12-14: close with proof

Show rider trust recovery, owner margin, MDS health, traces, cost, and an executive summary of approved actions.

Close: start with one daily story, expand into every decision that affects riders and margin.
click to advance