What does a LINE developer actually build?
Setting up a LINE Official Account is not development. Here is what a LINE developer actually builds for a business, and what to ask before you hire one.
Key takeaways
- Rich menus and chat flows are the visible layer of a LINE Official Account. Much of this is configuration, not code.
- The Messaging API connects your OA to your own server, so bookings, orders and reminders can be automated.
- LIFF apps and MINI Apps put real web tools, such as booking forms and member cards, inside the LINE chat.
- Integrations with your CRM, POS, ERP or payment system are where most of the value, and most of the effort, sits.
When a Thai business says “we need someone to do our LINE”, it can mean anything from designing a rich menu to building a booking platform. That gap causes most of the disappointment: owners pay for development and receive account setup, or expect automation and receive a nicely designed menu.
This article explains what a LINE developer actually builds, what does not count as development, and what to ask before you hire one.
What is LINE development, and what is not
Setting up a LINE Official Account in the LINE Official Account Manager is not development. Creating the account, uploading a profile image, writing a greeting message, adding keyword auto-replies and designing a rich menu are useful jobs, and many businesses can do them alone or with a marketing agency.
LINE development begins when your own software becomes involved. That means code running on a server, web pages opened inside LINE, or data moving between LINE and your other systems. If nothing in your plan touches a server or a database, you probably do not need a developer yet. If you want to send a confirmation after a booking, look up an order, or recognise a returning customer, you do.
Rich menus and chat flows
The rich menu is the grid of buttons at the bottom of the chat. On the design side it is an image with tappable areas. On the development side it is what each button does: open a link, send a message, or open a web app.
A chat flow is the sequence of messages a customer goes through, for example “choose a service, choose a branch, choose a time”. Simple flows can be built with the manager’s own tools. Flows that depend on live data, such as which time slots are really free, need code behind them. Good flows are short, give buttons instead of asking people to type, and always offer a way to reach a human.
Messaging API: webhooks, replies, push and broadcasts
The Messaging API is how your server talks to your LINE Official Account. It has two directions.
Incoming: webhooks. When a customer sends a message, follows your account or taps a button, LINE sends a small event to an address on your server called a webhook. Your software reads the event and decides what to do. We go through this step by step, including security, in connecting LINE to your CRM.
Outgoing: three kinds of message.
- Reply messages answer an event that just arrived. They are tied to that event and must be sent soon after it.
- Push messages are sent by your system at any time to a specific person, such as a reminder the day before an appointment.
- Broadcasts go to all or a segment of followers, such as a promotion.
The type matters for your cost, because LINE’s message quotas and pricing depend on how you send. Check the current LINE pricing page rather than relying on an article, including this one.
LIFF apps: forms, member cards and catalogues
LIFF lets a web page open inside LINE and, with the customer’s permission, read their LINE profile. The customer does not need to type a name or create an account.
Typical LIFF builds are booking forms, digital member cards with points, product catalogues, registration forms and order-status pages. They are ordinary web development with LINE login added, so a developer who knows web apps can learn LIFF quickly. The harder skill is designing for a phone screen inside a chat, where patience is short. The difference between the options is covered in LINE OA, LIFF or MINI App.
LINE MINI Apps
A MINI App is a fuller service built on the same web technology and reviewed by LINE. It suits a business where LINE is the main place customers order, book or manage a membership, not only a way to reach them. The extra work is the review process and meeting LINE’s requirements, so ask a developer whether they have taken one through review, and check the current LINE documentation on LINE Developers before planning.
Integrations: CRM, POS, ERP and payments
This is where the largest share of effort goes, and where the value is. A chat window with no link to your business data can only answer generic questions. Connected to your systems it can:
- create or update the customer record in your CRM when someone books;
- check stock in your POS or ERP before confirming an order;
- send a payment link or QR code and mark the order paid when it clears;
- trigger a follow-up message when a treatment, service or subscription is due.
Each integration needs a decision about who owns the data, how duplicates are avoided and what happens when one system is down. Our own booking and CRM platform, FoxConnect, is an example of this kind of build: customers book and get reminders inside LINE while the business manages calendars and customer profiles behind the scenes.
What to ask before you hire a LINE developer
Use this checklist in your first meeting.
- Which parts will be coded, and which are configuration? A clear answer separates development from setup.
- Who owns the LINE channel, the code and the data? You should own the channel and your customer data. Ask what happens if you change supplier.
- How do you verify webhook requests and handle failures? If the answer is vague, security is probably vague too.
- How will customers be matched to our CRM, and how is consent handled? A good developer raises PDPA unprompted.
- Have you built something similar that is live? Ask to see it, or to hear how it behaves in production.
- What do we pay LINE separately? Messaging fees and quotas are paid to LINE and are separate from development.
- What does a staged delivery look like? Look for a small first release that you can use before the whole project is done.
- Who maintains it? LINE changes its platform from time to time, so ask who updates the system and how that is agreed.
Cost is the question everyone wants answered first. We explain what drives it in what a custom business app costs in Thailand.
Next step: define the first useful release
Before you contact any developer, write down the one customer journey you most want to improve, such as booking, reordering or asking about delivery, and which systems it touches. That single page is a better brief than a feature list.
If you would like a second opinion on it, our LINE development team in Bangkok can review your plan and tell you honestly which parts need code and which do not. You can reach us through the contact form.
Frequently asked questions
Do I need a LINE developer if I only want a rich menu and auto-replies?
Usually not. Rich menus, greeting messages and keyword auto-replies can be set up in the LINE Official Account Manager by someone on your team. You need a developer when LINE has to talk to your own systems.
What is the difference between a LINE developer and a LINE OA agency?
An OA agency typically handles account setup, content, broadcasts and rich-menu design. A LINE developer writes software: a server that receives LINE events, web apps that run inside LINE, and integrations with your business systems. Some teams do both, so ask which part of the work is actually coded.
How long does a LINE integration take?
It depends on the scope, so be wary of a fixed answer before anyone has seen your systems. A simple chatbot or booking form is a small project. Syncing with an ERP or POS, with custom rules, is larger. A good developer will split the work into stages and tell you what each one delivers.