Skip to content
OhMy.xindocs

Playbook 1: bot onboarding

A member’s first minute in your circle decides their second. This playbook combines three bot-layer features into a multi-layer guided flow: welcome-card buttons, the send-text action type, and auto-reply triggers. It all happens in chat and works with any layout.

The idea: besides opening links, a welcome-card button can send text — it posts a message as the member. If that text happens to be an auto-reply trigger, the bot answers. Button → trigger → reply card → the card carries more buttons, and a guidance tree grows.

Welcome card buttons

Settings → Welcome & onboarding. Each button is a link or a send-text action — send-text sends that text as the member.

  • ★Open the circleLink · /
  • Start here tourSend text
  • Help centerSend text

Auto replies

Console → Group chat → Auto replies. Triggers exact-match the member message; when one trigger has several rules, the first created wins.

  1. 1tourApp card
  2. 2helpApp card
  3. 3communityText
  4. 4exploreApp card
  5. 5contactContact card
每日笔记BOT

You joined the circle

Welcome to “Daily Notes”! I’m the circle bot — start with the buttons below.

每日笔记

Tap a button to begin — each one sends a message as you.

The left side simulates the console configuration (welcome-card buttons + auto-reply rules); the right side is the conversation members see. Tick “X-ray” to see the rule behind each message. Try: “Start here tour” → “Find content” → “Open the circle home”.

How it works

Section titled “How it works”
  1. A member joins; the bot delivers the welcome message and card (Settings → Welcome & onboarding).
  2. The card has a primary button (default “Open the circle”, linking to /) plus grid buttons. Each button is one of two kinds:
    • Link — opens an https://… page or a / circle path;
    • Send text — posts the given text into the conversation as the member.
  3. That text exact-matches an auto-reply trigger (case-sensitive; one rule can carry several triggers, comma-separated), and the bot replies with text, a post, a contact card, or an app card with buttons.
  4. App-card buttons support send text too — so the tree keeps going. When one trigger has several rules, the first created wins.

Four steps for the owner

Section titled “Four steps for the owner”
  1. Draw the tree before touching the console. Two layers usually suffice: entry buttons (2–3) + a second-level menu under each. Pick a trigger word per entry — it appears on the button and is the message members send, so make it readable (“tour”, “help”).
  2. Configure the welcome card. Console → Settings → Welcome & onboarding: keep the primary button as “Open the circle”, put your entries in grid buttons with kind send text, value = the trigger. Labels ≤20 chars, primary + grid ≤18 buttons total. Preview it to your own Mixin before saving.
  3. Configure auto replies. Console → Group chat → Auto replies — one rule per entry: trigger = the text the button sends; reply with an app card (title ≤36, description ≤1024, up to 18 buttons, labels ≤36). Leave the leaves to lighter types: link buttons for help docs, a post for long tutorials, a contact card for human support.
  4. Always leave a human exit. End every menu with a “contact an admin” send-text button pointing at a contact-card reply — members who can’t find an answer need a way out.

Variations

Section titled “Variations”
  • Paid circles: add a “See plans” link button on the welcome card straight to the membership page — an entry inside the chat converts faster than hoping members find the pricing page.
  • Passphrase play: use a send-text button as a passphrase that triggers a resource post or a red packet — your active members will spread it for you.
  • English circles: triggers are case-sensitive; lowercase trigger words (tour, help) save everyone the guessing.
Section titled “Related pages”