Every Thai customer has LINE. Almost every customer has at some point sent the same message: “ช่างมาถึงไหมแล้วครับ?” — “Is the technician there yet?” — sometimes to a business that already dispatched someone thirty minutes ago but never told anyone.

For installation and maintenance businesses in Thailand, customer communication during a service job is one of the most overlooked parts of the operation. The actual work gets done, the technician is competent, the job closes fine — but because the customer was never told what was happening, the experience feels uncertain. That uncertainty produces phone calls to your office, frustrated messages to your sales contact, and the quiet feeling that the business is hard to deal with.

The fix is not more staff to field calls. It is automated LINE notifications triggered by real events in your job workflow — dispatched, on the way, checked in, job done. Each message is short, specific, and arrives exactly when the customer needs it.

What Do Customers Actually Want to Know During a Service Job?

Most customers are not asking for detailed technical updates. They have four questions, and they want the answers without having to ask:

Is the appointment confirmed? After they submit a request or you call to schedule, they want confirmation in writing — date, time window, and what will be done.
Who is coming, and when will they arrive? A technician name and a realistic arrival time means they do not have to sit waiting with no reference point.
Has the technician arrived and started? Especially useful for customers who are not on-site themselves — property managers overseeing a unit, office managers with technicians working after hours.
Is the job finished, and what was done? A brief job summary — what was inspected, what was repaired, what parts were used — gives the customer something to file and removes ambiguity about what happened.

These four questions map directly to four moments in your job workflow. If you send a message at each moment, the customer experience becomes smooth without anyone on your team spending time on status calls.

When Should Each Notification Go Out?

The value of automation is that timing is consistent and requires no one to remember.

At job confirmation — When the appointment is booked and a date and time window are locked, a short message goes to the customer: job type, date, time window, and a contact number for rescheduling.

At technician dispatch — When you assign a technician and they accept the job, send the technician’s name and approximate arrival window. For residential customers this stops them going out. For commercial customers it lets the site coordinator prepare.

At check-in — When the technician checks in on the mobile app, a brief arrival notification fires. Especially useful when the customer is in a different part of the building.

At job close — When the technician submits the report and checks out, the most substantial message goes out: job complete, a brief summary of what was done, and a link to the service report or photos if available. For MA customers, include the next scheduled visit date.

What Should Each LINE Message Contain?

Short messages outperform long ones in LINE. Customers are confirming an event, not reading a report. A reliable format:

Job reference number — so multi-unit customers or property managers can track which site or which unit this relates to
Technician name — personalizes the message and gives the customer someone to ask for if needed
What happened — one sentence: “ช่างเริ่มงานแล้ว” or “งานเสร็จสมบูรณ์ ล้างแผงคอยล์, เติมน้ำยา R32 0.5 กก.”
Time stamp — LINE includes this automatically, but the message body should reference the event (“12:47 เริ่มงาน”) if the timing matters
Next step or contact info — “หากมีคำถาม ติดต่อ [เบอร์]” or “นัดครั้งต่อไป: 4 ธ.ค.”

Resist the temptation to put everything in one message. A long message reads like marketing. A short, accurate message reads like operational competence.

What Happens When You Rely on Manual LINE Messages?

Most Thai installation businesses start with a manual process: someone in the office sends a LINE message when they remember, or the technician sends one from their personal account before setting off.

The failure modes are consistent:

Inconsistency — Different technicians send different information, or nothing at all. Customers who use your business regularly notice and adjust their expectations downward.

Timing gaps — A technician dispatched at 9am may not think to send a LINE until 9:40. The customer who expected the technician at 9:30 has already called the office.

No record — When a customer later disputes whether they were notified, a message from a personal account on a technician’s LINE is not easy to retrieve or verify. A system-generated message is a timestamped record tied to the job.

Staff time absorbed by status calls — For a business running fifteen jobs per day, incoming status calls from customers typically consume one to two hours of office staff time. That is time spent on information that should have been delivered automatically.

A Worked Example: Aircon Service Company, Bangkok

A residential aircon service company with five technicians handles twelve to fifteen jobs per day. Before automating customer notifications, the front desk received around eight status-check calls per workday — customers asking when the technician was coming, or whether the job was finished.

After linking job events to LINE notifications, those calls dropped to two or three: genuine exceptions where something changed or a customer wanted to add scope. The staff time freed up goes into following up on open quotes and MA renewal windows instead.

The technicians’ workload did not change. The jobs did not change. Only the communication step changed — and it is now handled by the system when the technician updates their job status.

Does Automation Replace the Personal Touch?

For field service businesses where relationships matter — and in Thailand, they do — this is a reasonable concern. Automated notifications handle the operational layer: timing, confirmation, status. The personal layer is where your technician greets the customer, handles their concern on-site, and follows up if something unusual happened.

An automated “งานเสร็จสมบูรณ์” does not replace a technician who notices a second unit running noisily and flags it before leaving. The notification handles the expected; the technician handles the unexpected.

The businesses that struggle with this are ones that mistake silence for professionalism. Sending a customer nothing because “we don’t want to bother them” is not professional restraint — it is a gap that the customer fills by calling your office.

Connecting Notifications to Your Job Workflow

Automated notifications only work consistently if they are triggered by actual job status changes — not by a manual step someone might skip. When a technician updates their job in the mobile app (dispatched → en route → checked in → job closed), the notification system fires based on that status change. No one has to remember to send the message.

This is why notifications live inside the work order system rather than a separate messaging task. The technician’s field actions trigger customer-facing messages automatically. Businesses that send LINE manually — from a spreadsheet or by memory — cannot sustain consistency when jobs stack up.

For MA customers, notifications also serve as proof of delivery: when a PM visit closes and the customer gets a job-complete message, the service record is visible to them at the moment it is created — not as a quarterly report they have to chase.

FAQ

What if our customer doesn’t use LINE?

LINE reaches over 90% of Thai smartphone users, making it the default for Thai B2C communication. For corporate customers — particularly international companies — SMS or email may be preferred. A flexible system should support both. For most Thai residential and SME customers, LINE is sufficient.

Should notifications be in Thai or English?

Match the customer’s language. Thai for residential customers; English for international property managers or expat homeowners. If unsure, Thai is the safer default — a bilingual customer will not mind, and a Thai-only reader will.

What if the technician arrives outside the promised window?

Send an updated notification as soon as the delay is known — not after the technician is already late. A proactive message, even with bad news, lands better than silence followed by waiting.

Customer communication during a service job is not an add-on to good field service — it is part of the service itself. In a market where LINE is universal and customers have learned to expect instant messaging, a business that sends nothing between booking and completion is creating an experience gap that competitors who do communicate will fill.

If you are building out your field service operations and want to see how automated notifications connect to job dispatch and work orders, take a look at what OnSiteQ is designing for Thai install and maintenance businesses.

Automated LINE Updates for Field Service Customers