Last updated: August 29, 2026
If you want to create a survey in a LINE Official Account, choose the collection route before writing every question. LINE Official Account Research, CRM Forms, and an external form can all support a useful survey, but they differ in how answers, tags, branching, exports, and follow-up work.
This guide covers the complete operating decision: distribute a survey through a message or rich menu, collect and test answers, branch questions when necessary, aggregate the result, and decide whether a reminder is appropriate. For general question design, use the survey design guide. For the broader FORMLOVA workflow, start with the FORMLOVA form creation guide.
The short answer: choose the route from the action after the answer
“A LINE survey” can mean several different products. Decide what you want to do the day after the answers arrive.
| Route | Best fit | Answer and analysis model | Main caution |
|---|---|---|---|
| LINE Official Account Research | Run a short survey inside the official-account experience | Review results in the official manager and download an Excel result when eligible | Check the current download conditions and limits |
| CRM Form | Connect answers to customer information and tags | Review results and answer history, then use tags for customer segmentation | Published or scheduled forms have editing restrictions |
| External form | Keep the question, identity, branching, and export model flexible | Use the form service as the response system of record | The respondent leaves the LINE conversation for a web page |
| FORMLOVA | Combine LINE distribution with form operations and post-response work | Search, classify, report, and follow up from form-owned response data | LINE integration records supported link activity; it is not universal LINE tracking |
Official Account Research is a sensible choice when the survey can stay close to LINE and the official manager is enough for review. CRM Forms are a better fit when a CRM option is already in use and answers should update customer information or tags. An external form is easier to standardize across LINE, email, a website, and other channels.
FORMLOVA is useful when the survey is one part of a larger operation: a form response may lead to a support task, an application, a payment, a report, or a carefully reviewed follow-up. It is not a promise to replace LINE’s CRM, to recover every message read, or to prove delivery.
Step 1: Choose the survey route and the system of record
Write down the decision the team will make after the survey. If you only need a quick satisfaction pattern, Research may be enough. If a selected answer should apply a customer tag for a later LINE audience, CRM Forms may fit. If the same questions must be available from a website and an email, an external form gives you a clearer common record.
Use Official Account Research when these statements are true:
The survey can stay inside the LINE Official Account experience.
The questions are short and the official result view is sufficient.
The answers do not need to be merged with another response database.
The official Research manual states that results can be downloaded in Excel format, but it also lists eligibility conditions. As of the manual checked on August 29, 2026, at least 20 answers are required before a result download is available, and the downloadable result is limited to 50,000 rows. These details can change, so verify the current manual before promising a report to a stakeholder.
Choose CRM Forms when answer-driven customer updates matter. The official CRM Form manual describes customer-information updates and tag assignment from answers. It also says that questions and the answer period cannot be edited after a form is published or scheduled. If your team expects to change the questions while the survey is running, settle the versioning plan before publishing or copy the form for a new version.
Choose an external form when you need any of the following:
- a common survey URL for LINE, email, and your website;
- optional contact details after an answer that requests follow-up;
- a custom branching model or completion page;
- a response export that matches your internal columns;
- a form response that should join an inquiry, application, or payment workflow.
The key question is not “Which tool has the most features?” It is “Which system owns the answer and the next action?” Decide that before the distribution copy is written.
Step 2: Design short questions and explicit branches
A survey opened from LINE is usually answered on a phone. Start with a measurable choice, ask for the reason only where it matters, and make long text optional unless the answer is impossible to act on without it.
For a survey about a new announcement, a practical structure is:
Q1. How clear was the announcement? (Single choice, required)
Q2. Which part was most useful? (Multiple choice, optional)
Q3. What was unclear? (Open text, optional)
Q4. Would you like a personal follow-up? (Single choice, optional)
Q5. If yes, where should we contact you? (Optional contact field)
Q1 creates the overall signal. Q2 gives you a comparable category. Q3 explains the negative or unusual answers. Q4 and Q5 separate the desire for contact from the survey itself. This keeps the main path short while still supporting a useful follow-up branch.
Before building the form, make a branch table:
| Trigger answer | Next view | Data action | Test case |
|---|---|---|---|
| Clear | Skip the explanation field | Keep the answer in the main result | Choose “Clear” |
| Unclear | Show the optional explanation | Add the text to the improvement review | Choose “Unclear” and write one sentence |
| Follow-up requested | Show the contact field | Route the request to a named owner | Choose “Yes” and submit a dummy address |
| No follow-up | End without contact details | Keep the response in aggregate analysis | Choose “No” and submit |
The branch is useful only when each path has a next action. A question that changes the screen but changes nothing in the operation adds friction without adding insight.
LINE CRM Forms can use selected answers for tag settings and later customer segmentation. A tag is not proof that a message was read, that a person is still a friend, or that a later application was completed. Keep these as separate events in your measurement plan.
If the native LINE option does not support the required branch, use an external form with an explicit test plan. FORMLOVA supports conditional field visibility, page skipping, and form completion based on response conditions. The survey form guide covers the broader setup and aggregation model, while the internal survey guide covers anonymity and response-rate risks for employee surveys.
Step 3: Distribute the survey and test the real respondent path
Use a message, rich menu, or another LINE entry point that your account already operates. The official rich-menu manual describes links to external websites and booking pages, so a survey URL can be treated as one destination in the menu. You do not need to rebuild every button to add one survey route.
The invitation should state the reason, approximate effort, deadline, and what will happen to the result:
We are improving the next update and would value your feedback.
The survey takes about three minutes and is mostly multiple choice.
Open-ended comments are optional.
Please respond by September 2.
Survey link: https://formlova.com/...
Do not assume that a link click equals a completed response. Keep these events separate:
Message sent
Link opened
Survey started
Survey submitted
Follow-up requested
Next action completed
Before sending to a broad audience, use a phone and follow every route. Confirm the message, the rich-menu action, the first question, the branch, the completion screen, the stored answer, and the deadline behavior. The official manual notes that rich menus are not displayed in the PC or Chrome versions of LINE, so a desktop check is not a substitute for a phone check.
For CRM Forms, verify whether the respondent must use LINE and whether non-friends or blocked users can answer under the current account behavior. The current official manual says that LINE use is required for an answer, while users who have not added the account or have blocked it can still answer. That distinction affects both audience planning and the language of the invitation.
For FORMLOVA, ask in chat for the survey purpose, audience, questions, required fields, completion message, and branch conditions. The draft should remain unpublished while you inspect the preview. Confirm access mode, duplicate-response prevention, privacy requirements, notification recipients, and every branch before publishing.
FORMLOVA’s LINE integration is intentionally narrower than an all-purpose LINE analytics product. A FORMLOVA-issued LIFF link can record a supported tap and connect it to FORMLOVA-owned form activity. It does not retroactively recover clicks on existing buttons, identify every person who ignored a message, or report individual read status. If you have an existing LINE automation tool, preserve its webhook and change only the link surface that you have explicitly approved.
Step 4: Aggregate the result and plan a measured reminder
Start analysis with completion, not with the most interesting comment. Use a repeatable order:
1. Compare started and completed responses.
2. Review the distribution of each fixed-choice question.
3. Compare the branches and their drop-off.
4. Read optional comments next to their trigger answer.
5. Separate follow-up requests from the aggregate result.
6. Select no more than three changes for the next release.
Research results are reviewed in the official manager and can be downloaded in Excel when the current conditions are met. CRM Form results are available in the form result view and the user’s answer history. The CRM Form manual checked for this guide says result aggregation runs once per day rather than appearing in real time. Record the aggregation timestamp whenever a deadline decision depends on the result.
For an external form or FORMLOVA, name the system of record and the export moment. A CSV or spreadsheet is an output, not a decision. Keep the question version, distribution window, answer window, branch, and exclusion rules with the report so the next survey can be compared honestly.
A reminder should be a controlled follow-up, not a repeated broadcast. First determine which people can be identified as eligible nonrespondents. If the survey is anonymous, a person-level reminder may contradict the promise made to respondents. In that case, send one general reminder or close the survey without individual targeting.
If the account can use a LINE audience or a response-linked customer segment, inspect the estimated audience, the message quota, and the exact exclusion rule before sending. The official message-delivery manual treats audience size and actual delivery as separate operational concerns. Do not write “everyone received it” unless the provider gives evidence that supports that statement.
FORMLOVA can draft a segment-based LINE send from stored tap or form activity. Sending requires the dashboard approval surface, a target snapshot, a test send, and approval. The integration uses push or multicast to stored user IDs; it does not use a broadcast shortcut. The LINE Login channel and Messaging API channel must be under the same provider for the user ID relationship to hold, and the connection should be verified with a test user before the first real send.
For a response-centered follow-up, the survey follow-up Workflow can organize score and open-text outcomes into the next task. For recurring theme review, use the open-text theme report Workflow. These workflows operate after the answer is available; they do not turn an untracked LINE message into a response.
LINE Official Account or FORMLOVA?
Use the data relationship as the deciding factor:
| Need | Primary place | Why |
|---|---|---|
| A short LINE-native pulse check | Official Account Research | Distribution and result review stay close to the account |
| Answer-driven customer tags and customer operations | CRM Forms | Answers can feed customer information and tag-based audiences |
| The same survey across multiple channels | External form | One question and export model can serve LINE, email, and web |
| A response that must lead to tickets, applications, payments, or reports | FORMLOVA | Form-owned data can be searched, classified, and routed into follow-up |
There is no need to force one system to own every part. LINE may be the distribution channel, while the form service owns the answer. Or the official account may own both the survey and the customer tag. Make that boundary visible to the team so that “sent,” “opened,” “answered,” and “followed up” are not combined into one misleading conversion rate.
FORMLOVA does not replace a LINE Official Account, LINE CRM, or an existing LINE marketing platform. Its LINE layer records the supported reaction to an approved link and connects that activity to form-owned outcomes. The value is in making the next action explicit without claiming access to events the link or API does not expose.
Frequently asked questions
Can I create a survey only with a LINE Official Account?
Yes, when the account has access to the relevant Research or CRM Form feature. Use Research for a short LINE-native survey and CRM Forms when answer-driven customer information or tags matter. Confirm the current account, contract, answer, export, and editing conditions in the official manual before launch.
Can a LINE survey show different questions based on an answer?
It depends on the route and the question types it supports. Define the trigger, next view, data action, and test case first. If the native route cannot express the branch, choose a CRM Form or external form that can, and test both the positive and negative path on a phone. FORMLOVA supports conditional fields, page skips, and completion conditions in its form model.
Are CRM Form results real time?
Do not assume so. The current CRM Form manual says that result aggregation runs once per day. Record the aggregation timestamp and describe the result as a snapshot when making a deadline decision.
Can I remind only people who have not answered?
Only when the audience and the response can be linked under the promise made to respondents. An anonymous survey should not silently become a person-level tracking exercise. Even with a response-linked integration, a link tap is not the same as a submitted answer, and an untracked non-clicker cannot be inferred safely.
Is a survey distributed through LINE anonymous?
The channel does not decide anonymity. Questions, contact fields, customer tags, timestamps, access permissions, and the provider’s technical records all affect the promise. Explain what is collected, who can view it, how results are aggregated, and whether a voluntary follow-up channel is separate from the answer.
Should I use an external form for open-ended answers?
Use the route that gives you enough open-text control without creating unnecessary respondent effort. Keep open-ended questions focused and optional where possible. If you need a comparison of LINE’s survey routes for open-ended collection, the Japanese LINE open-ended survey guide covers that narrower Japan-specific intent.
Summary: separate the LINE touchpoint from the answer operation
Creating a survey in a LINE Official Account starts with a route decision, not a question list.
Research fits a short LINE-native check. CRM Forms fit answer-driven customer information and tags. An external form fits a shared question and export model across LINE, email, and web. FORMLOVA fits when the form response must become a searchable, reviewable, and approved next action.
Before distribution, test the message, link, first question, branch, completion, aggregation, and deadline on a real phone. Keep sent, opened, started, submitted, and followed-up as separate events. That separation is what makes the next improvement visible.
Once the questions and post-response action are clear, start a FORMLOVA survey draft and build the smallest version you can review end to end.
Disclosure and Verification
This guide is for teams deciding how to operate a survey from a LINE Official Account. I work on FORMLOVA, so the FORMLOVA examples describe the implemented form and LINE integration boundary. I reviewed the official LINE or LY Corporation manuals for Research, CRM Forms, rich menus, and message delivery on August 29, 2026, along with the relevant FORMLOVA specification. Provider screens, account eligibility, and limits can change; verify them before a live distribution. This is operational guidance, not legal advice.
