Overview

Communications let you send messages to end users at the right moment — by email, push notification, SMS, WhatsApp, Telegram, in-app screen, or chat. Each communication has one or more channels, audience rules, and a trigger (a system event or a manual send).

Labels match brand mek (en) in Admin.

Open Content → Notifications Center for recurring (event-driven) templates, or Messaging Center for manual campaigns.

Choose the right trigger: Recurring templates need a trigger event and parameters. See the communication trigger events reference for every option and when it fires. Matchmaker brands: use the EM slot table. Chat nudges: see It's Quiet Here parameters, timing overview, and App Settings labels (self-service timer edits under Mobile App).

Communications list

Each row is one communication template, grouped by Category:

ColumnWhat it showsNotes
NameInternal name for this communication (editable inline when you have edit permission).Double-click a category row to rename the category.
EventThe system event that triggers this communication (recurring only).One-time rows always show the one-time event.
ParamAdditional parameters that narrow when the template runs (for example a specific introduction status or chat event type).Human-readable labels come from your brand’s status and event lists.

List actions

ActionWhat happensWho can use it
Pushes pending communication content, translations, and info screens live so event-driven sends and member-facing copy use the latest saved versions.Publish permission on the communications list
Communication (add)Opens a new template starting on the email channel. For one-time, opens with the one-time event already set.Add permission
Category (add)Creates a new grouping folder for the list.Add permission

WhatsApp Templates — Collapsible section at the bottom of the recurring list. Create, refresh, submit, and delete WhatsApp templates that approved channels can pick on each communication.

Click a communication row to open the detail page.

Communication detail page

Configure one template: header, audience rules, each channel, delays, and send history.

The left navigation switches between channels and utility sections:

SectionPurpose
EmailSubject, template body fields, preview, and tap-through actions.
PushTitle, body, in-app live behavior, and open actions.
SMS text and optional deep link.
TelegramTelegram message body.
WhatsAppPick an approved WhatsApp template (not available for one-time comms today).
In-appShow a popup or curtain info screen inside the app.
ChatInsert one or more Lora chat lines (text, question, or sub-questionnaire).
HistoryDelivery log for the currently selected channel.
Communication DelaysWait intervals after the trigger before sending (recurring only).

Above the channel area:

  • Pre-validate (collapsible) — audience eligibility rules shared with groups and questionnaires.
  • Channel status control — set Draft, Active, Deactivated, or Internal for the channel you are viewing (see below).

If a channel is not configured yet, you see Channel is not active with a button to add that channel to the template.

Channels

Each channel is optional. Enable only the channels you need; a template can email without push, or push without email.

Email

FieldWhat to enterMember effect
Email TitleSubject line (supports merge fields your brand configures).Shown as the email subject.
TemplateLayout preset (introduction update, system, login verification, matchmaker variants, free-style body, etc.).Controls which body fields appear below.
Header / body fieldsTemplate-specific text blocks; free-style uses a rich-text editor.Rendered in the outgoing email.
Action URLWhere the primary button or link opens (app screen, content screen, share sheet, custom action, etc.).Member taps through from the email into the app or web.
Decline URLOptional secondary action (for templates that include decline).Second button path when the template supports it.

In the free-style rich-text body, select an inserted image to open its floating toolbar — the link icon there makes the image itself clickable to a URL (e.g. a video link), so you don't need separate "click here" link text next to it.

Push

FieldWhat to enterMember effect
TitleNotification title.Shown on the device banner.
BodyNotification text.Shown under the title; may truncate on some devices.
While app liveNone, popup, inner message, or app screen.When the app is open, controls whether the member sees only a banner or also an in-app popup/screen.
Action URLsWhere tapping the notification navigates.Opens the chosen screen or deep link.

FieldWhat to enterMember effect
SMS contentPlain-text message.Sent as an SMS when the channel is Active and the member has a phone on file.
Optional action URL (same action picker as email).Link embedded for tap-through where your SMS provider supports it.

Telegram

Message body field—same pattern as SMS without a separate link section in Admin.

WhatsApp

FieldWhat to enterMember effect
TemplateChoose an approved template from the list (manage templates on the communications list page).WhatsApp delivers the approved template body. Variable slots come from the template definition.

One-time note: WhatsApp is not supported on one-time communications in Admin today—the channel shows a not-supported message.

In-app

FieldWhat to enterMember effect
ScreenPopup or curtain info screen from Content → Info screens.Overlays the app when the comm fires.
DismissableToggle whether the member can close without acting.When off, they must use screen buttons to continue.
Expiration dateLast day the in-app message may show (defaults about 30 days ahead).After this date the overlay is not offered.

Chat

Build a sequence of Lora chat lines delivered when the comm fires (requires Active chat channel). Rows run top-to-bottom after pre-validation passes:

Message typeWhat to configureMember effect
TextFree-text body.Chat bubble from Lora.
QuestionPick a question from the Other Questions questionnaire pool (same pool as comm-triggered chat elsewhere).Member must answer that question in chat before the sequence continues.
Questionnaire headerPick a published questionnaire; optional prevent duplication toggle (defaults on for this row type).Inserts that questionnaire’s steps in the thread when the member has not already started it on this introduction. When duplication prevention is on, the row is skipped if the member already received the same questionnaire recently.

Each chat row can override the default duplication flag — turn it off when you intentionally want repeat questionnaire headers on every trigger.

On one-time chat comms, set an expiration date for how long the chat sequence remains valid.

Full trigger-parameter reference: communication trigger events → chat channel sequences.

Channel status

Each channel has its own status—not the same as the list-level Publish button.

StatusMeaningWhen messages send
DraftWork in progress.Channel is skipped when the trigger fires.
ActiveLive for members.Channel sends when the trigger fires, pre-validation passes, and any delays elapse.
DeactivatedTurned off without deleting content.Channel is skipped.
InternalStaff or test-only sends (where your brand uses this flag).Sent only for internal/test scenarios—confirm with your team lead before using on production brands.

Send now on one-time comms only sends through channels that are Active at send time—the confirmation dialog lists which channels will fire.

One-time vs recurring

Communications are either one-time (sent manually to a specific audience) or recurring (sent automatically each time the trigger event fires):

  • Recurring — fires automatically whenever the configured system event occurs and parameters match. Examples: push when someone receives a new introduction; email after a profile status change. Supports Communication delays and trigger-event parameters.
  • One-time — you manually trigger from the detail page. Useful for announcements, campaigns, or re-engagement. Supports Send now (all qualifying members) and Send by profile IDs (specific member ids). Optional profile-status filter in the header applies to profile-id sends.

Audience rules (pre-validation)

Pre-Validation on a communication restricts who may receive it—for example only approved profiles, or only members in a particular city. When a member does not pass the rules, every channel on that template is skipped for that send. Other communications are unaffected.

Configure rules in the collapsible Pre-validate section on the detail page. The editor is the same as on groups and questionnaire steps.

Rule groups are combined with OR. A member receives the comm as soon as one group passes; the AND/OR switch applies only within a group. To require two rules together, add the second row to the same group with the + button — not with Add `OR` condition, which starts a new group and widens the audience.

Live audience counts (one-time communications). Each rule group shows how many profiles that group alone currently matches, refreshed as you edit. The counts respect the profile statuses selected in the header. A group whose count is close to your whole member base is matching almost everyone — check whether it was meant as a separate OR group.

See Pre-Validation for how to build rules and which condition operators work in communications.

Communication delays

Recurring templates only—wait after the trigger before sending.

Open Communication Delays (or the collapsible Communication Delays card on recurring templates) to add one or more wait intervals—for example 24 hours after an introduction is created, then another nudge 72 hours later.

  • Each interval is stored in minutes (you can pick minutes, hours, or days in the editor).
  • When the trigger fires, the system schedules reminders instead of sending immediately. When a reminder becomes due, the send runs with the delayed-execution system event.
  • Delays apply to the whole template—configure per-channel content first, then set timing here.

One-time communications do not use this section; use Schedule send for later in the send dialogs instead.

Send dialogs

One-time communications only (after the template is saved).

Send now

Field / buttonWhat to doWhat happens
Confirmation textLists which channels are Active and will send.Review before confirming.
Recipient previewRead the count shown for each rule group, plus the combined total.Groups are OR'd, so the total is an upper bound that counts anyone matching more than one group twice. Counts are taken before per-member notification preferences and the duplicate-send window, so the delivered number can be lower — but never higher.
Schedule send for laterCheck to pick a date and time at least one minute in the future (up to 15 days ahead).Schedules a bulk send for all qualifying members at that time instead of sending immediately.
Send to a limited number of profiles (test send)Check and enter a maximum (defaults to 15, up to 5000).Only the first N matching members receive the send — a safe way to sanity-check a new audience before sending to everyone. Combines with Schedule send for later: a scheduled send keeps its limit when it fires.
Send now / Schedule sendConfirm.Saves the template, then queues or immediately publishes the one-time system send event.

Send by profile IDs

FieldWhat to enterWhat happens
Profile IDsPaste member profile ids (UUIDs), separated by commas or new lines. Invalid tokens are ignored.Only listed members are targeted. Duplicates are removed.
Profile status header filterIf you set statuses in the header, ids not in those statuses are filtered out.Counts of skipped members are returned to the server; no message is sent to filtered-out ids.
Schedule send for laterOptional future date/time (same rules as Send now).Creates per-member delayed reminders instead of immediate delivery.

Both dialogs require at least one Active channel with content. Save the template before send buttons appear.

Actions

ActionWhat happensWho can use it
SaveSaves changes to the communication template. Does not send anything by itself.Edit permission on the detail page
(list)Publishes communications, translations, and info screens together so live sends use updated copy.Publish permission on the list
Send nowImmediately or scheduled bulk send for one-time templates.Edit permission
Send by profile IDsSend to specific member ids (optional schedule).Edit permission
Delete ChannelRemoves configuration for the channel you are viewing and saves.Edit permission
Delete communicationPermanently removes the entire communication template.Delete permission

Reference