How it works

How Delegate Works

Delegate helps people send approved items through reviewed travelers, partner hubs, and documented pilot handoffs — so every package has a clear path and accountability.

Sender
Delegate
Traveler
Hub
Recipient

The simple idea

Someone is already flying.

Every week, people fly from Seattle and Toronto to Addis Ababa.

At the same time, families and small sellers need to send real things home: laptops, phones, school items, documents, books, clothes, gifts, and other approved goods.

Today, this usually happens informally through WhatsApp groups, friends, relatives, and community referrals.

Delegate does not invent this behavior.

Delegate makes it safer, clearer, and more accountable.

Sender submits. Delegate reviews. Hub records. Traveler carries when approved.

The four people in every delivery

Every delivery has clear roles.

Sender

The person who wants to send an approved item. They submit the item, destination, declared value, recipient details, and suggested traveler reward.

Traveler

Already flying on the route. During the pilot, they submit trip details and Delegate Ops coordinates manually if an approved request fits.

Hub

A reviewed pickup or drop-off point. Hubs help record intake, store packages temporarily, and record handoff. Hubs do not handle money, negotiate pricing, or resolve disputes.

Delegate Operations

Reviews requests, reviews travelers and hubs, documents packages, manages QR and seal records, and handles issues.

Manual review

No one carries without Delegate review.

Every traveler and every hub application is reviewed before pilot coordination. The pilot does not claim automated KYC or instant approval.

Delegate Ops may request identity, route, business, or contact information before approving a person or location for a specific pilot role.

What we review

Identity, contact details, trip route, item comfort, and pilot suitability.

When it happens

Before Delegate Ops coordinates a traveler or activates a hub for pilot work.

What we store

Operational records needed for review and coordination. We do not claim an automated identity-provider integration is live.

If there is a concern

Delegate Ops can pause, decline, or request more information. No anonymous carriers.

Step-by-step flow

From request to handoff.

  1. 01

    Send request

    The sender submits what they want to send, where it is going, and how much reward they want to offer the traveler.

  2. 02

    Pilot coordination

    Delegate Ops reviews the request and coordinates manually with approved travelers on the corridor.

  3. 03

    Package documented

    Once approved, the item can be documented with photos, item details, Bag UID, Seal UID, and QR code where the package setup flow is used.

  4. 04

    Scanned through the route

    The package is scanned at each major custody point. The scan creates a timestamped record.

  5. 05

    Confirmed handoff

    At the end, the package is released through the approved handoff process and recorded for pilot accountability.

QR identity

Every package gets a QR identity.

Packages documented through the pilot setup flow can receive a unique QR code.

That QR code does not expose private information.

It simply opens the secure Delegate scan page.

When an authorized pilot operator scans it, the app checks the package ID and security token before showing scan details.

The QR helps answer

  • Where is this package?
  • Who scanned it?
  • When was it scanned?
  • Was the seal intact?
  • What is the next step?
The QR code is not the trust by itself. The scan record is the trust.

Seal

The seal shows whether the package was touched.

Delegate uses tamper-evident bags and seals.

That means if someone tries to open or remove the seal, there should be visible evidence.

A seal is not magic. It works together with:

photo recordsBag UIDSeal UIDQR scanshandoff recordshub confirmationpilot handoff confirmation
The seal does not replace trust. It creates evidence.

At a hub

What does a Delegate Hub do?

A Delegate Hub is a trusted community location. Depending on the hub type, it may help with pickup, drop-off, safe temporary storage, and scan confirmation. Most hubs do not open packages.

Hubs do

  • scan package in
  • confirm seal condition
  • store it safely
  • scan package out
  • report issues immediately

Hubs do not

  • handle money
  • negotiate traveler rewards
  • resolve disputes
  • release packages without app confirmation
  • act as couriers

When something looks wrong

If something looks wrong, the package stops.

Delegate is designed to stop risky packages before they continue. The package is stopped if:

  • the seal is broken
  • the QR does not scan
  • the item does not match the record
  • someone asks to skip the app
  • someone tries to move the package off-platform
  • the wrong person arrives for pickup
  • the recipient cannot confirm pickup

When that happens, the app creates an issue record and Delegate Operations reviews it.

No scan, no movement. Broken seal, stop. Wrong person, no release.

What can be sent

Approved items only.

Delegate starts with conservative, low-risk item categories.

Common approved

  • · documents
  • · books
  • · school items
  • · clothes
  • · shoes
  • · small electronics
  • · phones
  • · laptops
  • · family gifts
  • · packaged personal goods

Requires manual review

  • · medicine
  • · supplements
  • · liquids
  • · cosmetics
  • · batteries
  • · high-value electronics
  • · fragile goods
  • · bulk quantities
  • · multiple identical items

Never allowed

  • · cash
  • · weapons
  • · illegal substances
  • · mystery packages
  • · counterfeit goods
  • · explosives
  • · dangerous chemicals
  • · anything the traveler cannot inspect
If the item cannot be clearly described, documented, and accepted, it does not move through Delegate.

How travelers earn

Travelers earn from trips they already take.

Travelers do not need to become couriers.

They are people already flying on the route.

During the pilot, Delegate Ops contacts reviewed travelers when a request may fit their route. The traveler reviews the item details, reward, and route before agreeing.

Travelers should never carry a mystery package.

Travelers should never carry anything they are uncomfortable with.

You are already flying. Delegate lets the empty space help pay for the trip.

Payment & pricing

Pilot payments are coordinated after confirmed handoff.

During the pilot, payment is handled manually by Delegate. When you submit a Send Request, nothing is charged. Delegate confirms the total with you before coordinating a traveler.

Traveler reward release is coordinated manually by Delegate Ops after the recipient handoff is confirmed. Held-payment escrow is part of our roadmap, not yet live.

How the reward is set

The sender suggests a traveler reward.

The traveler can agree or decline after reviewing the request.

Delegate adds a clear service fee.

If a hub is used, the hub may receive a fixed handoff fee.

The total is confirmed before Delegate Ops coordinates the traveler.

The market sets the reward. Delegate provides the trust layer.

Current routes

Opening routes.

Delegate is starting narrow on purpose.

Seattle → Addis Ababa
Toronto → Addis Ababa

We are starting with one destination from two diaspora origins so we can build trust, train hubs, learn the route, and improve the system before expanding.

The route already exists

Delegate makes it reliable.

People are already flying.

Families are already sending.

Travelers are already carrying things informally.

Delegate adds the missing layer: review, documentation, QR-supported handoff, partner hubs, and accountability.