LINE
What a Woodstock agent could do inside a LINE group — answer from your knowledge, send reminders, keep the files people share — and what LINE won't allow. Explored in a prototype; not in Woodstock yet.
Thai teams already talk in LINE groups. The idea: invite a Woodstock agent into the group, so people can ask it things, get reminders from it, and have what they share kept — without leaving LINE.
The idea in one picture
A LINE group is a window onto one Woodstock channel. What people say and share in the group lands in the channel; what the agent says in the channel goes back to the group.
What it can do
Answer from your knowledge Tried
Start a message with ws (or mention the bot). The answer comes back as a card, with the page it came from and
a few follow-up questions to tap. About 6–28 seconds; Thai stays Thai.
Four answer cards Tried
The agent picks the card that fits the question. Plain text is there too, for people who prefer a normal message.
On a real phone — the prototype's sample cards in LINE on iPhone:
What the real thing shows: cards take most of the screen width, titles are dark grey rather than black, link buttons are a muted blue, and long words wrap mid-word. The bot shows LINE's blank avatar until it is given a profile picture.
Cards with pictures Tried
Cards can carry photos in four ways, all seen working in LINE on iPhone. A photo has to sit at a public link that never expires, because LINE's apps load it directly (limits). The prototype used stock photos.
| Style | Best for | Watch out for |
|---|---|---|
| Big image | One thing where the picture matters: a product, a receipt, a site photo | Tall on screen; one per answer |
| Thumbnails | A list of results people recognise by sight | Keep to 3–5 rows |
| Swipe cards | Several items to browse, each with its own button | Only the first is fully visible |
| Gallery | Pictures only, one label each | Labels are 12 characters at most (per LINE's docs) |
More ways to use them Mock-ups
Send a message by itself Tried
A routine or a follow-up can post to the group without anyone asking — a morning summary, a due-date reminder. This is the only kind of message that costs (see limits).
It can also tag a person in the group — "@Nok the Acme invoice is due today" — as a real, tappable mention Tried.
Keep what people share Needs Woodstock work
Every photo, PDF and voice note sent in the group arrives at the bot, and the prototype could download all of them. In Woodstock they would land in the channel and be read like any drop — so a receipt becomes a searchable source and a filed page, and can be found and shared again later.
Join and connect Invite: tried Connect: not built
When someone invites the bot, it hears about it at once and can answer for free — tried in the prototype. That makes it the natural moment to ask which Woodstock channel this group belongs to. The card and button below are a mock-up of that idea; no connect flow exists yet.
What LINE won't allow
These are LINE's rules, measured in the prototype unless marked.
Use cases
| Group | Someone in LINE… | Woodstock… | Ready? |
|---|---|---|---|
| Shop + accountant | drops a receipt photo | reads it, files it under Expenses, confirms in the group | Needs Woodstock work |
| Sales team | asks ws "ราคาส่ง Acme เท่าไหร่" | answers from the price-list page, with a link | Tried |
| Owner + staff | gets "3 bills due this week" every Monday | runs a routine and posts it | Needs Woodstock work |
| Project with a client | asks "what did we decide on Thursday?" | answers from the meeting page | Tried |
| Field team | sends a voice note after a site visit | transcribes it into a visit note | Not yet possible |
| Anyone | asks "send me last month's Acme invoice" | finds the saved file and sends it back as a link | Needs Woodstock work |
Voice notes are "not yet possible" because Woodstock doesn't store audio files today; it needs a new file type and a transcription step.
To decide before it's built
The prototype answered with a stand-in, not Woodstock's own agents. Building it for real needs these settled first — none are LINE limits:
- Who is speaking? People in the group mostly have no Woodstock account. Woodstock needs a new kind of author — "a person from LINE" — that can wake an agent.
- What can the group see? Everyone in the group reads every answer. An answer must only use what the whole group is allowed to see, not everything the person who connected the group can see.
- Do people know? Keeping a group's messages and files in Woodstock needs the group's consent (Thai PDPA).
Notes for designing cards
- Cards are LINE's Flex format: boxes of text, separators, buttons and images. Thai, bold spans, muted colours and full-width buttons all render well on phone and Mac.
- A swipeable row of cards suits "these pages"; a single card suits one answer.
- Buttons either open a link or send a message back — a tapped button counts as a new question, so it is free to answer.
- Mixed Thai and English can blur. In a Thai message, short English words take the Thai font's shapes — on iPhone, "ws มีเอกสาร…" reads as "พร มีเอกสาร…". Keep keywords and short labels in one script, or set them apart.
- Keep a plain-text fallback. Every card carries a short text version that shows in notifications and chat lists.
Connectors
Give agents read-only access to approved GitHub repositories and Linear teams, file and edit Plane work items from a channel, save files to Google Drive and work in Google Sheets, and see merged pull requests as updates in a channel.
Channel threads
Side conversations inside each channel, with a personal thread list and agents that stay in the discussion.