Fast & reliable service in Buea
AHLink Delivery
Your local delivery team for food, parcels, documents, pharmacy pickups, market errands, and business deliveries, coordinated from request to handover.
Local dispatch teamBranded AHLink ridersWhatsApp follow-up
Local knowledge. Professional coordination.
One request, one accountable delivery flow
AHLink connects the person placing the order, the receiver, dispatch, and the assigned rider. Our team confirms the details, coordinates pickup, and remains available for follow-up.
Start a delivery request1Tell us what is moving
Share the pickup, destination, parcel type, and reachable WhatsApp contacts.
2Dispatch confirms
Our office reviews the request, confirms the delivery arrangement, and assigns an AHLink rider.
3We coordinate the handover
The rider handles pickup and delivery while dispatch keeps the request connected to the right people.
Operations Command Center
Today's action queue
Immediate items that need office attention for the selected day.
Real-time shift control board
Financial closure view for programmed rides: MoMo, cash, unpaid delivered rides, and balancing readiness.
Completed rides per rider
| Rider | Day | Night | Total | Avg duration day | Avg duration night | Expected stop points |
|---|
Updated.
Delivery Dispatch Console
Create a ride and assign a rider. Office can update statuses too.
Dispatch-controlled company phones
Live Rider Tracking
Dispatch assigns each registered company phone to a rider and controls when duty tracking begins and ends.
0 liveOpen full map page
Admin phone pairing
ADMIN ONLY
Enter the four-digit code displayed on the physical phone, then assign its matching sticker ID and a clear office name.
| Company phone | Approval | Assigned rider | Duty | Last contact | Controlled by | Admin setup |
|---|---|---|---|---|---|---|
| Open AHLink Rider once to register a company phone. | ||||||
Delivery route planner
Enter pickup and delivery points to estimate distance, time, and best route before assigning a rider.
Route playbackLoad a dated route to begin.
--:----:--
Live riderLive
Locating rider...
Waiting for GPSSpeed unavailable
LiveStaleRoute trail
| Rider | Current location | Current ride | Last update | Speed | Accuracy | Battery | Status |
|---|---|---|---|---|---|---|---|
| Waiting for rider locations. | |||||||
Live dispatch command board
Rider Fleet Status
All riders at a glance: availability, open rides, GPS freshness, phone battery, and delivery state.
Payment control
Real-time Shift Control Board
Delivered rides remain financially open until Cash is returned or MoMo is confirmed.
Shift continuity
Dispatch Handover Notes
Leave clear pending issues for the next dispatch or finance shift.
Client communication
WhatsApp Desk
Send delivery updates from the AHLink portal and keep replies visible to dispatch, finance, and admin.
Checking WhatsApp connection...
Inbox and recent replies
Loading WhatsApp inbox...
Online requests
Client Orders
Review requests submitted through the public order page before creating a ride. New requests appear automatically.
LiveChecking now
Open public form
| Request | Submitted | Client | Route | Package | Status | Actions |
|---|---|---|---|---|---|---|
| Loading client requests... | ||||||
Create Ride
Choose the applicable delivery zone. Use custom fee only for approved exceptions.
Use this when the three zone fees do not apply.
Standard Day fee applies.
Rides
| Ride | Date | Rider | Status | Workflow | Pickup / delivery / contact | Fee | Actions |
|---|
Line-haul and package movement
Trips, Vehicles, Manifests & Departure
Plan a vehicle trip, build the manifest from delivery rides, confirm packages as loaded, then release the trip for departure.
Vehicle setup
| Vehicle | Driver | Capacity | Status | Notes |
|---|
Create trip
| Trip | Route | Vehicle / driver | Manifest | Status | Actions |
|---|
Manifest workbench
Select a trip to build its manifest.
Available rides
| Ride | Package / route | Status | Action |
|---|
Add manual package
| Package | Client / receiver | Route | Count / weight | Loading | Actions |
|---|
Rider Operations & Compensation
Real-time ride workflow, selected-period compensation, paid status, and cash-return control.
Dispatch-managed company phone
Duty Location Tracking
This company phone is controlled by Dispatch. Keep it powered, connected, and with location enabled while on duty.
Waiting for DispatchDispatch will start and end duty tracking.
Selected-period rider compensation
The amount below is calculated only from the selected dates, so older paid months do not increase the current balance.
Cash collected and returned
Completed cash rides in the selected period, including what was collected, returned, and still pending to the office.
| Ride | Date | Shift | Vendor / Client | Fee | Payment status | Cash collected | Returned | Pending | Note |
|---|
Delivery details and paid status
Open and completed deliveries for the selected period. Paid status is allocated from payments recorded for the same period.
| Ride / date | Ordering client | Pickup contact | Receiver | Parcel details | Route | Status | Shift | Rider pay | Actions |
|---|
Payment history for selected period
| Date | Covered period | Amount | Paid from | Paid by | Notes |
|---|
Current rider board
| Ride | Route | Status | Actions |
|---|
Locations
Rider position updates for dispatch visibility.
| Rider | Name | Location | Updated |
|---|
Finance & Reconciliation Control Center
Petrol, expenses, salaries, delivery payment collection, Mobile Money, bank deposits, and payout tracking.
Petrol log
| Date | Rider | Total | Paid from | Note |
|---|
Other expenses
| Date | Category | Amount | Paid from | Note |
|---|
Salaries
| Month | Worker | Amount | Paid date | Paid from |
|---|
Monthly rider payout
| Rider | Name | Earned | Paid | Balance due | Action |
|---|
Completed delivery payment validation
Validate delivered Cash and MoMo rides. A ride is not financially closed until Cash is returned or MoMo is confirmed.
| Ride | Shift | Rider | Vendor / client | Mode | Fee | Payment status | Amount paid | Pending | Cash returned | Received / confirmed by | Note | Action |
|---|
Mobile Money reconciliation
Track MoMo inflows, transfers, cash-return deposits, and automatic deductions for the selected reconciliation date.
Add MoMo deposit (inflow)
Transfer MoMo -> Bank
| Time | Type | Dir | Amount | Party | Provider | Ref | Notes | Recorded by |
|---|
| Automatic deduction | Source | Amount |
|---|
Bank transactions & balance
| Date | Type | Amount | Ref |
|---|
| Automatic deduction | Source | Amount |
|---|
Daily finance report (print / PDF)
Generate a printable end-of-day finance report for admin review, stamping, and PDF saving.
Partner Settlement & Delivery Intelligence
A secure partner workspace for delivery visibility, monthly settlement summaries, payout tracking, and executive-ready pay statements.
Partner setup
Partner Monthly Settlement Statement
Generate a digital settlement certificate for vendor partners, including completed deliveries, compensation, paid amount, balance, QR login, and AHLink management verification.
| Ride | Date | Status | Client / route | Fee | Partner compensation | Payment | Action |
|---|
AHLink Financial Control
Dispatcher Balancing Control
Replace paper and WhatsApp balancing with a digital record focused on closing system balance, verified MoMo, cash, debts, discrepancy, and validation notes.
Balancing session
Shift close readiness checklist
The system checks delivered rides, cash return, MoMo confirmation, cancellation reasons, debts and handover before validation.
Shift opening and protected closing
Dispatch enters the balance received at handover. The closing system balance is calculated from Finance records and cannot be altered.
Enter the balance received when this shift began.
Actual cash, MoMo and debts
If discrepancy is not zero, continue investigation and write a clear note before validation.
Debt lines
Add amounts explaining why system balance and physical cash/MoMo differ: rider owes AHLink, AHLink owes someone, client owes, or other debt. To bring forward an old debt, load the validated balancing history for that day and click Call debt lines on the exact record.
| Party / person | Direction | Amount | Note | Source | Action |
|---|
Balancing note and validation
Validated balancing history
Admin control log with exact saved and validation time for each balancing session. Select one day or a full period, then call debt lines from the exact validated record you want to continue.
| Date | Saved time | Validated time | Shift | Dispatch | Dispatcher | Income | Expense | Actual | Discrepancy | Status | Actions |
|---|
Admin-only Intelligence
Client Growth & Performance Analytics
Backend analysis of ordering behavior, receiver-only leads, dormant clients, shift performance, rider productivity, and revenue patterns.
Analysis period
Place-order portal activity
Track how clients are adopting the public order portal, who submits most often, and which portal requests convert into real rides.
| Client | Submitted | Converted | Completed | Revenue | Last portal order | Last route |
|---|
Client conversion pipeline
Record WhatsApp outreach, client response, and follow-up action. If the client later orders, Intelligence will flag conversion beside that phone number.
New clients gained
First-time ordering clients in the selected period, including receivers who later returned to place their own orders.
| Client | Contact / pipeline | First order | Source | Orders | Completed | Revenue |
|---|
Graphical performance analysis
Plot completed rides, gross revenue, and projected income by days, weeks, months, or years.
Revenue versus expenses
Net income control
Expense breakdown
| Expense category | Amount | Source | Interpretation |
|---|
Daily completed delivery trend
Shift performance
Who should AHLink lure?
These people received deliveries during the selected period but have never appeared as ordering clients in the app.
| Lead | Contact / pipeline | Received deliveries | Last sender | Location | Suggested action |
|---|
Dormant clients to reactivate
| Client | Contact / pipeline | Last order | Days inactive | Previous completed | Previous revenue | Suggested action |
|---|
Location heatmap
Top delivery destinations by completed deliveries and revenue.
Peak-hour analysis
Busiest operating hours for staffing and rider planning.
Partner performance
| Partner | Deliveries | Revenue | Compensation | Unpaid balance | Monthly growth |
|---|
Top active clients
| Client | Contact / pipeline | Orders | Completed | Revenue | Top type |
|---|
Rider performance
| Rider | Completed | Open | Revenue | Avg min |
|---|
Monthly management report
Printable executive summary for management review.
Executive insights
Administrative control center
Administrative Control Center
Manage users, settings, partners, roles, PINs, and audit logs from one protected admin workspace.
Settings
Use {name} and {phone}; Intelligence WhatsApp buttons will open with this text.
WhatsApp Business templates
Prepare reusable delivery messages for dispatch. When Meta approves production templates, record their official names here.
Useful placeholders: {name}, {client}, {ride_id}, {fee}, {pickup}, {delivery}, {tracking_link}
| Template | Category | Meta approval | Status | Body | Action |
|---|---|---|---|---|---|
| Loading templates... | |||||
Client loyalty & promotions
Define percentage rewards for clients using the public order page. Use 0 converted orders when every portal client should qualify immediately.
Use 0 for all portal clients.
| Rule | Threshold | Reward | Status | Message | Action |
|---|
Active order-page clients
Review clients using the public order form. Apply a manual percentage discount or free-delivery waiver when management wants to reward a specific client.
Leave blank to run indefinitely.
| Client | Submitted | Converted | Last order | Revenue | Current promotion | Action |
|---|
Client-specific rewards
| Client | Reward | Reason | Expires | Status | Action |
|---|---|---|---|---|---|
| Loading client rewards... | |||||
Client portal accounts
Review optional client accounts used for delivery history, saved contacts, and loyalty bonuses. Guest ordering remains available.
| Client | Status | Portal orders | Linked rides | Last login | Action |
|---|---|---|---|---|---|
| Loading client accounts... | |||||
Restore misdated rides
Use this only when a dispatcher accidentally created rides on the wrong date. Load the wrong date, select the affected rides, then move only those rides to the correct operating day. The action is written to audit.
| Select | Ride | Created | Client | Rider | Status | Route | Fee |
|---|---|---|---|---|---|---|---|
| Load a date to review rides. | |||||||
Delivery fee catalogue
Maintain the public fee guide shown to clients on the order form. Use active/inactive instead of deleting historical pricing context.
| Zone | Title | Areas | Day | Night | Status | Actions |
|---|
Users
| User | Name | Role | Active | Rider ID | Partner ID | Action |
|---|
Deactivate rider account
This removes the rider from login and assignment lists, while keeping old delivery history for reports. Choose the rider, enter a reason, then type the confirmation phrase.
Partners
Create vendor partners first, then create a PARTNER user account with the same partner ID.
| Partner | Name | Contact | Phone | Default comp | Active |
|---|
Audit control rail
Review sensitive edits, ride corrections, cancellations, finance changes, user changes, and balancing validations in a cleaner control view.
| Time | User | Category | Action | Ride / record | Reason | Review summary |
|---|
Audit Trail
Operational actions recorded from the API layer.
| Time | User | Category | Action | Details |
|---|