How To Use Opine

Manage communities at a glance

Opine provides a suite of tools to run your community effectively. Instead of spreadsheets and scattered forms, you visualise member activity and health in one place.

Capturing user sentiment

Sentiment is captured across every touchpoint — events, feedback forms, and polls. Opine uses an AI workflow to turn each response into a sentiment score between 0 and 1:

• 0 — Unsatisfied
• 0.5 — Neutral
• 1 — Happy

The Analytics Hub

The Analytics Hub is your command centre — an immediate overview of your entire organisation or workspace in a single click.

• Community Health — a single score out of 100 with member, response, survey, and event counts, and a link through to detailed sentiment analytics.
• Member Quadrants — your members grouped four ways (Champions, Dormant Advocates, At-Risk Regulars, Disengaged), each with the themes driving that group and a plain-language explanation of who's in it. Click any name to jump straight to that person's member detail page.
• Workspaces — a health bar per workspace, so you can see which stream of work is carrying the community and which is drifting.
• Member Spotlight — an individual worth your attention right now, with the sentiment behind it.
• Events — one panel covering upcoming and past events. Upcoming are ordered by what's happening soonest, past by what ran most recently, and every column is sortable. Expand an event for its RSVP, attendance, and feedback breakdown.

Understanding performance metrics

Every event, feedback form, and poll captures its own performance metrics. The Summary tab opens with a compact row of cards:

• Overview — total responses, how many were completed (with the rate), the share of questions that got an answer, and the aggregate sentiment score.
• Respondent Types — the split between organisation members and non-members.
• Attendance (events only) — expected attendance, who checked in, and no-shows.
• AI Summary — a few sentences on whether it went well, why, and the one thing worth improving. Click it for the full text.

Below the cards sit the notable user sentiments, then a per-question breakdown with trend analysis across event instances.

Moving beyond guesswork

Opine turns qualitative interactions and survey responses into quantifiable, actionable data — so you can shift from reactive troubleshooting to proactive care, and spot falling sentiment early enough to intervene before members disengage.

Creating an account

Head to app.opine.asia to open the web app. You can sign up two ways:

• Google — sign in with your Google account for instant access.
• Email — register with an email address, then click the confirmation link we send to verify your account.

Linking your account with Telegram

Linking Telegram lets you use bot-based features and open the Opine web UI directly inside Telegram. After creating your account, a banner appears at the top of the web app with a Link Telegram button; click it and confirm the connection in Telegram.

Bot commands

• /home — open the Opine web interface in Telegram to view events and your profile.
• /inbox — read messages sent to you by organisations.

Creating an organisation

Open the org selector on the home screen and switch to the Organisation view. Click Create Organisation, enter a name, and confirm to initialise your workspace.

Working with workspaces

Workspaces (previously called Projects) sit under an organisation and group related events and surveys. A new organisation automatically gets a First Workspace so surveys and events can be created immediately. Use the workspace selector in the header to switch scope; a Viewing badge shows which workspace you're scoped to, so it's always clear whether the numbers on screen cover one workspace or the whole organisation.

Select a workspace and open its Workspace Settings tab to rename it, edit its description, or delete it.

Tracking workspace sentiment

Just like the organisation view, you can drill into the sub-sentiments for a single workspace via the Action Hub — click View Detailed Sentiments.

Your organisation landing page

Every organisation gets a public landing page you can share with members or guests. Edit it in the Landing Page Editor — set social links, toggle whether the page is public, and enable a Join Community button or a Paid Membership button. The editor is an extension: switch it on under Community Extensions and its sidebar tab appears.

Organisation settings

The Organisation Settings tab is the control panel for your community, split into tabs so each area stays manageable. The admins and workspaces tabs both have a search box, which matters once you're past a handful of either. From here you can:

• Add admins and create admin groups for survey management.
• Enable an event-approval process for chapters.
• Enable auto onboarding — anyone who attempts a form is invited to join as a member, and a Join button appears on the landing page.
• Enable paid onboarding and attach a paid onboarding form.
• Manage Telegram connections (see the Telegram Connections chapter).

Showing and hiding features

Not every community needs every tool, so the optional ones live in their own tab: Community Extensions. Each is a card you can open before deciding — what it does, what it adds to your sidebar, and any settings of its own — with the on/off switch on the card and on its page.

• Chapters — sub-communities nested under this one, each running itself.
• Telegram Connections — link your Telegram groups to recruit and broadcast from them.
• Landing Page Editor — a public page for your community.
• External Imports — bring in events and responses hosted on Luma, Google Forms or Microsoft Forms.
• PDPA Consent — a data-protection consent question on the forms you create (see Surveys → PDPA consent on your forms).

Admins and roles

Add admins under Organisation Settings. If they already have an Opine account they're added directly; otherwise they receive an email invitation. There are three roles:

• Owner — full visibility across all workspaces and surveys; cannot be removed.
• Admin — visibility across all workspaces and surveys; can add or remove other admins.
• Member — a workspace-scoped role that only sees and creates within its allocated workspaces, plus any surveys shared through an admin group.

Admin groups

To streamline permissions, create Admin Groups and attach a whole group to a survey or workspace at once.

1. Open Organisation Settings or Survey Settings.
2. Click the User Groups button.
3. Edit an existing group or create a new one.

Receiving analytics as an admin

Admins can opt in to receive analytics once a survey's analysis completes. Notifications arrive via the Opine Inbox, or by email if the account isn't connected to Telegram. Organisation-level analytics for admins are broader than survey analytics — they include organisation and workspace sentiment, with an option to drill into a specific survey.

Linking a Telegram group

Add the Opine bot (@opine_assistant_bot) to your Telegram group. Then, in Opine's Telegram Connections tab, copy the provided command and paste it into the group chat. The bot replies with a success message once linked.

Inviting users from Telegram

From a linked group you can invite users to create an Opine account or join with a specific role, using the commands listed in Telegram Connections:

• Create account — posts a button that sends users to the bot to create their Opine account.
• Invite as member — posts a role-tagged button; tapping it adds the user to your organisation with that role and sends a confirmation via the bot.

Onboarding your first members

Users can become members three ways: manual email invitation, automatically when they interact with a form or event (if auto-onboarding is on), or via the Telegram bot in a linked group.

Inviting by email

1. Open the Members Management tab.
2. Choose Add Member (single) or Upload CSV (bulk).
3. Users are prompted to join by email or on their next survey attempt.
4. If they aren't on Opine yet, they get an invitation email with a dedicated account-creation page.
5. Optionally tag them with a member type as you invite.

Reading the member table

Search by name, filter by role, and invite — single or bulk — from one toolbar. Alongside each member's sentiment sits their engagement group: Champion, Dormant Advocate, At-Risk Regular, or Disengaged. Filter on that column to work one group at a time, and sort by it to bring the members who need attention to the top.

Automatic & paid onboarding

Enable auto onboarding in Organisation Settings to prompt any registered user who starts a form or event to join — on the web, in Telegram, at the bottom of an event page, or from the landing page. For paid onboarding, create a form of type Onboarding and attach it to the landing page or share its link directly.

Onboarding forms don't require an account

Onboarding forms used to force respondents to create an Opine account and join before they could answer, which cost sign-ups at the worst possible moment. They no longer do: anyone with the link can complete one, and every onboarding form carries a required Name and Email question so you always know who replied.

You then decide who becomes a member. Open the form's Responses tab and invite respondents to the community from there, tagging a member type as you go — so joining is something you offer people who already showed interest, rather than a toll gate in front of the form.

Capturing custom member data

Add custom data variables from the Members Management tab via Add Optional Member Data. Define a variable and mark it required or optional. When a member starts a survey they're prompted to fill in these values; required ones must be completed before proceeding.

Membership types & roles

Create member types (roles) with a name, description, visibility (Hide from Members), and default duration. If a duration is set, each membership gets an expiry date.

Once a member accepts their invitation, click their row in the members table to tag them with the appropriate tier. All roles are visible on a user's profile unless Hide from Members is on.

Renewals

Member types with a duration expire, and chasing those expiries by hand doesn't scale. Attach a renewal form to a member type and Opine handles the reminder for you: as a member's role approaches its expiry date, they're emailed a link to that form. Each member is reminded once per cycle, so nobody gets pestered daily.

Submissions land in the Renewals view, where you review what they filled in — the submitted response is one click away — and confirm the renewal, which extends the membership by the type's duration.

Broadcasting updates

Create broadcast groups under the Broadcast Management tab by selecting members. You can then send custom emails or Telegram messages to specific segments — predefined broadcast groups or micro groups.

Did anyone actually read it?

Every email broadcast reports an open rate and a click rate, so "we sent it" and "they saw it" stop being the same claim. The click breakdown is per link: if a message has three calls to action, you can see which one people chose.

The Broadcast History table lists past sends with their open and click rates, searchable and filterable by type, status, and date. Open one for the detail view — a Message tab pairing the content with its preview, and a Recipients tab you can search and filter, showing per person whether they received it, opened it, and clicked.

Creating a survey

Surveys live inside a workspace, so create an organisation and workspace first. Survey types are General (standard questionnaires) and Onboarding (used to bring new people into the community — see Member Management). The creation wizard lets you configure:

• Allow Multiple Responses — let registered users submit more than once.
• AI Assistance — swap the static form for a conversational AI that interviews the respondent.
• Micro Groups — adds a tab to group respondents (see the final chapter).
• Pulse Checks — adds follow-up questions and segmented cluster analytics (see the final chapter).

Editing questions

Open the Survey Editor to modify questions. Each question supports a description, image attachment, and settings such as min/max length. Conditionals can branch the flow based on Single Choice, Multiple Choice, or Yes/No answers.

PDPA consent on your forms

Turn on the PDPA Consent extension and write your data-protection notice once, under Community Extensions → PDPA Consent: a question title and the policy text respondents read. Opine ships a sample policy to start from — replace it with your own wording and contact details before you put it in front of anyone. It is a starting point, not legal advice.

Every form you create after that carries a Yes/No consent question at the end, already filled in with your wording and switched off. Open the question in the survey editor and use its switch to ask for consent on that form. Once it's on, a respondent has to answer Yes before they can submit.

• The wording cannot be changed on an individual form — that is the point of setting it once, so everyone agrees to the same thing.
• The question stays last, and moves with you: add a section and it follows to the end of the new one.
• It cannot be deleted, dragged, or duplicated, and deleting the section it sits in keeps it.
• While it's switched off, respondents never see it — on the web, in Telegram, or in the AI chat.

Settings, sharing & collaborators

The Survey Settings tab exposes the same behaviour toggles as creation, plus Close Survey and a custom close message. Add collaborators here by selecting an admin group. Share the survey two ways:

• Web Share — opens the web version of the survey.
• Telegram Share — routes respondents to the Telegram bot.

Importing and adding responses

Responses don't have to arrive through the form. If you ran something on paper, in another tool, or over a chat, you can get that data into Opine and have it analysed alongside everything else. Both routes live under the Import button in the responses toolbar.

Import a CSV

1. Choose Import CSV and upload the file.
2. Map each column to a question. Opine matches obvious headers for you; correct anything it got wrong.
3. Optionally point it at an Email and a Name column. Email lets Opine merge a row onto an existing respondent instead of creating a duplicate; Name fills in who the response belongs to.
4. Review the preview — it shows exactly which rows will be created, which will be updated, and which columns are being ignored — then import.

Add a single response

Choose Add Response to type one in by hand — useful for a late paper form or a reply someone gave you in person. Turn on keep adding and the form stays open after each save, so a stack of paper forms is one sitting rather than one modal per response.

Survey insights

View analytics under the Responses tab. A submitted response automatically schedules analytics to run 24 hours later, or you can force it with Run Survey Analysis from the Summary tab. Metrics include average sentiment, aggregated ratings, and clustered groupings of open-ended answers.

Each run also writes a short AI Summary to the Summary tab: a few sentences on whether it went well, why, and the single thing most worth improving, with the full text a click away. It's meant to be the thing you read first.

Creating an event

Create events from the Organise Events tab (an organisation and workspace are required first). On creation, a feedback form is generated and attached automatically. The event editor has tabs for Settings, Event Editor, Feedback Editor, Event Management, Broadcast Management, and Responses. The creation wizard covers:

• Make Event Public — visible to all users on the platform.
• Member-Only Event — block non-members from RSVPing.
• Allow Multiple RSVPs — let users RSVP more than once.
• Auto-Confirm RSVPs — pick a member type that bypasses the waitlist.
• AI Assistance — applies to the feedback form.
• Feedback Reminder — auto-remind attendees to submit feedback after the event.

Event settings & recurring instances

The Event Settings tab tweaks visibility, RSVP rules, auto-confirm, feedback options, and close controls. For recurring events, add specific dates under Event Instances — the walk-in QR can then check people in for different days (e.g. a multi-day workshop). Turn on the instance selector to make respondents pick their date before the feedback survey.

Managing attendees

Handle sign-ups under the Event Management tab. Attendees have one of three statuses: Confirmed, Waitlisted (the default unless auto-confirm is on), or Cancelled. Accept or reject sign-ups manually here.

Status changes trigger an automatic notification email. You can customise each status template via the cards at the top of the page and preview them with Test Email. The RSVP table marks anyone who isn't a member of your community as a Guest, so you can see at a glance how much of your turnout is coming from outside.

The Email Broadcasts card carries the engagement figures for everything automated Opine sent these attendees. Open it to see each broadcast type — confirmations, reminders, announcements — with its own open and click rate, so a reminder nobody opens is visible as a reminder problem rather than an attendance mystery. The RSVP table also has an Opened column for the per-attendee view.

Check-in & attendance

Take attendance two ways, both under the Check-In Management tab:

• Walk-in QR — attendees scan a QR for the selected instance. Unregistered users are auto-registered and checked in; confirmed users are checked in; unconfirmed users see a 'reservation not confirmed' message.
• Manual scanning — on a mobile admin device, tap Scanner QR for the correct instance and scan attendees' ticket QRs.

Announcements & feedback reminders

Use Broadcast Management to email or Telegram attendees. Feedback reminders can be sent to attendees of a specific date who checked in but haven't completed the feedback survey — delivered via Telegram where available, otherwise email. A reminder can only be triggered once per event date.

Emailed announcements and reminders report open and click rates the same way broadcasts do, so a reminder that went out but changed nothing is easy to tell apart from one nobody opened. See Broadcasting updates for how the rates are counted and their caveats.

Post-event analytics

The Responses tab offers several views:

• Summary — the statistic cards, the AI summary, automated sentiment analysis with low-sentiment alerts and clickable sentiment cards, and per-question analytics that show metrics rising or falling across instances.
• Responses — the individual rows, with search, filters, and export.
• Response Detail — click a row for the full response, plus comments, micro groups, Telegram invites, and member tagging.
• Trend Analysis — inside the response detail: one person's answers over time (needs multiple responses or instances).

For a recurring event, use the view selector at the top to switch between the combined picture across every instance and a single date.

Pulse Checks

Enable Pulse Checks in survey settings to add a Pulse Checks tab under Responses. It analyses responses against member-level data across four quadrants:

• Champions — high attendance, high sentiment.
• Dormant Advocates — low attendance, high sentiment.
• At-Risk Regulars — high attendance, low sentiment.
• Disengaged — low attendance, low sentiment.

Micro Groups

Enable Micro Groups in survey settings to add a Micro Groups tab under Responses. Group members manually or automatically with AI, choosing mentors as anchors per group. Preview generated groups, confirm them, shift members between groups, and export the result to Excel.

Choosing what the respondents table shows

Use the Columns button beside the search box to decide what you group people on, without leaving the table:

• Any survey question as its own column, so answers sit next to each other rather than one response detail at a time.
• Comments — the notes already recorded against that person, each attributed to whoever wrote it, with a + to add one without opening their profile.
• Member Types — the roles they currently hold, filterable by type when you want one group per tier.
• Completed At and Anchor can be switched off when you don't need them.