Delivery Integrations

A delivery integration lets your agents take an order from conversation to shipment without requiring a Shopify store. With a supported service such as Nova Post, an agent can collect the order and recipient details, find a suitable branch or location, quote delivery, create a waybill after customer confirmation, check shipment status, and notify your fulfillment team through CRM.

Navigation: Open General → Integrations, expand Deliveries.

Before connecting delivery

Use this feature when customers place orders directly by phone, email, or chat and you want the same agent to prepare delivery instead of asking a teammate to re-enter the details. It is especially useful for order-booking workflows that do not use Shopify.

You need an active account with a delivery service supported by the connection dialog. Gather the business sender details requested on screen. Delivery-bearing agent actions also require a working CRM integration, which gives your team a record to review and fulfill.

Connect and verify

Select Connect a Delivery.
Choose the delivery service.
Complete the fields shown for that service.
Select or enter the sender profile and sender location when requested.
Save the connection.
Wait for verification.

Do not enable agent delivery actions while the connection shows Verification pending or Verification failed.

Understand connection status

Connected — verified, enabled, and selectable.
Disabled — saved but not available to agents.
Verification pending — not ready for live use.
Verification failed — review details and verify again.
Prepayment only — the current connection supports only that customer payment option in Versafy.

Set workspace defaults

Workspace defaults keep payment and delivery rules consistent across multiple order-taking agents. After at least one verified connection is active, use Default for all agents to select common behavior. The form can include:

default delivery integration;
customer merchandise payment options;
who pays the carrier delivery price;
CRM stage or tags used when an order is ready for fulfillment.

Defaults do not automatically turn delivery on for every agent. Each agent must opt in.

Enable delivery for an agent

Enable delivery only on agents that should collect and confirm shipment-bearing orders. For example, a Voice Agent can complete an order during a call, while a Messaging Agent can help a customer choose a location and prepare the waybill in chat.

Open a Voice, Email, or Messaging Agent and select Delivery.

Connect CRM first if the page asks you to.
Enable delivery for the agent.
Use workspace defaults or select an agent-specific connection.
Review merchandise-payment and delivery-payer options.
Select only the agent delivery actions needed.
Save and test with a non-customer scenario.

The agent should confirm products, customer details, destination, payment choice, and delivery quote before creating a shipment.

Review recent delivery operations

Use recent operations to confirm that a promised shipment was created and that your team was notified before anyone repeats the action. The Deliveries card shows recent operations with order, recipient, destination, payment, shipment status, tracking number, CRM status, and creation time.

Common states include Creating, Created, Needs verification, Failed, and Cancelled. CRM status indicates whether the fulfillment team was notified.

Recover an uncertain operation

Use a recovery or reconcile action only when you have independently confirmed the shipment in the delivery service and can provide the exact requested reference. Recovery links an existing external result; it should not be used to create another shipment.

If an operation is uncertain, first search using the visible order marker, customer, and approximate time. Repeating a create action can produce duplicates.

Troubleshoot delivery

Agent Delivery settings are locked

Connect and enable CRM for that agent, then connect and verify a delivery service. Refresh the agent editor afterward.

Delivery creation is blocked

Read the blocker shown in the agent’s Delivery tab. Common causes include unverified prices, incomplete customer information, unavailable payment options, or missing CRM routing.

Shipment was created but CRM was not updated

Check the recent operation’s CRM status. Use the guided recovery action only after verifying what already exists in both systems.