Answers for moving
business forward.

Use the Partner page to submit your organization, market, locations, primary use case, and transportation or delivery needs.

No. A submission records business interest only. It does not create an account, guarantee service availability, confirm pricing, or establish commercial terms.

AkiGO may review the request for operational fit, market readiness, service eligibility, volume, support needs, and technical requirements before deciding whether to follow up.

Review time can vary based on request completeness, market status, service complexity, internal capacity, and whether additional information is required.

No. Support depends on the use case, eligible services, market coverage, operational readiness, legal requirements, safety standards, and available business workflows.

Yes. AkiGO may collect business interest before a market opens, but registration does not guarantee launch selection or timing.

Account setup may require legal organization details, primary contacts, business locations, billing information, approved users, service needs, and operational instructions.

AkiGO business workflows may support multiple approved locations where that capability is enabled for the organization and market.

Yes, where supported. Pickup notes, delivery instructions, service contacts, and location details should be configured accurately for each location.

Activation occurs only after required review, account setup, market availability, service eligibility, and any applicable commercial or compliance steps are complete.

Approved administrators should be able to update eligible account details, users, locations, and instructions. Certain legal, billing, or compliance changes may require review.

Potential requests may include eligible meals, retail goods, documents, packages, and other approved local items, subject to market and item restrictions.

A request may require pickup and drop-off addresses, contact names, phone numbers, eligible item details, size or handling notes, timing, and delivery instructions.

Where available, the business experience is designed to show request status, assignment progress, pickup, route activity, and completion updates.

Proof-of-delivery options may include completion status, recipient confirmation, photo evidence, signature, or other records where enabled and appropriate.

Prohibited items may include illegal goods, hazardous materials, regulated substances, weapons, cash, certain high-value goods, and any item restricted by law or AkiGO policy.

The driver or support workflow may attempt contact, document the issue, follow return or failed-delivery instructions, and update the request according to the applicable policy.

Scheduled transportation may be available for eligible markets, service types, account configurations, and request details.

Recurring transportation or delivery may be supported for approved use cases where the account and market have the required scheduling workflow.

The scheduling window depends on the service, market, account configuration, and operational capacity shown in the business experience.

No. Scheduling records the request in advance but does not guarantee assignment. Fulfillment depends on eligibility, driver availability, coverage, and operating conditions.

Eligible changes and cancellation options depend on the request status, assignment progress, timing, and applicable business policy.

Supported methods may include eligible cards, approved account billing, wallet balance, or other business payment arrangements where enabled.

Payment timing may depend on the request type and account setup. A charge may be authorized before fulfillment and completed or adjusted after the request is finalized.

Business accounts may provide transaction records, receipts, statements, or invoices where that billing workflow is enabled.

Multiple approved payment methods may be supported depending on the account configuration, user role, and billing policy.

Use the business support workflow and provide the request reference, charge details, date, and explanation. AkiGO will review the available records and applicable policy.

Adjustments may occur for waiting time, route changes, approved fees, cancellations, corrections, refunds, or other request-specific review.

Yes, where team access is enabled. Each approved user should have an individual login and assigned role rather than sharing credentials.

Possible roles may include account administrator, requester, dispatcher, billing user, viewer, or support contact, depending on the business configuration.

Role and location restrictions may be supported so users can access only the requests, locations, billing information, or administrative tools they need.

Approved account administrators should manage team access, subject to any verification or security requirements.

An administrator should promptly remove or disable access, review active sessions, and update any shared operational or billing contacts.

No. Shared passwords reduce accountability and security. Each approved user should have a separate account with the correct role.

Use the Help Center, Contact page, or business support workflow when available. Choose the category that best matches the account, request, billing, technical, safety, or partnership issue.

Include the organization name, account email, request or charge reference, date, location, screenshots where appropriate, and a clear description of the problem.

Use the safety or incident workflow and provide accurate request details. Call local emergency services immediately when there is immediate danger.

An account administrator should confirm the user’s access and role. Use account support for unresolved login, verification, or permission problems.

AkiGO should not claim continuous support coverage unless that service is operational. Available channels and response expectations will be shown in the applicable business experience.