The delivery notice that saves a second trip.
Your TMS or ERP posts the status, a journey sends the delivery window on WhatsApp with buttons to confirm or reschedule, and the customer's answer comes back to your system. Questions like “where is my parcel?” go to an AI that checks your tracking API.
Sign up through the site and get a US$5 test credit.
Four moments that decide a delivery.
Each one starts with an event from your system or a question from the customer, and runs on journeys, the inbox and the AI agent.
Out for delivery
Your TMS posts the event through the API, and the journey sends a utility template with the delivery window and buttons to confirm or reschedule.
Confirm or reschedule
The button reply comes back as a received message on your signed webhook, and the journey's condition can branch on whether the customer replied.
“Where is my parcel?”
An HTTP tool registered in the AI agent calls your tracking endpoint and answers with what it returns. It only reads: a request to change something goes to a person.
A failed attempt
The failed-delivery event starts a journey that offers a new attempt, and your team handles the exceptions with the whole history in Contact 360.
A notice with a plan B, not a blast twice.
The condition waits for WhatsApp's delivery signal, counted from the actual send. If it arrives, your system hears about it; if it doesn't, the backup goes out, and only then.
The backup branch is one you add in the builder. Outside Brazil it goes by email; SMS reaches Brazilian numbers only, on request.
The channels a delivery operation needs.
WhatsApp carries the notice and the reply. The others cover whoever WhatsApp doesn't reach, and the AI answers the questions that repeat.
Delivery windows with Confirm and Reschedule buttons, through utility templates. Replies come back to your system.
Explore WhatsAppBackup for numbers without WhatsApp, with the carrier's delivery receipt. Brazilian numbers; other countries on request.
Explore SMSProof of delivery, documents and the backup notice outside Brazil, from your own domain.
Explore EmailAnswers “where is my parcel?” by calling your tracking API, and hands anything else to a person.
Explore AI agentFewer missed deliveries, more proof.
What protects the operation is knowing the notice arrived and having a record of what was agreed.
What one delivery costs in messages.
You pay the monthly plan and each message at its published price. Waits, conditions and webhooks cost nothing.
International price list in US dollars. WhatsApp prices are for messages to the United Kingdom; each destination country has its own price.
What delivery teams ask before they start
Still unsure? Talk to the team that runs the platform.
How does my TMS talk to CCX?
Through the REST API: your system posts an event to start a journey, or sends the message directly. Statuses and replies come back through signed webhooks, retried if your endpoint fails.
Can customers reschedule in the chat?
Yes. The notice can carry Confirm and Reschedule buttons, the reply reaches your system through the webhook, and the exceptions land with your team in the inbox.
What if the customer doesn't have WhatsApp?
A journey condition waits for the delivery signal and, if it doesn't arrive in time, takes the backup branch: SMS for Brazilian numbers, or email.
Can the AI change an address or a delivery date?
No. The AI's HTTP tool only reads from your system. A request to change something goes to a person, with the conversation attached.
Is there a ready-made connector for my carrier or TMS?
No. Your system connects through the API and webhooks, with test keys that don't touch your balance while you integrate.
How much does it cost?
The monthly plan, from US$39, plus each message at its published price. A delivery notice is a utility template. No per-seat fees.
Tell customers when, before the truck leaves.
Sign up through the site and get a US$5 test credit.