AI agents that take reorders from dealers and distributors, log breakdowns on installed equipment and dispatch the technician, and follow up with suppliers and carriers on every open order, in English, Spanish and more than 25 languages in all. They work from the dealer, order, asset and purchase-order record, and finish the task during the call: enter the order, open 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 program, gives order status and the ship date, and reminds them of past-due invoices.
A customer or dealer calls about installed equipment that is down. The agent finds the asset by serial number, checks the service contract or warranty, dispatches the technician and checks the 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 carrier and dock appointment details.
The number is matched to the dealer, customer or supplier: recent orders, open invoices, active programs, installed assets with their service contract or warranty, open tickets and open purchase orders. Consent, calling hours in the contact's local time and do-not-call lists are checked before an outbound dial.
The agent confirms who it is speaking to, takes the order, the breakdown or the delivery date, and enters the sales order, opens the ticket or updates the PO while the caller is on the line.
A line that is down, a credit 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 chemical release 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 shipment.
Outbound calls are placed only inside the hours you set, in the contact's local time, for example 8 am to 9 pm, the window the TCPA rules set for telemarketing calls. The order desk, service line and incident line answer at any hour.
Since the FCC ruled in February 2024 that AI-generated voices are artificial under the TCPA, outbound calls go only to contacts who gave prior express consent, and written consent where the call is telemarketing, such as a program or launch call. For telemarketing calls, the National Do Not Call Registry and your own do-not-call list are checked.
An injury, a fire, a chemical release or an electrical hazard is handed to a person at once, and the caller is told to call 911 if anyone needs emergency help. 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. The agent never asks for a full card number, a bank account number, a Social Security number, a one-time code or a password.
The agent runs in your Google Cloud project, in a US region. Recordings and business data stay in your storage.
The agent quotes only from your price book and active programs. 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 territory manager, service manager 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 your ERP, dealer portal or field service system, is connected through its API during setup. Tilicho builds and maintains it at no extra cost.
More than 25 languages, including English, Spanish, Vietnamese, Mandarin, Tagalog, Korean, Arabic, French and Portuguese. The agent switches language during the call, which matters when a plant technician starts in Spanish and a manager joins in English.
Yes, when the contact has given the consent the TCPA requires for calls with an AI voice, inside the calling hours, and after the do-not-call lists are checked where they apply. The agent says it is an AI assistant at the start of every call.
Yes. The agent reads inventory, prices, programs and open invoices and enters the sales order through your ERP's API, which is connected during setup.
No. The caller is matched to the registered number and confirms a detail such as the account number before the agent reads out anything from the account.
A line-down breakdown goes to your on-call service manager live, with the asset and the history on screen. An injury, a fire, a chemical release or an electrical hazard is handed to a person at once, and the caller is told to call 911 if anyone needs emergency help.
No. The agent connects to your existing numbers and systems. There are more than 50 integrations, and other systems, such as your ERP, dealer portal or field service 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.