AI agents that confirm cash-on-delivery orders before dispatch, call customers when a delivery fails, answer your helpline about orders and bookings, and call travellers when a booking needs attention, in more than 25 languages. They work from the order or the booking and finish the task during the call: correct the address, book the pickup, rebook the trip, send the payment link. Tilicho builds and runs them inside your own Google Cloud project, starting from accelerators for 25 e-commerce and travel use cases.
Orders, the helpline and travel bookings, each with its own agent. All three read and write the same customer, order and booking record, so one integration supports all three.
The agent confirms cash-on-delivery orders before dispatch and calls the customer when a delivery fails. It corrects the address or books a new date, so fewer parcels go back to origin.
The customer calls about an order or a booking. The agent finds it from the caller's number and answers on status, returns, refunds or changes, at any hour.
The agent confirms bookings, calls before a held booking expires or a document is missing, and calls when a schedule changes with the rebooking options.
The number is matched to the customer's orders and bookings: items, payment mode, courier status, travel dates and open tickets. Calling hours and consent are checked before an outbound dial.
The agent confirms the order or the booking, takes the change the customer asks for, and corrects the address, books the pickup, rebooks the trip or sends the payment link while the customer is on the line.
A fraud concern, a refund dispute, a traveller stuck at an airport or station, or any request for a person goes to your team live, with the order or booking, the history and the summary on screen.
Status, outcome tag, transcript and recording are written to your order or booking system and CRM. The courier update, the payment follow-up or the review call is scheduled.
Each agent starts from an accelerator, so a use case is on live calls in about one month.
The opening is fixed in the script. It is the same on every call, in every language.
On an outbound call the agent confirms it is speaking to the customer who placed the order, or the lead traveller, before it names the order or the trip.
Your brand's name and the purpose of the call, in the words your team approved.
The agent says it is an AI assistant and that the call is recorded.
Only then does the script move to the order, the delivery or the booking.
Offer calls, such as cart recovery and repeat-purchase offers, are placed only inside the hours you set, for example 9 am to 9 pm. The helpline answers at any hour.
Promotional calls go only to customers who have consented, and numbers on TRAI's National Customer Preference Register (DND) are checked first.
The agent never takes a card number, OTP or UPI PIN on the call. It sends a secure payment link from your payment gateway.
PII is masked in transcripts and logs. Access is by role. Consent and retention are set up for the Digital Personal Data Protection Act, 2023.
The agent runs in your Google Cloud project, in region. Recordings and customer data stay in your storage.
The agent changes an address, an order or a booking only for the confirmed customer, and reads the change back before it is saved.
The agent runs in the Google Cloud region closest to your customers. This is fixed before the build, since reply time cannot be tuned afterwards.
The agent mirrors the customer turn by turn, so it follows the customer's language and not a setting.
A supervisor routes to small agents that share the state of the call. The script grows by adding agents.
A health-checked fallback model in the same region takes over mid-call, with the state of the call intact.
Your team member sees the order or booking, the history, the transcript summary and the captured details before speaking.
An analyzer agent keeps each order or booking open until it reaches an end state: confirmed, delivered, rebooked, refunded, or handed to your team.
Anything not on this list, including your shipping platform, courier partners or booking engine, is connected through its API during setup. Tilicho builds and maintains it at no extra cost.
Online retailers and D2C brands, marketplaces, quick commerce, online travel agencies, airlines, hotel groups, tour and holiday operators, and bus and rail booking platforms.
More than 25 languages: Hindi, Hinglish and the Indian languages, and for other markets Bahasa Indonesia, Malay, Thai, Vietnamese, Filipino, Arabic, Spanish, French, German and Portuguese among others. The agent switches language during the call when the customer does.
The agent confirms each COD order and its address before dispatch, so orders the customer did not mean to place are cancelled before they ship. When a delivery fails, it calls the same day and books a new date or a corrected address, so the parcel is attempted again instead of going back.
No. It never asks for a card number, OTP or UPI PIN. It sends a payment link from your payment gateway on WhatsApp or SMS, and confirms on the call when the payment lands.
The call is transferred live to your team with the order or booking, the history and the summary, so the customer does not repeat the case. You decide which cases always go to a person, such as fraud concerns, refund disputes and travellers stuck at an airport.
In your own Google Cloud project and your storage. Tilicho runs the agent inside that project.
No. The agent connects to your existing numbers and systems. There are more than 50 integrations, including Shopify, and other systems, such as your shipping platform or booking engine, are connected through their APIs during setup.
A 30-minute session: a live call with the agent, then a walk through one use case of yours, such as COD confirmation, failed-delivery calls or a flight schedule change.