Customers
Manage the people and businesses that request deliveries through your organization.
What Is a Customer?
A customer in Deliverty Hub represents the person or business that requests a delivery. Every task is linked to a customer record, which stores their contact information, delivery preferences, and history. Customers are the senders or recipients of packages — they are the reason tasks exist.
Customers are organization-scoped, meaning each organization maintains its own independent customer database. The same physical person can exist as separate customer records in different organizations with no data shared between tenants.
Customers are not the same as platform users. A user is someone who logs into Deliverty Hub (admins, dispatchers, agents). A customer is a recipient/sender in the delivery workflow. Customers may optionally have a linked user account for features like notification preferences and self-service tracking, but many customers exist only as contact records.
Customer Profile
Each customer record contains the following information:
| Field | Type | Required | Description |
|---|---|---|---|
name |
String | Yes | Full name of the customer |
email |
String | No | Email address for notifications and communication |
phone |
String | No | Phone number for SMS notifications and agent contact |
address |
String | No | Default address used for pre-filling delivery locations |
notes |
String | No | Internal notes about the customer (delivery preferences, access codes, etc.) |
user |
User | No | Optional linked user account for self-service features |
organization |
Organization | Yes | The organization this customer belongs to (auto-set) |
Managing Customers
Customers are managed through the Customers section in the dashboard. Here you can:
Creating Customers
- Manual creation: Dispatchers can add customers directly from the dashboard by entering their name, contact details, and optional address.
- During task creation: When creating a new task, you can select an existing customer or create a new one inline. The new customer record is saved for future use.
- Via API / Channels: When tasks are created programmatically through channels (e.g., from an e-commerce integration), customer records are created automatically from the incoming order data. If a matching customer already exists (based on phone or email), the existing record is reused.
Viewing and Searching
The customer list in the dashboard supports:
- Search: Find customers by name, email, or phone number.
- Pagination: Results are paginated with 20 customers per page by default.
- Detail view: Click on a customer to see their full profile and delivery history.
Editing Customers
Customer records can be updated at any time. Changes to contact information (email, phone) will affect future notifications for that customer's tasks. Historical task records are not affected by profile changes.
Delivery History
Each customer's profile includes a complete history of all tasks associated with them. The delivery history shows:
- Task ID and type (pickup, delivery, cash collection, etc.)
- Task status (completed, cancelled, in transit, etc.)
- Pickup and drop-off locations
- Assigned agent
- Payment information and amount
- Creation date and completion date
This history is valuable for understanding customer activity, resolving disputes, and identifying high-volume customers who may benefit from priority service.
Customer Notifications
Customers can receive automated notifications about their delivery status through multiple channels:
| Event | Channels | Description |
|---|---|---|
| Task Created | In-app, Email | Confirmation that a delivery has been requested for the customer |
| Task Accepted | In-app, Email | An agent has accepted the delivery assignment |
| In Transit | In-app, Email, SMS | The delivery is on its way to the customer |
| Completed | In-app, Email, SMS | The delivery has been successfully completed |
| Cancelled | In-app, Email | The delivery has been cancelled |
Email notifications require a valid email address on the customer record. SMS notifications require a valid phone number. If either field is missing, that notification channel is silently skipped for the customer. See Notifications for more details.
Address Book
Customers can have multiple saved addresses in their profile. When creating a task for a returning customer, dispatchers can select from previously used addresses instead of entering a new one each time. This speeds up task creation and reduces data entry errors.
Addresses include:
- Formatted address string (street, city, postal code)
- GPS coordinates (latitude and longitude) for map positioning and distance calculations
- Optional label (e.g., "Home", "Office", "Warehouse")
- Optional contact person and phone number at the address
Organization Scoping
Customer data is strictly isolated per organization:
- Organization A cannot see, search, or modify customers belonging to Organization B.
- All customer queries (from the dashboard or API) are automatically filtered by the current organization.
- When creating a task, only customers within your organization appear in the customer selection dropdown.
- Super Admins can access customers across all organizations for support purposes.