You build appliances that outlive kitchens. Then March arrives and the same four questions arrive with it: which model for eight people, gas or electric, is it rated for indoors, and where is my burner kit. An AI employee takes that whole tier off your team, in French, English and Italian, and hands your people the calls that actually need a human.
None of this work is hard. All of it is relentless, and it lands on the four people who were doing something else.
Enquiries stack up between March and June and again before the holidays, and the people who can answer them are the same people packing orders. Hiring for eight weeks and training for four is not a plan, it is a tax.
Surface size against party size, kW against cooking zones, butane against propane, chrome-plated against enamelled against stainless. The answers never change, and your best product person repeats them fifty times a month.
Gas models need ventilation an indoor kitchen cannot give them, and electrical models need the right supply. Get it wrong on the phone and you have a liability, not a sale.
A burner kit, an ignition module, a drip tray, a replacement grate. Each one is a two-minute conversation and a serial number, and every one of them interrupts somebody who was doing something else.
Registration windows lapse, serial numbers go unrecorded, and the first time you hear about a unit is when it fails. Then the claim arrives with no proof of purchase and a customer who is already annoyed.
The UK, Italy and Spain buy, and the support desk sits in one country speaking one language. Callers who cannot be served in their own language do not leave a voicemail. They buy somebody else's grill.
Three chains it owns end to end, on the systems you already run. Each one ends in a record, not a callback.
Adjudication stays with a person. The agent assembles the claim. It does not approve money and it does not accept liability, because those are not decisions you hand to software. WhatsApp agents for delivery and claim photos carry the picture half of that chain.
Start with one. The one whose calls you can hear from the other side of the office.
Answers the model-selection call end to end: surface size against party size, fuel type, indoor rating, accessories, and either takes the order or books the sales call.
Identifies the unit from a serial number, confirms fitment, checks stock and lead time, and ships the burner kit or the grate without anyone reading a catalogue aloud.
Chases registration in the first thirty days, then takes the claim later: symptom, photos, serial, dealer of record, pre-coded for the back office.
Handles the ventilation, gas conversion, electrical supply and siting questions, and escalates anything that smells like a safety issue to a human immediately rather than guessing.
Works the outbound side before the peak: reactivates last year's enquiries, reminds owners about covers and pre-season servicing, and books the calls that turn into orders. Built on the same engine as Rocket Sales Agent for outbound reactivation.
Direction, not a spreadsheet. We do not publish a percentage we cannot source.
The first ring is answered in the caller's language, at 9pm on a Saturday in May, instead of a callback on Tuesday.
Peak season stops being a hiring decision. The same team covers a heavier month.
Your product experts stop repeating the catalogue and start closing the calls that need judgement.
Warranty registration happens while the customer still has the box, so claims arrive with a serial number instead of an argument.
Export enquiries in French, English and Italian get served by the same agent, from the same knowledge base, without a second support desk.
Every call leaves a record: what was asked, which model, which language, what was promised. Your CRM stops being a guess, and customer risk intelligence has something real to read.
Nothing changes for the customer. They call the same number and it gets picked up.
Twilio, Aircall, Ringover, OVH or the PBX you already pay for. The brand number is where these calls land, so that is where the agent sits. How the voice agents are built.
The default channel for a photo of a cracked burner and for delivery updates across France, Italy and Spain.
Shopify, PrestaShop, WooCommerce, Magento. Live stock, order lookup, and taking the parts order inside the call.
SAP Business One, Odoo, Cegid, Sage. Serial records, stock, lead times and the warranty register. If you run the bigger SAP estate, here is how the SAP integration works.
Zendesk, Gorgias, Freshdesk, Front. Every call becomes a ticket with a transcript attached, so a human picks up mid-context.
HubSpot, Pipedrive, Zoho, Salesforce. Dealer and end-customer records, enquiry history, language preference.
Catalogue PDFs, spec sheets, care guides and an export of the top fifty questions from your support inbox. One source, answered in every language.
Google Calendar or Outlook, for sales callbacks and technician slots. SalesDonna, the sales meeting agent, runs the same diary.
DPD, GLS, Colissimo, UPS. Proactive delivery updates instead of a queue of "where is my order" calls.
These run in your browser and take about a minute each. No signup, and we do not record you.
Try saying "Looking for a plancha BBQ for 6 to 8 people, gas, and easy to clean. What do you have?" and hear the model-selection call end to end.
The plancha product advisor demo →
Serial number in, fitment confirmed, stock checked, order raised. The two-minute call that eats your afternoon.
The spare parts ordering hotline demo →
Serial, fault, purchase date and photos captured on the call, so the claim reaches your team complete on first touch.
The warranty claim intake demo →
One agent, English, French and Italian, switching mid-call when the customer does. This is the one export directors ask to hear twice.
The EN / FR / IT multilingual demo →
Order number in, current stage and a realistic date out, with the promise written down where your team can see it.
The order status and ETA demo →
The long version of the three-language support argument, with the setup we actually use.
Automating support in three languages →
The buyer profile we build this for is public on our blog: a Basque-country manufacturer of premium plancha grills and outdoor cooking equipment, based in Came in south-west France, selling into France, the UK, the US and Italy, with a range that runs from an entry-level plancha to a custom outdoor kitchen, and a support team of one to three people at headquarters who are fluent in French and stretched in Italian. That post frames it as a reference profile, not a scoreboard, so that is how it stays here. No percentages, no savings figure, no call count. All live voice agent demos are on the site if you would rather judge it by ear.
Selling outdoor furniture alongside the grills? That is a different desk with a different calendar, so it has its own page: AI agents for furniture manufacturers. Fitting solar on the roof of the same factory is a third conversation again, covered in AI agents for rooftop solar providers. Running an order and parts desk at scale sits in AI for manufacturers running order and parts desks, and every industry we build AI employees for is listed in one place.
Yes, and that is the point. Volume in March through June is the same four questions at five times the frequency. The agent takes the repeat tier, which is most of it, and the calls that need a product expert reach one faster because the queue in front of them is gone. You staff for your normal month, not your worst week.
It answers what your documentation says. Surface size against party size, kW against cooking zones, butane against propane, which models are rated for indoor use and which need a conversion kit. It works from your catalogue, spec sheets and care guides, so the answer on the phone matches the answer on the box.
It is built not to improvise on that. Ventilation, fuel conversion and electrical supply answers come from your own documentation, and anything outside it, or anything that reads like a safety concern, goes to a named person immediately. Safety questions are an escalation rule, not a confidence score.
It takes the claim and assembles it: model, serial, purchase date, dealer of record, symptom description and photos over WhatsApp, pre-coded against your fault categories. Your back office gets a complete file instead of a voicemail. Adjudication stays with a human, because approving money and accepting liability are not decisions to automate.
One agent, one knowledge base, three languages. The caller's language is detected from the first seconds of speech and the agent stays in it, switching mid-call if the customer asks. You maintain your documentation once, in your primary language, and the agent answers from it in the others. There is a live demo of exactly this on the site.
If the part is in your catalogue, yes. The agent identifies the unit from the serial number or walks the caller through finding it, confirms fitment across the model range, checks stock and lead time in your ERP, and raises the order. Discontinued units are usually the easiest, because the fitment table already exists.
Two weeks from kickoff, which is the standard stated on every demo we publish. Most of that is your content, not our build: the catalogue, the care guides, the warranty terms and an export of your top fifty support questions. Pricing is per minute used, so a quiet February costs what a quiet February should.
Most brands start with parts or pre-sales, because the volume is obvious and the answer already exists in a document. Bring a week of call logs and your top fifty questions, and we will tell you which one pays back first.