---
url: https://docs.oakmega.com/en/recipe.md
---

# Recipes

Complete walkthroughs that combine several features, such as sending a coupon and adding a tag when someone becomes a friend.

* [Give new friends a pass and tag them when they join](/en/recipe/new-friend-coupon-and-tag)：Combine a welcome message bot, tags and a pass into a new-friend gift: the moment someone adds you, they're tagged "New friend" and get a link to claim a pass that only new friends can see, limited to one per person, with claiming and using it tagged automatically too. This recipe also covers what existing friends see when they tap the link, which bot replies when several welcome messages are on, and whether people who block and re-add you count as new friends.
* [Find interested members with an approved page, then post to them by tag](/en/recipe/approved-page-segment-broadcast)：Before a product launches, share an intro page, and whoever opens it is tagged automatically. On launch day, send the offer only to people who viewed the intro and haven't bought yet, so you don't disturb every friend each time and you save message quota. Using a new product intro page as the example, this recipe shows how tags, an approved page and a segmented post fit together, and how to check how many people viewed it and how many will get the offer.
* [Collect event sign-ups with a form, tag and confirm automatically, then send reminders by session](/en/recipe/form-leads-follow-up)：Run event sign-ups without tidying spreadsheets: collect them with an OakMega form, and everyone who submits is tagged with the sign-up and session tags, gets a confirmation in LINE, and has their name and phone saved to member data. The day before, remind each session by its tag. Using a product preview event as the example, this recipe shows how forms, tags, message templates and segmented posts fit together, how to cap seats, and how to check sign-up numbers.
* [Compare how many new friends each channel brings](/en/recipe/channel-friend-tracking)：Put a separate New/Existing Friend Link on your store poster, Instagram bio and product packaging to see which channel brings the most new friends. New friends are tagged with their source and get a welcome gift automatically, while existing friends who tap the link get this month's offer. This recipe covers creating a link per channel, reading new friend counts and conversion rates, who isn't counted as a new friend, and what deep links are good for in this scenario.
* [Take bookings with Booking Center, tag by booking status and send reminders](/en/recipe/booking-reminder-and-tag)：Booking Center doesn't remind members on its own. This recipe shows a store how to fill that gap: tag members and send a confirmation automatically when they book; the day before, download the bookings, pick out tomorrow's guests and remind only them with a 1-day expiry tag; switch people who cancel to another tag automatically and invite them to rebook. It also covers rescheduling, canceling, staff notifications and reminders when you take bookings every day.
* [Take in-store bookings, give a repurchase voucher after the visit, and remind people who haven't come back](/en/recipe/store-booking-to-repurchase)：How a store can use LINE to turn an in-store booking into a repurchase: open free skin check bookings with Booking Center and a form, tag members and send a confirmation automatically when they book; after the check, staff show the QR code of a repurchase pass, claiming it adds "Skin check done in store" and using it at checkout adds "Repurchased"; then filter by tag to remind only the people who came in but haven't bought again. It also covers whether no-shows can claim the pass and what happens when a booking is canceled.
* [Auto-DM and tag people who comment on Facebook or Instagram posts](/en/recipe/comment-to-message)：Publish a "comment +1 and we'll DM you a code" post, and let a comment reply bot reply under each comment, send the commenter a discount code by direct message and tag them; add a LINE add-friend link in the message to bring Facebook and Instagram fans over to LINE for the long term. This recipe ties together comment reply bots, tags and a New/Existing Friend Link.
* [Product launch: compare friends from each ad channel, then post only to interested people](/en/recipe/launch-campaign-by-channel)：When a product launch runs on IG ads, FB ads and an influencer post at the same time, give each channel its own New/Existing Friend Link to see which brings the most new friends. Put the product page's LINE deep link in the welcome message so everyone who opens it is tagged as interested, and on launch day post the offer only to them. This recipe walks through a skincare brand's launch from start to finish.
* [Membership Month: give a welcome pass to friends who fill in their profile](/en/recipe/member-signup-campaign)：For a membership drive, send every new friend a member profile form as soon as they join. When they submit it they're tagged and get a claim notice automatically, and the welcome pass is visible and claimable only to people who filled in their details. This recipe walks through a skincare brand's Membership Month, showing how tags, a pass, a template, a form and the welcome message fit together.
* [Different Richmenus for VIP and regular members: a VIP-only menu and a VIP-only pass](/en/recipe/tiered-richmenu)：How to show VIP members a different Richmenu from regular friends in their LINE chat: mark VIPs with a tag, create a pass only VIPs can see and claim, build a segmented Richmenu with "VIP Voucher", "VIP Line" and "My Wallet" buttons, then apply it to VIP members in bulk from LINE Member Management. It also covers switching the menu for newly upgraded VIPs and switching it back when they're downgraded.
* [Lucky draw: collect entries with a form, draw from the downloaded list, then notify winners and everyone else](/en/recipe/lucky-draw)：For a LINE friend lucky draw, use a form that only accepts friends, within an entry period and once per person. Download the responses, draw winners in a spreadsheet, tag all winners at once by LINE User ID, then post separate articles to winners and to everyone who didn't win. This recipe walks through a skincare brand's 10th anniversary draw from entry to notification.
* [Win back inactive members: find dormant friends with an expiry tag and send a welcome-back gift](/en/recipe/win-back-inactive)：OakMega's member filters have no "last interaction time". This recipe records recently active members with a 90-day expiry tag, then uses an advanced filter to exclude them and recently joined friends, finds dormant members and posts an article with a welcome-back pass. A skincare brand's win-back campaign shows how tags, chatbots, the advanced filter and passes fit together.
* [Membership tiers: build monthly upgrade and downgrade lists from store visits, repurchases and spending](/en/recipe/member-tiering)：How a CRM owner can run membership tiers in OakMega: let bookings, store visits, voucher use and chatbots tag members automatically; each month, load two saved filters, "Gold upgrade list" and "Gold downgrade list", and add or remove tier tags in bulk in LINE Member Management; tag VIPs in bulk from a list of LINE User IDs exported from your POS. Then post by tier and switch to a tier-only menu. It also covers strength tag conditions, And/Or rules in filters, and batch limits.
* [Monthly performance report: which numbers to track for friends, channels, posts and service, and where to find them](/en/recipe/monthly-report)：When a CRM owner puts together a monthly LINE report, which OakMega numbers can show "this month" and which are only cumulative or current: count this month's new friends and blocks with a saved filter in LINE Member Management, compare channels with the statistics interval on New/Existing Friend Links, download data for articles published in a set period to see impression and click rates, then add service, tag and pass numbers to a single monthly report table. It also covers limits such as "Month Is" ignoring the year and the Service Center Data Center having no response times.
* [Bring customers who haven't added you on LINE back to your official account by SMS, and track how many join](/en/recipe/sms-to-line)：When you have customers' phone numbers but they aren't LINE friends yet, here's how to bring them to LINE by SMS: create a New/Existing Friend Link in OakMega that applies "Source: SMS" on click, so new friends get a welcome message and the member profile form; save the SMS content as an SMS template within 66 characters, then send it from Every8d. Finally, use the link data and tag counts to see how many new friends the SMS brought in. Also covers the current limit that the new dashboard can't send SMS directly.
* [Split permissions between HQ, stores and support: who can post, who can see members, and who sees only their own store's conversations](/en/recipe/team-permissions)：How to share out permissions in OakMega when your brand has HQ marketing, store managers and support agents: use identities in Permission Management to decide which features each job can use and whether it can download member data, then use Service Center roles and organizations so store staff only see their own store's conversations. Includes a permission table for the three jobs and explains the limits, such as workspace permissions not being able to split data by store and Service Center having no "View Only" option.
* [Your first week with Service Center: activation, assignment, auto-close and notifications](/en/recipe/service-center-first-week)：The first time you open Service Center, you need to finish activation, get conversations to the right organization and agent, close resolved conversations automatically, and make sure agents get notified. Using a skincare brand's rollout, this recipe shows how the setup wizard, an organization's assigned tag, Auto Distribute to Agent, automatic closing, a chatbot that transfers to Service Center and APP notifications fit together, and explains a common trap: the setup wizard doesn't distribute conversations to agents by default.
* [Self-service FAQ: route questions with a Richmenu and chatbots, and hand off to a person only when needed](/en/recipe/self-service-faq)：How to let members find answers to common questions themselves with a LINE Richmenu and chatbots: menu buttons send fixed text, and keyword chatbots answer directly with "Trigger Keyword (Equals)"; when a question is out of scope, an event-triggered bot's "Default Reply" points the member back to the menu or to a person; and only when a member sends "Talk to staff" does the conversation go to Service Center. Also covers when the Default Reply doesn't trigger.
* [Reply automatically after hours and pick up the next day](/en/recipe/after-hours)：How to make sure members who ask for a person after hours don't feel ignored: two chatbots share the same keyword; one uses a "Weekly Effective Period" so it only replies during business hours, and the other replies after hours that you'll follow up the next day and applies the "After-hours message" tag. The next morning, agents use the tag and the Open status to find last night's messages. Also covers which chatbot replies when both match, and how the time zone and end time of a time range work.
* [Tag complaint keywords automatically and send them straight to a support supervisor](/en/recipe/complaint-escalation)：How to make sure complaints on LINE don't slip past your regular agents: a chatbot's "Trigger Keyword (Contains)" catches words like complaint, refund, return and allergy, replies with an apology, applies the "Complaint: needs supervisor" tag and transfers the member to Service Center, and an organization's assigned tag routes the conversation straight to a support supervisor. Also covers what happens when the conversation is already in service or the member matches several organizations, and how supervisors find complaints that were missed.
* [Give every salesperson their own QR code, see how many friends each one brings and route chats to them](/en/recipe/sales-personal-qr)：How to give every salesperson or beauty advisor their own add-friend QR code: one New/Existing Friend Link per person. When a new friend scans it, a chatbot applies an "Advisor: …" tag and transfers them to Service Center, and an organization containing only that advisor routes the conversation straight to them. When an existing friend scans it, they're tagged and asked to send a keyword to reach the advisor. Also covers how to compare how many friends each person brings, and the limits: existing friends who scan aren't transferred to Service Center automatically, and members already in another organization stay there.
* [One LINE Official Account, separate AI for after-sales and VIP](/en/recipe/line-departments-different-ai)：On a single LINE Official Account, send regular customers' repair requests to an after-sales AI and VIP customers to a VIP AI that speaks differently and offers different benefits. Using a home appliance brand, this recipe shows how tags, chatbots with Service center transfer, organizations' assigned tags and "Transfer to Agent → Enable AI Agent" work with two OakXgen AIs, with real test screens from a phone.
* [Managing customers on LINE for manufacturers: an overview for sales, after-sales service, and distribution](/en/recipe/manufacturing)：How manufacturers use OakMega to manage customers on LINE: find customers interested in a product line with digital catalogs, route trade show leads to sales by region, use a QR code on the machine for warranty registration and expiry reminders, hand repair requests to Service Center and AI triage, and track lead sources with a dedicated link for each dealer. This page groups the recipes that fit manufacturers by sales, after-sales service, and distribution.
* [Send digital catalogs on LINE for manufacturers: find interested customers by product line and hand them to sales](/en/recipe/manufacturing-product-dm)：How manufacturers can send product catalogs on LINE and find the customers who are really interested: build one approved page per product line as a digital catalog, tag customers with that product line automatically when they view it, then let sales filter the list by tag, send a trial cutting invitation only to catalog viewers, and follow up on replies in Service Center.
* [Capture trade show leads for manufacturers: one QR code at the booth, routed to sales by request and region](/en/recipe/manufacturing-trade-show-leads)：How manufacturers can capture trade show leads on LINE and route them to sales: put one form QR code at the booth, visitors scan it, add your account as a friend and fill it in, their answers apply "Request: catalog", "Request: factory demo" and region tags automatically, every lead is transferred to Service Center and assigned to the sales team for that region, and after the show you send the digital catalog or book factory demos based on what each lead asked for.
* [Warranty registration for manufacturers: a QR code on the machine to register serial numbers, and automatic picks of customers whose warranty is about to expire](/en/recipe/manufacturing-warranty-registration)：How manufacturers can run product warranty registration and expiry reminders on LINE: put one QR code on the machine or in the user manual, customers add your account as a friend and register the serial number, model and delivery date in a form, product-line and "Warranty registered" tags are applied automatically, and a 335-day expiry tag works as a timer so each month you send maintenance and extended warranty reminders only to customers whose warranty is about to run out.
* [After-sales repair requests for manufacturers: a "Repair request" button on the Richmenu, routed to service teams by machine model](/en/recipe/manufacturing-repair-request)：How manufacturers can take repair requests on LINE and route them to the right service team: a "Repair request" button stays on the Richmenu, customers open a repair form and enter the machine model, serial number and problem, options apply product-line and issue tags automatically, each request is transferred to Service Center and assigned to the service team for that product line, and conversations close automatically once resolved so the next request is routed again.
* [Dealer management for manufacturers: one dealer portal link, then new products and pricing by tier and region once approved](/en/recipe/manufacturing-dealer-network)：How manufacturers can manage dealers and channel partners on LINE: share one Tag Routing Link as the dealer portal link, have dealers who aren't approved yet fill in a dealer registration form, and once a sales manager approves them and applies dealer and tier tags, the same link opens a dealer-only portal. New products, price changes and training are then sent to dealers by tier and region.
* [Account handover for manufacturers: review tags, form replies and handover notes in Service Center before you take over a customer](/en/recipe/manufacturing-sales-account-history)：How manufacturers can hand customers over smoothly when a sales rep leaves or changes territory: the new rep opens the customer in OakMega Service Center, reads product line, region and request from tags, sees in Member History when each tag was applied from a trade show form or catalog page, opens the form replies in the chat for the machine serial number and request, reads the handover the previous rep left in Notebooks, then assigns themselves and writes the first note.