AI agents that take reorders from dealers and distributors, log breakdowns on installed equipment and book the technician, and follow up with suppliers and transporters on every open order, in Hindi, English, Hinglish and the Indian languages, more than 25 languages in all. They work from the dealer, order, asset and purchase-order record, and finish the task during the call: book the order, raise the service ticket, update the delivery date. Tilicho builds and runs them inside your own Google Cloud project, starting from accelerators for 25 manufacturing use cases.
The order, the installed equipment and the supply behind it, each with its own agent. All three read and write the same dealer, order, asset and purchase-order record, so one integration supports all three.
Dealers and distributors call to order, or the agent calls them before the season. It takes the reorder, checks stock and the active scheme, gives the order status and dispatch date, and reminds them of overdue invoices.
A customer or dealer calls about installed equipment that has stopped. The agent finds the asset by serial number, checks AMC or warranty, books the technician and checks the spare part and its price.
The agent calls suppliers on open purchase orders. It gets the PO acknowledged, confirms the delivery date, records any delay and its reason, and collects the transporter and vehicle details for gate entry.
The number is matched to the dealer, customer or supplier: last orders, outstanding invoices, active schemes, installed assets with their AMC or warranty, open tickets and open purchase orders. Calling hours and consent are checked before an outbound dial.
The agent confirms who it is speaking to, takes the order, the breakdown or the delivery date, and creates the sales order, raises the ticket or updates the PO while the caller is on the line.
A plant that has stopped, a credit-limit request, a price negotiation, a dispute or any request for a person goes to your team live, with the record and the summary on screen. An injury, a fire or a gas leak is handed to a person at once.
Order, ticket, delivery date, outcome tag, transcript and recording are written to your ERP, CRM and service system. The payment reminder, the technician visit or the next supplier 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 dealer, customer or supplier contact on record before it names an order, an invoice or a PO.
Your company'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 equipment or the delivery.
Outbound calls are placed only inside the hours you set, for example 9 am to 9 pm. The order desk, service line and incident line answer at any hour.
Order, service, payment and PO calls go to dealers, customers and suppliers you already do business with. Promotional calls, such as scheme and launch calls, are checked against TRAI's National Customer Preference Register (DND).
An injury, a fire, a gas leak or an electrical hazard is handed to a person at once. Incidents are routed to your safety team, who decide what is recorded and reported.
PII is masked in transcripts and logs. Access is by role. Consent, retention and access follow the Digital Personal Data Protection Act, 2023. The agent never asks for a card number, OTP or password.
The agent runs in your Google Cloud project, in region. Recordings and business data stay in your storage.
The agent quotes only from your price list and active schemes. Extra discounts and credit-limit changes go to your team.
The agent runs in the Google Cloud region closest to your dealers and plants. This is fixed before the build, since reply time cannot be tuned afterwards.
The agent mirrors the caller turn by turn, so it follows the caller'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 sales officer, service engineer or buyer sees the record, the transcript summary and the captured details before speaking.
An analyzer agent keeps each case open until it reaches an end state: ordered, paid, repaired, delivered, or handed to your team.
Anything not on this list, including SAP, Tally, your dealer management system or service system, is connected through its API during setup. Tilicho builds and maintains it at no extra cost.
More than 25 languages: Hindi, Hinglish and the Indian languages, such as Marathi, Gujarati, Tamil, Telugu, Kannada and Bengali, and for other markets Bahasa Indonesia, Malay, Thai, Vietnamese, Arabic and Spanish among others. The agent switches language during the call, which matters when a dealer starts in Hinglish and moves to Marathi or Tamil.
Yes. The agent reads stock, prices, schemes and outstanding invoices and creates the sales order through your ERP's API. SAP, Tally and other systems are connected during setup.
No. The caller is matched to the registered number and confirms a detail such as the dealer code before the agent reads out anything from the account.
A plant-down breakdown goes to your service manager live, with the asset and the history on screen. An injury, a fire, a gas leak or an electrical hazard is handed to a person at once.
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, and other systems, such as SAP, Tally or your dealer management system, 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 the dealer order desk, the service line or supplier follow-up.