03 Parties & CRM
Contacts
Contact create flow, lists, and groups.
Illustrations on this page are conceptual examples — not screenshots of the live system.
How you can use it
The same Fleet module supports different transport models — pick the scenarios that match your operation.
Contacts in daily operations
Contact create flow, lists, and groups.
Client & partner records
Contacts for sales, billing, and CRM teams — typical in Bangladesh contract carriage businesses.
Client and shipper profiles with…
Teams use Contacts when they need client and shipper profiles with contact persons — without maintaining a separate spreadsheet or WhatsApp thread.
Contact groups for pricing and…
Teams use Contacts when they need contact groups for pricing and reporting — without maintaining a separate spreadsheet or WhatsApp thread.
Benefits for your team
What improves when vehicle data lives in one place instead of spreadsheets and phone calls.
Client and shipper profiles with…
Contacts helps because client and shipper profiles with contact persons — recorded inside the VMS audit trail instead of informal channels.
Contact groups for pricing and…
Contacts helps because contact groups for pricing and reporting — recorded inside the VMS audit trail instead of informal channels.
Supports trip billing and location…
Contacts helps because supports trip billing and location sharing — recorded inside the VMS audit trail instead of informal channels.
History of communication and linked…
Contacts helps because history of communication and linked trips — recorded inside the VMS audit trail instead of informal channels.
Makes daily work easier
Less chasing, less re-entry, fewer surprises on the morning dispatch board.
- Contacts supports view, add, list — so users do not jump between unrelated tools for the same task.
- Less manual follow-up: client and shipper profiles with contact persons
- Less manual follow-up: contact groups for pricing and reporting
- Less manual follow-up: supports trip billing and location sharing
- Branch-scoped access means local teams open Contacts without seeing other depots' records.
Multi-user & mobile-ready
Different roles see different slices — desktop for planning, mobile for field, dashboard for leadership.
- Operations lead (desktop)Plans and supervises Contacts with full register access, filters, and exports.
- Branch user (tablet / laptop)Works on branch-scoped Contacts records — no cross-branch data leakage.
- Field staff (mobile)Submits or confirms Contacts tasks from phone — limited permissions, faster updates.
- Manager / approverReviews exceptions, approvals, and summaries inside Contacts without re-keying data.
- Owner / executive (dashboard)Reads KPI widgets fed by Contacts — not day-to-day data entry screens.
Works with your other modules
Fleet is the vehicle master — other modules read from it so data stays consistent across the platform.
- TripsTrip records pull vehicle, driver, and billing context from Contacts.
- AgentsContacts and Agents share the same platform data — no duplicate entry between modules.
- SMSContacts and SMS share the same platform data — no duplicate entry between modules.
- VendorsContacts and Vendors share the same platform data — no duplicate entry between modules.
- File ManagerContacts and File Manager share the same platform data — no duplicate entry between modules.
- ReportsReport hub aggregates Contacts metrics for branch and management packs.