Let your WhatsApp AI assistant read the shipment status Shiprocket returns. Configure the merchant credentials, test an AWB or order lookup, and leave fulfilment changes to your operations team.
Illustrative exchange. A real tracking response must use the provider result, not a fabricated status or delivery time.
The dedicated adapter logs in with configured Shiprocket credentials and reads order or AWB tracking information for an enabled WhatsApp AI tool. It answers from the returned response; it does not create shipments, labels or pickups.
Shipment notifications are a separate merchant-configured event workflow. A tracking lookup does not automatically subscribe every customer to proactive updates. WhatsApp CRM access, AI credit for replies, provider credentials and message eligibility are prerequisites.
Read the tracking details available for the identifier supplied by the customer.
Search provider orders using supported inputs. Search results are limited, not a complete shipment history.
Map a merchant-installed webhook and customer phone to a matching message rule.
Let a person handle address changes, non-delivery, pickup or refund requests.
Answer the customer who already has an AWB with the status the source returns.
Ask for a clearer identifier instead of exposing another customer’s shipment.
Keep NDR resolution, pickups and changes with the responsible team.
Tracking data is only as current and complete as the provider response. An in-transit status does not establish a delivery deadline. Share an ETA only when the source actually returns it and your policy permits that wording. An accepted lookup is not a guarantee that the parcel is moving or that a courier will meet an estimate.
A customer-provided identifier is not a separate identity verification. Decide which fields are safe to disclose and how your business handles sensitive information. Search can return limited or ambiguous matches; do not select another person’s shipment simply to produce an answer.
For business-initiated shipment updates, your merchant system must emit the event with a usable phone and the correct shipment reference. Map shipped or delivery events to the message you intend to send, then test event receipt and message dispatch independently.
Do not assume the read adapter continuously polls carriers or resolves non-delivery reports. Outside the WhatsApp customer-service window, an appropriate approved-template path and consent are required. The integration does not create shipments, arrange reverse logistics or automatically refund a buyer.
Your warehouse, carrier and store remain responsible for shipment creation, address changes and delivery exceptions. Repli’s configured tool reads available order and tracking data during a conversation. If you add an external write endpoint, its authorization and business checks must be tested separately.
Compare the source response with the customer-facing answer before enabling the tool for a wider audience. Review wrong identifiers, expired credentials, provider errors and insufficient AI credit. A successful sample is useful evidence for your configuration, not a guarantee for every shipment.
No. The dedicated Shiprocket adapter is read-only; operational changes belong to your team or a separately configured system.
A merchant-configured shipment webhook is a separate event workflow. It needs phone mapping, a matching rule and a compliant sending path.
No. The answer can use only details returned by Shiprocket. Missing data must not become an invented delivery time.
WhatsApp CRM plan access and AI reply credit are separate. Meta template charges and any external-provider fees may also apply; check pricing before connecting.
Repli is a third-party integration. This page does not claim Shiprocket endorsement.
Pricing · All features · How it works · Blog