Reference (partial) — Event names and parameter lists are seeded from Admin code. Plain-language “when it fires” notes marked verified were traced in the member app or notification processor; rows marked TBD need product confirmation for your brand.

Overview

Recurring communications fire when a trigger event happens in the system. The header on each communication template picks the event and one or more parameters that narrow when this template runs.

One-time communications use a fixed trigger (One Time) and do not let you change the event dropdown. You send them manually with Send now or Send by profile IDs instead of waiting for a system event.

When an event fires, the system looks up all communication templates for your brand that match the event and at least one of the stored parameter combinations. Each matching template then checks Pre-Validation and sends only through channels whose status is Active.

Trigger event catalog

Options in the Trigger Event dropdown (recurring communications only).

Trigger event (Admin label)When it fires (plain language)Typical parametersNotes
None Never fires automatically. None Use for drafts or templates you only trigger manually.
Profile Status Updated verified — A member’s profile status changes in the app or through automated flows (not Admin bulk edits). One or more profile status values (multi-level parameters supported). Pair with pre-validation when you need extra filters beyond status.
Admin Profile Status Updated verified — A manager changes a member’s status from Admin. Profile status values (same picker as above). Separate from member-initiated status changes so you can send different copy to ops-driven updates.
Intro Update verified — An introduction’s status changes (either side). Introduction status (for example approved, declined, engaged) plus reminder variants. Includes dedicated reminder parameter values for availability and introduction nudges.
Intro Update Initiator verified — Same as Intro Update, but only when the member was the initiator of the introduction. Introduction status values. Use when initiators and responders need different messages for the same status change.
Intro Update Responder verified — Same as Intro Update, but only when the member was the responder. Introduction status values. Pair with Initiator variant for symmetric flows.
Chat Event verified — Activity inside an introduction chat thread. Reaches the member who received the message. Text, photo, video, break-the-ice, daily mood, phone-share request/allowed, and related chat types. Each parameter is a distinct chat action type.
Chat Event Sender verified — Same chat activity as Chat Event, but reaches the member who sent the message. Same chat types as Chat Event. Use when both sides need a follow-up for one action — for example a member who shares her phone number (Phone Share Allowed) gets her own feedback questionnaire, while Chat Event covers the member who received it. Pair with Chat Event the way Intro Update Initiator pairs with Responder.
Call Event verified — Voice or video call events between matched members. Missed voice/video call, partner calling, active call. See Call Event parameters for each option.
Partner Events verified — Something changed about the member’s current partner link. Partner became irrelevant, partner deleted, partner started/stopped snoozing. Useful for “your match is no longer available” style messages.
Lora Message verified — Lora chat system events (not ordinary member typing). New questionnaire assigned; image rejected. Often paired with chat-channel comms that insert Lora lines.
Questionnaire Answer Comm verified — A member submits a specific questionnaire answer that has a linked communication id on the answer configuration. Usually none in the header—the link lives on the question answer in the questionnaire editor. Configure on the answer row in View Question, not only here.
Its Quiet Here verified — A daily job detects a matched introduction chat that fits a quiet pattern (no messages, short back-and-forth, long silence, one-sided texting, phone number shared, etc.) and fires a comm for that pattern. One of the quiet-scenario parameters below (for example Empty First, Short Second). Requires the It's quiet here app feature on your brand. See parameter catalog and timing settings.
MM Emails verified — Matchmaker-facing email when a shidduch introduction changes status, times out, needs a reminder, or when matchmaker account events occur. Slot id EM0–EM26 (one per template). For brands using the matchmaker module. See the slot catalog for which slot matches which moment.
End User MM Emails verified — Member-facing message when no matchmaker is available or the assigned matchmaker is temporarily unavailable. No matchmaker assigned or Matchmaker unavailable. See end-user matchmaker emails.
Reminder verified — Scheduled reminder jobs (introduction availability, waiting introduction, did-not-finish, etc.). One of four reminder subtypes—see Reminder parameters. Timing comes from Settings → Settings → Reminders, not from the communication template. Often works together with Communication Delays on the template.
One Time Does not fire on system events—used for manual campaigns. Audience subtype (all users vs active users) or profile-status filter on one-time sends. Listed on the Messaging Center menu. Send via action buttons on the detail page.
System verified — Account verification and parent-link flows, plus delayed bulk-send execution. Verify email/phone, parent email flows, linked parent, comm delayed execution. Comm delayed execution is internal—fires when a scheduled one-time or delayed recurring send becomes due.
BO Emails verified — Email to Admin users (staff), not members. Ticket assigned, guest admin reply, profile status updated, matchmaker paid. Pre-validation is skipped when there is no member profile (for example guest support emails).
BO Socket Update verified — Real-time update pushed to open Admin browser sessions. New notification, dashboard refresh, profile import finished, AI chat message. Not a member-visible channel—used for live Admin UI refresh.
BO Admin Update verified — Notable Admin-only milestones. New institution; new engagement (introduction reached engaged status). Custom admin channels from Admin channels can extend parameter options.
Matchmaker Status Changed verified — A matchmaker profile’s status changes (available, pending, blocked, etc.). Matchmaker status value. For brands using SME/matchmaker profiles.

Chat Event parameters

When the trigger is Chat Event or Chat Event Sender, pick one parameter per template row. The same list appears for both triggers — the difference is who receives the communication (recipient vs sender).

Parameter (Admin label)Plain meaningTypical use
Text verified — A normal typed chat message in the introduction thread. Follow-up nudge after first message, ice-breaker tips, or moderation reminders.
Photo verified — Member sent an image attachment in chat. Photo-sharing etiquette, safety tips, or post-upload questionnaires.
Video verified — Member sent a video attachment in chat. Same as photo — often paired with moderation or safety copy.
Break The Ice verified — System posted a break-the-ice prompt in the match chat. Encourage reply after an automated ice-breaker appears.
Break The Ice Response verified — Member answered a break-the-ice prompt (response message type). Thank-you or next-step content after they engage with the prompt.
Daily Mood Request verified — Daily mood check-in widget appeared in chat. Remind members to complete mood updates when the widget is still open.
Phone Share Allowed verified — Woman (or initiator side) completed the share-phone workflow and posted her number chip in chat. Chat Event → message to the partner who received the share. Chat Event Sender → confirmation or safety copy to the member who shared. See share phone chat chips.
Phone Share Request verified — Man (request side) completed the request step and posted the request chip in chat. Nudge the partner to share her number, or ack copy to the requester via Chat Event Sender.

Pairing tip: For share-phone, many brands configure Chat Event on the partner (recipient) and Chat Event Sender on the member who took the action — same pattern as Intro Update Initiator vs Responder.

Call Event parameters

When the trigger is Call Event, pick one voice/video parameter per template row.

Parameter (Admin label)Plain meaning
Missed Voice Call verified — Partner attempted a voice call that was not answered in time.
Missed Video Call verified — Partner attempted a video call that was not answered in time.
Partner Is Calling verified — Incoming call notification while the partner is ringing.
Active Call verified — A voice or video call is in progress between the matched pair.

Confirm your brand enables in-chat calling before wiring these templates — some brands disable voice/video in the member app.

Reminder parameters

Recurring communications with trigger Reminder must pick exactly one parameter below. Each parameter matches a daily (or scheduled) job that publishes a Reminder system event for qualifying members.

Where timing is configured: Open Settings → Settings → expand the Reminders category. Each parameter has a matching …Times row (comma-separated offsets in minutes). Click Publish on App Settings after changing values—communication templates do not control reminder schedules.

How multi-step reminders work: Each comma-separated value is one nudge wave. The job tracks how many reminders a member already received and fires the next wave only when the matching time window has passed. The last wave may trigger a stronger action (for example terminating an ignored introduction or snoozing after availability checks).

Parameter (Admin label)When it fires (plain language)App Settings rowTypical member effect
Intro Availability Check verified — An introduction is waiting in Availability check status and the initiator has not yet marked themselves available. Fires on each configured reminder wave until the final wave. Intro Availability Check Times Push/email (and sometimes a Lora line in the introduction thread) nudging the initiator to complete the availability questionnaire. On the last configured wave, the introduction may be terminated and the member may be snoozed if they still have not answered.
Intro Availability Check Answered verified — Same availability-check status, but the initiator has submitted an availability answer and the introduction is still waiting for the next step. Intro Availability Check Answered Times Follow-up nudges after they answered availability but the introduction has not progressed. Uses the same multi-wave pattern; final wave may terminate and snooze.
Introduction Waiting verified — A suggestion is still Raw (initiator has not responded) or Initiator approved (responder has not responded) and the response deadline has passed the first reminder window. Introduction Waiting Times Reminder to the member who still owes a response on a pending introduction. May insert a Lora reminder line in the introduction chat. Separate from the cron that auto-declines expired suggestions.
DNF Reminder verified — Profile status is Did not finish (partial onboarding) and the account was created within the lookback window defined by your brand’s DNF reminder schedule. DNF Reminder Times (plus related DNF pending rows in the same Reminders category) Re-engagement message encouraging the member to complete mandatory onboarding. Pair with questionnaire comms or deep links into the unfinished batch.

Related App Settings rows (Reminders category)

Setting (param name)What it controls
DNF Reminder TimesComma-separated minute offsets for DNF Reminder waves.
DNF pending after minutesHow long after the last questionnaire activity before a partial onboarding profile moves toward pending promotion (works with DNF status jobs—not the comm parameter itself).
DNF pending lookback hoursHow far back the DNF reminder job looks at account creation time when selecting profiles.
Introduction Waiting TimesReminder waves for Introduction Waiting.
Intro Availability Check TimesReminder waves before final termination for unanswered availability checks.
Intro Availability Check Answered TimesReminder waves after availability was answered but the intro is still stuck.

Prerequisites: Availability-check reminders require the Introduction availability check app feature on your brand. Create one communication template per reminder subtype you need, each with trigger Reminder and the matching parameter, channels set to Active, and optional Pre-Validation to narrow the audience further.

Tip: Introduction status change comms use trigger Intro Update (instant on status change). Reminder comms are for time-based nudges before or after those milestones—use both when you want an immediate message plus follow-up days later.

It's Quiet Here — parameters

Each parameter is a quiet-chat scenario. Pick the one that matches the nudge you want to send. The system classifies conversations daily and fires your template only when the chat matches that scenario.

Who receives the message: For early empty or short-chat scenarios, the member who has not sent the latest message is nudged and may be sent straight to the introduction chat. For most other scenarios, the quieter member is nudged and may see a Lora follow-up questionnaire on the home chat. Snoozed members are skipped.

Parameter (Admin label)What it meansTypical useMember effect
Empty First verified — Matched chat exists but nobody has sent a message yet, and the first idle window has passed. Gentle “say hello” nudge when a match opens chat but stays silent. Push/email to the member who has not spoken; tapping opens the introduction chat.
Empty Second verified — Still no messages, but the chat has been idle longer (second empty window). Stronger follow-up when neither side started the conversation. Same routing as Empty First—a direct link into the introduction chat.
Short First verified — A few messages total (below your brand’s “short chat” message count), and the first short-idle window has passed. Re-engage a chat that started but stalled early. Nudge to the member who has not sent the latest message; opens introduction chat.
Short Second verified — Same short-chat category, second (longer) idle window—or after a snooze period for one side. Second nudge before escalating to Lora help. Same as Short First for the first notification pass.
Single Side verified — One person sent several messages in a row without a reply within the configured gap. When only one side is texting repeatedly. May mark the chat quiet and later start a Lora questionnaire for the partner who has not replied.
Medium First verified — Conversation has a moderate number of messages (between your brand’s short and medium thresholds) and passed the first medium idle window. Mid-stage chats that went quiet. Lora “it's quiet here” questionnaire can start for the less active side.
Medium Second verified — Same medium-chat band, second trigger—often after the other person has been snoozed long enough. Follow-up when medium-length chats cool off. Questionnaire or second nudge depending on timing branch.
Long First verified — Heavier conversation history (at or above your brand’s medium message count) and the first long idle window has passed. Established chats that stopped for days. Lora questionnaire for the quieter member; both sides may receive notifications in sequence.
Long Second verified — Same long-chat band, second trigger—includes snooze checks so a paused member is not spammed. Final long-idle escalation. Second-side questionnaire or notification after snooze rules pass.
Partner Obsessive verified — One partner sent at least N consecutive messages without a reply from the other side, where N is your brand’s How many messages partner write to be obsessive row in App Settings (Mobile App). When one side overwhelms the thread without replies. Flags the chat; may trigger snooze-based follow-up for the overwhelmed partner. There is no separate minutes row for this scenario in the current server build—the time span check reuses the same numeric setting as the message count. Treat the App Settings value as “how many messages in a row” when tuning; confirm with engineering before expecting a distinct minute window.
Contacts Included verified — Phone or contact details were shared in the thread, and the long-idle window applies. Re-engage after numbers were exchanged but chat died. Lora questionnaire flow for one or both members.
Contacts Included 2 verified — Same as Contacts Included, second window—respects snooze so members who paused the app are not nudged too soon. Second nudge after contact exchange. Second questionnaire or notification after snooze threshold.

Tip: Create separate communication templates per parameter if you want different copy for “never messaged” vs “went quiet after 30 messages.” Use Pre-Validation on each template to limit who receives nudges (for example only approved profiles).

Quiet chat timing (brand settings)

How long the system waits before each It's Quiet Here parameter fires is not on the communication template. Timers and message-count thresholds live in Settings under the Mobile App category. Values are stored in minutes (the table may show them as days or hours depending on your brand’s editor).

Where to edit: Open Settings → Settings → expand Mobile App. Use the Description column to find each row below. Click Publish on that settings page after changing values—communications templates do not need a separate publish for timers.

Prerequisites:

  • Enable the It's quiet here row in Settings → App Features. Without it, the daily quiet-chat job does not run and no It's Quiet Here templates fire.
  • Create one communication template per quiet scenario you want to message (see parameter catalog), each with trigger Its Quiet Here and the matching parameter.

How classification works (plain language): Once per day the system scans introduction chats that have been idle at least the minimal quiet interval. It counts recent messages from each side, checks whether contact details were shared, and applies the timers below. The first matching scenario sets the chat’s quiet type and fires your communication for that parameter.

Setting group (plain language)What it controlsExample values (one production brand)
Empty chat — first / second window Minutes of silence before Empty First and Empty Second (zero messages in the thread). 1 day, then 3 days
Short chat — message count Upper bound for the “short” band: if the lighter side has fewer than this many messages, short-chat timers apply. 5 messages
Short chat — idle windows Three timers: first short nudge, second short nudge, and follow-up after a member chose “I’m busy” / snoozed (Short Second, Single Side, Partner Obsessive snooze checks). 1 day, 3 days, 2 days
Medium chat — message count Upper bound for the “medium” band (above short, below long). 30 messages
Medium / long idle windows First and second timers for Medium and Long scenarios (and contact-included variants). Second timers often wait until a snoozed member has been paused long enough. 3 days / 2 days for medium; 4 days / 3 days for long (example brand)
Partner obsessive (message count) How many consecutive messages from one side (without a reply) before Partner Obsessive applies. This is the only App Settings row the quiet-chat job reads for obsessive detection today. 7 messages (example brand)
Single side chat minutes (if present) Not used by the quiet-chat classifier in the current server build—Single Side instead uses the Short chat — first reminder timer for the gap between consecutive messages from the same sender. May appear on older brands; safe to ignore unless engineering re-wires it.
Minimum quiet interval Floor before any chat is even considered for quiet classification (all scenarios). 60 minutes (example brand)

Example values are from a live brand configuration (June 2026) and will differ on your hostname. Always test on staging after changing timers—shorter windows increase nudge volume.

For the exact Description text your operators see in Admin—and which row drives which communication parameter—see App Settings labels.

App Settings labels (Mobile App)

Each row below is one line in Settings → Mobile App. The Description column is copied from live brand data (June 2026); your brand may use slightly different wording, but the param name pattern is the same across brands.

Description (Admin UI)Value typeIt's Quiet Here parameterWhat the number does
Minimal amount of minutes after last message (From all scenarios) Minutes All scenarios (gate) verified — A chat must be idle at least this long before the daily quiet scan includes it. Lower = more chats evaluated sooner.
Amount of minutes after last message for first reminder (Empty chat - 0 Messages) Minutes Empty First verified — No messages yet; first idle window elapsed.
Amount of minutes after last message for second reminder (Empty chat 0) Minutes Empty Second verified — Still no messages; second (longer) idle window.
Amount of minimum messages to define medium chat Messages (count) Short vs medium band verified — If the lighter side has fewer than this many messages in the scan window, the chat uses short-chat timers (Short First / Short Second / Single Side). Admin label says “medium” but this row is the short-band ceiling (often 5 on production brands).
Amount of minutes after last message for first reminder (Short chat 0-5) Minutes Short First; also Single Side gap verified — First short-idle nudge. Also used as the maximum gap between consecutive messages from the same sender before Single Side applies.
Amount of minutes after last message for second reminder (Short chat 0-5) Minutes Short Second verified — Second short-idle nudge when the first window did not re-engage the chat.
Amount of minutes after user choose Im busy (Short chat 0-5) Minutes Short Second, Single Side, Partner Obsessive (snooze) verified — After a member snoozes or taps “I’m busy”, the system waits this many minutes before a second nudge or obsessive follow-up.
Amount of minimum messages to define long chat Messages (count) Medium vs long band verified — When the lighter side has at least the short-band count but fewer than this count, medium timers apply (Medium First / Medium Second). At or above this count, long timers apply.
Amount of minutes after last message for reminder (Medium chat 5-30) Minutes Medium First verified — First idle window for medium-length conversations.
Amount of minutes after user choose Im busy (Medium chat 5-30) Minutes Medium Second verified — Second medium-idle nudge after snooze threshold.
Amount of minutes after last message for reminder (Long chat 30+) Minutes Long First; Contacts Included verified — First long-idle window (heavy message history) or first contact-shared idle window.
Amount of minutes after user choose Im busy (Long chat 30+) Minutes Long Second; Contacts Included 2 verified — Second long-idle or contact-shared nudge; respects snooze so paused members are not spammed.
How many messages partner write to be obsessive Messages (count) Partner Obsessive verified — One side sent at least this many messages in a row without the other replying (within the time span the job evaluates).
How much time partner write to be obsessive Minutes Partner Obsessive (time window) TBD — Listed in App Settings as a separate row below the message-count row. June 2026 server trace may not read this timer yet; confirm with engineering before tuning.

Stale row on some brands: Amount of minutes after last message for reminder (Only one side write) may appear in Mobile App settings but is not used by the quiet-chat job—Single Side follows the first short-chat timer instead. Ignore that row or ask engineering to remove it.

Tip for operators: Search the Mobile App list for “chat” or “reminder” to jump to these rows. Pair timer changes with a staging test: shorten windows only when you intentionally want more It's Quiet Here communications.

Related App Features row: In App Features, enable It's quiet here so the daily job runs. Chat must also be enabled for members to receive introduction messages.

Matchmaker email slots (EM0–EM26)

Recurring communications with trigger MM Emails must pick exactly one slot. Each slot corresponds to one automated email the matchmaker service sends to the assigned matchmaker (or staff user on some account events).

How slots are numbered: The Admin picker lists EM0 through EM26 (27 rows). The matchmaker email service maps EM1–EM5 and EM7–EM26 to automated senders. EM0 and EM6 appear in the picker but have no sender mapping in the current server build—templates bound to those slots never fire until engineering adds a mapping. Do not use EM0/EM6 for live shidduch workflows.

SlotWhen it fires (plain language)Notes
EM0Not wired — Admin picker only; no automated sender in current server code.Reserved placeholder—use EM1+ for live templates.
EM1verified — Introduction reaches Matched, or reassigned to a new matchmaker after a decline.Often includes approve/decline links to the shidduch request.
EM2verified — Introduction moves to MM Available.Matchmaker can take the case.
EM3verified — Status MM Taking On.Matchmaker accepted work on the introduction.
EM4verified — Status MM Connected.Coordinator connected both sides.
EM5verified — Status MM Recorded.Call or session recorded in workflow.
EM6Not wired — Admin picker only; skipped in server mapping (EM5 → EM7).Gap slot—use EM7 for Engaged milestone emails.
EM7verified — Status Engaged.Major milestone—may also drive BO admin update notifications.
EM8verified — Status Ended.Introduction closed.
EM9verified — Matchmaker declined while introduction was still Matched.Decline path (not SLA timeout).
EM10verified — Matchmaker declined while introduction was MM Available.Decline after matchmaker had availability.
EM11verified — Introduction timed out on matchmaker SLA (automatic decline).Distinct from manual decline emails.
EM12verified — Reminder: matchmaker has not responded while status is MM Taking On.From daily reminder job; may pair with Reminder comms to members.
EM13verified — Matchmaker marked busy / unavailable.End-user “matchmaker unavailable” comm may fire in parallel.
EM14verified — Scheduled reminder to a busy matchmaker (revive cron).Nudges coordinator to return.
EM15verified — Matchmaker returns from busy to available.Revived availability.
EM16verified — Member snoozed/paused on an active introduction (matchmaker event).Coordinator visibility.
EM17verified — Member requested snooze or similar change through matchmaker workflow.Includes user-request paths.
EM18verified — New matchmaker profile registered.Onboarding email to coordinator.
EM19verified — Matchmaker approved in Admin.Account activated.
EM20verified — Matchmaker blocked in Admin.Account suspended.
EM21verified — Introduction moves to On Hold.Paused shidduch.
EM22verified — Reminder while status is On Hold.SLA reminder job.
EM23verified — Reminder while status is MM Connected.SLA reminder job.
EM24verified — Matchmaker password reset initiated from Admin.Staff account email.
EM25verified — Member requested unmatch through matchmaker workflow.Coordinator alert.
EM26verified — Introduction moves to MM Timeout.Matchmaker missed deadline state.

Status names above match the introduction status labels your brand shows in Admin. Template bodies use the email layout you configure on the Email channel for that communication row.

End-user matchmaker emails

Member-facing templates for brands with assigned matchmakers.

Parameter (Admin label)When it firesWhat the member sees
No MM Assigned verified — No matchmaker could be assigned after declines or queue exhaustion on an introduction. Email/push explaining that no coordinator is available; copy is whatever you configure on this template.
MM Unavailable verified — The member’s assigned matchmaker switched to busy / unavailable status. Reassurance or next-step instructions while the coordinator is away. Often paired with matchmaker slot EM13.

Editing parameters

How the Param column and edit dialog work.

On recurring templates, parameters appear as chips in the communication header. Click a chip or the edit icon to open Edit Event Parameters.

ControlWhat to doEffect
Add Parameter Adds another independent parameter group. The template runs when any complete parameter group matches the incoming event (OR across groups).
Add Level (within a group) Adds another dropdown inside the same parameter. Values are stored joined with hyphens (level1-level2). The processor tries the most specific combination first, then falls back to shorter prefixes when matching.
Level dropdowns Pick from the list for that event, or type a custom value if your brand uses legacy ids. Must all be filled before Save is enabled.
Profile status events Uses the profile status picker instead of a free-text list. Same statuses as elsewhere in Admin.

On one-time templates, the header shows a profile status multi-select instead of the parameter dialog. When you Send by profile IDs, only listed members who are also in those statuses receive the send (others are filtered out silently).

BO Admin Update: When your brand uses custom Admin channels, extra parameter values may appear in the level dropdown beyond the defaults below — pick the channel-specific value your integration team documented.

Secondary trigger parameters

Parameter pickers for events that are not chat, intro status, or quiet-chat — one parameter per template row unless noted.

Partner Events

ParameterPlain meaning
Partner became irrelevantThe member’s current match link is no longer valid for matching (partner dropped off or status changed).
Partner deletedThe partner profile was removed or deactivated.
Partner started snoozingThe partner paused matching / chat availability.
Partner stopped snoozingThe partner resumed from snooze.

Lora Message

ParameterPlain meaning
New questionnaireLora assigned a new questionnaire thread to the member.
Image rejectedA photo the member submitted was rejected by moderation.

BO Socket Update

Not member-visible — refreshes open Admin browser sessions.

ParameterPlain meaning
New notificationStaff notification bell should refresh.
Dashboard updateDashboard widgets should reload counts.
Profile importA bulk profile import job finished.
AI chat messageNew backoffice AI chat activity for the signed-in admin.

System

ParameterPlain meaning
Verify parent email / Reminder parent email / Linked parentParent-account email and linking flows.
Verify email / Verify phoneAccount verification messages.
Comm delayed executionInternal — fires when a scheduled delayed send becomes due (not for manual template setup).

BO Admin Update

ParameterPlain meaning
New institutionA new institution record was created in Admin.
New engagementAn introduction reached engaged status.

Matchmaker Status Changed

Pick the matchmaker profile status value (available, pending, blocked, etc.) that should trigger this template. Options match the matchmaker status list on SME profiles.

Questionnaire Answer Comm

No header parameters — link the communication id on the answer row in View Question (answer settings → communication picker). The template’s trigger event must be Questionnaire Answer Comm.

Chat channel sequences

How the Chat channel delivers ordered messages when a communication fires.

On a communication template, the Chat channel is a sequence of rows—not a single body field. Each row has a type and optional settings:

Row typeWhat you configureMember effect
Text Message copy. Plain Lora line in the member's home or context chat when the comm sends.
Question Pick a question from the Other Questions pool. Member must answer before the sequence continues (same widgets as in questionnaires).
Questionnaire header Link to another published questionnaire by name. Inserts that questionnaire's steps when pre-validation on the row passes.
No duplicate (flag) When enabled on a row. Skips that row if the member already received the same content recently—useful for repeat triggers.

verified — Chat rows send only when the Chat channel status is Active/Published and the member passes Pre-Validation. Other channels on the same template are independent—push may send even when chat is draft.

Content step types for questionnaire rows: Content step types. Question pool type: Other Questions.