A LINE message arrives at 9:15 AM: “แอร์ไม่เย็นเลย ช่วยด้วย” — “AC not cooling at all, please help.” No address. No brand. No indication of whether this is a residential condo unit or a commercial system in a cold-storage room. No mention of an MA contract. The dispatcher asks for more information. The customer doesn’t respond for two hours. When they do, the only open slot is tomorrow afternoon — but the customer expected same-day.

Neither the customer nor the dispatcher is wrong. The gap between a request arriving and a dispatch-ready job record being created is where most scheduling friction in Thai installation businesses begins. The absence of a structured intake process — one that turns an incomplete request into a complete, actionable brief before a technician is committed — is the root cause.

What Breaks When Intake Has No Structure

When a service request is accepted and passed to dispatch without being qualified, four predictable problems follow.

Wrong priority assignment. Without knowing whether the customer has an active MA contract, the dispatcher treats every request as equal. An MA customer paying 48,000 baht per year for four-hour response windows waits behind a one-time repair customer because nobody checked. The MA customer doesn’t complain once — they quietly don’t renew.

Technicians arrive unprepared. A technician dispatched to an “AC not cooling” job without knowing whether it is a 9,000 BTU bedroom split unit or a 36,000 BTU cassette in a commercial kitchen brings the wrong tools, the wrong parts, and possibly the wrong experience level. The job either ends early with a return visit scheduled or takes twice as long.

Customer expectations go unset. A customer who sent a LINE at 9 AM and hasn’t been given a response window assumes urgency means same-day. When a slot tomorrow afternoon is offered, the conversation has already failed — not because the appointment is wrong, but because nobody set the expectation at the moment of intake.

Double-handling. Information gathered informally is gathered again later. The dispatcher asks, the technician calls to confirm, and the site contact gives a third version. Gathering information once, in structured form, at intake is the only way to avoid this.

What Does a Dispatch-Ready Job Record Need?

A job brief that can be handed to a technician without follow-up questions requires five pieces of information. Every intake process, regardless of channel or tool, should produce all five.

1. Equipment identification. Brand, approximate size or model, and location on site. For aircon: “Daikin 18,000 BTU wall split, master bedroom, second floor.” For CCTV: “16-channel NVR with 4 outdoor cameras, factory floor.” For solar: “5 kW Fronius inverter, roof-mounted array.” Exact models are a bonus; location is not optional.

2. Symptom description. What is the equipment doing or not doing? “Not cooling” and “tripping the breaker every twenty minutes” are different jobs with different parts requirements. Ask for a photo if the symptom is physical — a warning light, an error code, a leak. A photo sent over LINE saves a return visit more reliably than any other single intake step.

3. Contract status. Is this customer on an active MA contract, and if so, what tier? This determines priority level, response window, and whether parts and labor are billable. It should be answerable from your records without asking the customer.

4. Site access. When is the site available, and is there anything that needs to be arranged in advance? A condo that requires a visitor pass registered before noon. A factory that locks out contractors after 4 PM. A shophouse where the owner is only present certain days. Any of these will cancel a correctly staffed job if the technician arrives to a locked door.

5. Preferred contact method. Does the customer want updates on LINE, by phone call, or through a contact form? When a technician is running 45 minutes late, knowing how to reach the customer is the difference between a managed expectation and an angry call to the main line.

How Should You Classify Incoming Service Requests?

Once a request is qualified, it needs a priority level before dispatch. A four-tier system works for most Thai installation businesses:

Emergency — equipment completely down with a safety or financial impact: a cold-storage system failing, an active water leak into a ceiling, a fire panel alarm. MA customers with emergency SLA coverage. Response target: same day, within the committed window.

Urgent — equipment significantly degraded, customer is commercial or a priority account, business impact is real but not a safety issue. A restaurant’s dining-room aircon failing at noon. A CCTV system with no recording capability at a site handling cash. Response target: within 24 hours on a working day.

Routine repair — partial fault, residential, no MA contract, customer flexible on timing. “My bedroom unit is working but making a noise.” “The camera in the corner of the car park is offline.” Response target: within 3–5 working days, slotted into a planned schedule.

Scheduled PM — a maintenance visit that was pre-booked. These have a committed date, not an urgency level. The intake function is confirmation: verify access, scope, and site contact 24–48 hours before the visit.

What Channel Is Best for Service Request Intake?

Most Thai installation businesses receive requests through three channels: LINE, phone, and in some cases a web form or email. Each has real tradeoffs.

LINE is fast and preferred by Thai customers. The structural problem is that LINE conversations have no fields — a request arrives as free text or voice, and extracting the five intake pieces requires follow-up messages that stretch over hours. The practical fix is a LINE auto-reply that includes a short intake form link: customers who are ready to give information can do so immediately, and those who send a message without context get a clear prompt to complete one.

Phone works well when the problem is genuinely hard to describe in writing. The discipline required is immediate entry: whoever takes the call logs the five pieces into the job record before hanging up. A phone intake without a record is no intake.

Form intake is the most structured option and works well for new customers. For existing customers who have always called or messaged, a form requires explicit promotion: link in your LINE bio, in every invoice signature, and in the service report handed over at job close.

Why MA Customers Demand a Separate Intake Path

An MA customer who is not identified as such at intake is an MA customer who is not receiving the service they paid for. This is not a minor administrative inconvenience — it is a direct failure to deliver the product.

The fix is a checklist step that verifies contract status before any priority decision is made. In a job management system, this means contract records linked to customer profiles — MA status and tier visible immediately when a known customer submits a request. Without a system, a customer list with expiry dates and priority tier, checked at intake, prevents the most common MA delivery failures.

When an MA customer is identified at intake, two things should happen before dispatch: start their SLA window, and send an acknowledgement — a LINE message or callback confirming receipt and expected response time. This closes the expectation loop before it opens as a complaint.

FAQ

What if a customer doesn’t know the equipment details at intake?

Ask for a photo of the unit’s nameplate or the outdoor unit label. Most customers can send one from their phone in under two minutes. If the site is accessible to the technician anyway, document the model on first arrival and update the customer record — but do not dispatch without at least a symptom description and location.

How long should the intake process take?

For a standard repair request with a cooperative customer, a structured intake should take 90 seconds to three minutes of active exchange — assuming the customer is responsive. If the required information cannot be gathered within the first exchange, flag the job as incomplete and set a follow-up reminder rather than carrying the request in informal memory.

Should one person handle all intake, or can anyone on the team take requests?

A single intake owner — the dispatcher or office coordinator — produces more consistent results than ad hoc intake by whoever answers first. Multiple handlers means different questions each time, inconsistent prioritization, and information scattered across conversations. If team size requires shared intake, a shared standard — same questions, same form, same record structure — matters more than who does the asking.

A service request that arrives incomplete and exits intake dispatch-ready is a job that runs better from the first minute. OnSiteQ’s dispatch board gives your team a single place to receive, qualify, and assign incoming requests — so intake discipline becomes part of normal operations rather than a conversation you have to remember to have.

Service Request Intake: Triage Jobs Before Dispatch