AI Chatbot for Repair Shops: A Better Answer to ‘Is It Under Warranty?’

Read the receipt before reading too much into the word warranty

Start with the relationship, not an assumption about coverage. Did the customer buy the device from your business, pay you for a repair, or contact you about a manufacturer's service? A third-party protection plan may introduce another provider. Those enquiries do not all belong in the same queue.

A useful opening is: ‘Is this about a device you bought, or a repair we carried out?’ Adapt it when the message already provides that information. Someone who writes ‘You replaced my screen last week’ should not receive a new-customer questionnaire about buying a phone.

The distinction is not just terminology. Apple's Malaysia sales and support information presents hardware warranties, AppleCare and repair terms separately. Your shop should likewise explain the arrangement that actually applies to its own service, without presenting someone else's terms as yours.

An independent repair business must not imply that it can approve a manufacturer's claim merely because it repairs that brand. Explain your actual role and, where appropriate, the relevant official support route. This article concerns customer communication, not a determination of anyone's warranty rights.

Three replies that leave the customer in very different places

Consider this message: ‘My phone stopped charging. Bought it a few months ago. Still warranty?’ The customer wants to know whether to expect help, a cost or a wasted journey. They may not know which organisation should answer.

‘Yes, bring it in, no charge’ answers a question your team may not yet be able to decide. A recent purchase date does not establish the cause of a fault, the relevant agreement or your authority to provide that service.

‘Charging port replacement starts from...’ goes wrong in another direction. It assumes a diagnosis and sells a repair before addressing the warranty question. The customer has reported a symptom, not authorised a part replacement.

A more useful response is: ‘We can help you find the right next step. Is this about a purchase from us or an earlier repair at our shop? Our team will need to review the relevant record before confirming coverage or charges.’ Then explain your approved process, including any actual assessment fee before the person agrees to it.

The better answer is not evasive. It states what the business can do now and what needs review. Where an approved general policy answers the question, explain it plainly instead of hiding every answer behind ‘visit our shop’.

The customer should not have to become a technician

Ask what they noticed, not what component they think has failed. ‘It only charges when the cable is held at an angle’ is a useful reported observation. ‘Needs a new charging port’ is a technical conclusion that the assistant should not insert into the record.

For a first enquiry, identify the device and the relevant purchase or service reference where available. Ask for additional information only when it helps the next step. Samsung Malaysia's warranty guidance asks customers contacting its service team to have product identifiers, purchase details and a description of the issue ready. That is a manufacturer-specific example, not a requirement to copy every field into your own chat.

If a customer cannot find a receipt, explain how your team can review the situation rather than automatically rejecting the request. Avoid deciding that a missing document ends every possible route to assistance.

Use an appropriate private channel for service documents. Never ask customers to share passwords, one-time codes or banking credentials in the conversation. A public social-media comment is not the place to request a receipt containing personal information.

Keep troubleshooting within your approved safe support boundaries. Do not ask people to dismantle devices or perform risky tests to prove a fault. An enquiry assistant is there to prepare a helpful review, not replace a technician's assessment.

When a previous repair comes back into the conversation

This fictional example describes an invented Malaysian repair-shop enquiry. It is not a Reply.my case study, a coverage decision or a measured result.

Farid messages a shop on Messenger: ‘The laptop you fixed is giving trouble again. Can I claim warranty?’ The earlier job involved a keyboard. His new message does not say what is happening now.

A generic sales reply offers a diagnostic package. Farid reads it as a refusal to stand behind the earlier repair. A generic reassurance promises free work, even though nobody has established whether the concern relates to that job.

The helpful conversation starts differently: acknowledge the previous visit, ask what he is experiencing and help the employee locate the service reference. Farid explains that several keys repeat when pressed. That observation belongs with the earlier job reference for staff to review—not under a new label claiming the keyboard has definitely failed again.

If Farid later contacts another branch on WhatsApp, the employee needs to see that this is a review of earlier work. The branch should not restart the sales pitch or offer a different explanation because the request arrived on another channel.

The outcome remains open until the responsible team checks the device and applicable terms. What has improved is the quality of the conversation: Farid knows his concern has been understood, and the technician knows what needs reviewing.

What belongs in Reply.my—and what stays with your repair team

Reply.my's published scope includes FAQ assistance, customer fields and human handover. For a repair business, an agreed setup can use those capabilities to explain approved service procedures and collect the relevant enquiry context for staff.

Reply.my is omnichannel, not a WhatsApp-only proposition. Your customers may contact you through WhatsApp, Instagram, Messenger or Telegram. Confirm the supported accounts and channels in your proposal. An omnichannel inbox helps address scattered conversations; it does not automatically establish that two profiles belong to the same customer.

Coverage decisions, fault diagnosis, refund approval and permission to carry out chargeable work should remain with the authorised people and processes. Live access to job cards, manufacturer warranty checks or repair-status systems needs separate confirmation. None should be assumed simply because an assistant can discuss your general policy.

A useful human handover separates what the customer reported from what the business has confirmed. ‘Customer asks whether this relates to last month's repair’ is different from ‘warranty repair approved’. That small wording choice can prevent the next employee from treating an assumption as a decision.

For a multi-branch business, also explain which location can review the request. Shared branding does not necessarily mean every counter can access every service record or carry out every repair. Give the customer the correct next step without making them coordinate your branches.

Would clearer first replies change your counter's day?

Look at recent warranty enquiries that reached a technician. How many required staff to undo a promise? How many returning customers were treated as new sales leads? Were customers told about the actual assessment process before making a trip? Those are useful questions even before considering new software.

If the confusion comes from an unclear receipt or service description, improve that too. Automation cannot make inconsistent terms consistent on its own. A low-volume shop may get more value from a clearer explanation and one responsible employee than from adding another subscription.

When the same questions repeatedly interrupt several branches or inboxes, bring Reply.my two anonymised conversations: one new warranty question and one return visit after a repair. Ask which explanations can be handled from approved information, and where your employee would take over. Compare that agreed work with the published plan options, rather than buying a promise of fully automated claims.

The goal is a customer who understands the next step and a technician who receives the real question. A fast answer is valuable only when your team can stand behind what it says.