LINE Official · Real estate

LINE Official Account for real estate: the complete setup guide for Thai property agencies

Every serious Thai property lead starts on LINE. Here's how to wire LINE Official Account into a real CRM so the 11pm message about a Sukhumvit condo doesn't die in someone's personal phone.

Walk into any Bangkok property agency at 7pm. The senior agent has three phones on the desk — one for personal LINE, one for the "team LINE", one for the office number. Messages from prospects ping all three. By the time someone picks up, the prospect has already DM'd two competitors.

This is not a small-agency problem. We've seen 30-agent agencies in Sukhumvit running the same way. Personal LINE accounts forwarded to a "support" group, screenshots flying around, leads attributed by whoever happened to see the ping first. It works — until you measure the response time and realize you're losing the majority of inbound leads within the first 30 minutes.

The fix is not "discipline." It's LINE Official Account with a real webhook into a real CRM. Below is the practical step-by-step, written for someone who has never opened the LINE Developers Console before.

Step 1 — Create the LINE Official Account (15 minutes)

Go to linebiz.com and create an account for your agency. You need:

• A Thai mobile number (or a foreign one if your manager is non-resident).
• The agency name as it will appear to prospects (e.g. "Sukhumvit Property Co.").
• A square 640×640 profile photo — usually your logo on a light background.
• A category — choose "Real Estate / Construction" so LINE indexes you correctly in their directory.

Once approved (usually instant for non-verified accounts, 1-3 days for verified), you have a LINE Official Account with a unique ID like @yourgency. This is what goes on every business card, sign, and ad.

Step 2 — Enable the Messaging API (10 minutes)

In the LINE Official Account Manager, go to Settings → Messaging API → Enable Messaging API. You'll need to create a "Provider" in the LINE Developers Console — this is a one-time admin entity that owns your bots and channels.

After enabling, you'll get two values that your CRM needs:

• Channel Access Token — a long string used by your CRM to send messages out via the LINE Reply / Push API.
• Channel Secret — used to validate that incoming webhook events are actually from LINE (cryptographic signature verification).

Treat both like passwords. Don't paste them in Slack. They go into the CRM admin once and never leave.

Step 3 — Point the webhook at your CRM

The webhook URL is the most important field on the LINE side. It's the URL LINE calls every time someone sends your agency a message, follows the OA, or unfollows. If this URL is broken or slow, you lose leads.

For DevProp customers, the webhook URL looks like https://<your-agency>.devprop.io/api/line/webhook. Paste it in the LINE Developers Console, click Verify, and you should see a green check within 2 seconds.

Common failure mode: agencies set the webhook URL to a Zapier endpoint. This works for proof-of-concept but introduces 5-15 minutes of latency, drops LINE user IDs, and is impossible to debug when LINE rate-limits the Zap. Use a real CRM webhook, not Zapier, for production.

Step 4 — Set the greeting message and auto-reply

The greeting message is the first thing every new LINE follower sees. Make it count: introduce the agency in one sentence, ask one qualifying question, set expectation for response time.

Example greeting (English+Thai bilingual):

The auto-reply (different from greeting) is what LINE sends when no human agent is available. Most agencies leave this on LINE's default ("We'll get back to you soon!") which is the wrong choice — it gives the prospect no information. Replace it with an AI-powered auto-reply via your CRM that actually understands the question.

Step 5 — Connect the AI assistant

This is where a Thai-specialized CRM earns its keep. The AI assistant should be trained on:

• Your current inventory (so it can answer "do you have a 1-bedroom in Asoke under 25k baht/month?").
• Your office hours, response time, and contact policy.
• The Thai zoning and price-range vocabulary your agents use.
• The fallback: when a question is too complex, hand off to a human agent within 30 seconds.

In DevProp, this is one toggle in the admin panel — the AI reads your listing database directly. The first qualified response goes out in under 3 seconds. Industry research consistently shows that response within 5 minutes correlates with significantly higher conversion than slower replies.

Step 6 — Measure what matters

Once the pipe is live, the three metrics that matter:

• Time-to-first-response — measured in seconds, not minutes. Anything above 3 seconds for AI-handled replies is a configuration problem.
• Human-handoff rate — what % of LINE conversations need an agent to step in. Above 40% means the AI is undertrained. Below 10% means the AI is too aggressive and you're losing nuance.
• Lead-to-viewing conversion — of LINE conversations, how many turn into a property viewing within 7 days. This is the real ROI number.

The painful migration question

If your agency currently runs on personal LINE, the move to LINE Official is not technical — it's organizational. Every business card has the old QR. Every Facebook ad points at it. Every sign at every condo lobby has the old @username.

The pragmatic playbook: leave the personal LINE up as a forwarder for 90 days. Auto-reply on personal LINE: "We've moved to our LINE Official Account — scan this QR or tap @newhandle." During those 90 days, swap every external touchpoint to the new OA. By day 91, deactivate the personal forwarder.

It's annoying. It's also the single highest-ROI hour you'll spend in Q3, because every lead that lands on LINE Official lives in the CRM, has a real conversation history, and survives an agent leaving the agency.