Web flow vs message flow

SMOC has one Studio and Console, but two native conversation runtimes.

Web flow

Runs in-page: chat or card experiences on your site, ads, iframe embeds, or SMOC landing pages (go2.smoc.ai).
Studio tabs: Compose → Design → Style → Settings.
Best for inbound traffic, landing pages, and interactive ads.
Outcomes: interactions, smart clicks, smart identified leads from web capture.

Message flow (LinkedIn)

Runs async LinkedIn outreach: profile view, connect, DM/InMail, waits, suggested replies.
Studio tabs: Compose → Design → Targeting (no Style tab—the UI is LinkedIn’s inbox).
Best for outbound B2B when you have sender accounts and prospect lists.
Human-in-the-loop via Console Inbox when the flow pauses on Suggested Replies.

Analytics (sessions & users)

	Web flow	LinkedIn message flow
Flow Sessions	Visitor opens / begins the flow	Successful profile view, connection send, DM, or InMail
Unique Users	Distinct visitors in the range	Distinct contacts with that activity
Does not count	—	Enrollment alone, or waits before the first successful LinkedIn action

Message-flow Breakdown (on a single agent or rolled up on the company Agents Breakdown tab) also shows outbound actions for the selected date range, a planned actions table for the next seven days, and an outreach funnel (enrolled, connects, and so on). Outbound actions follow your date filter; the funnel and planned schedule do not. Details: Reading Agents analytics in Console.

What is not a native channel (yet)

Email, WhatsApp, and SMS are useful to distribute links into a web flow (or notify people), but they are not peer conversation runtimes alongside web and LinkedIn today.

Choosing quickly

Situation	Prefer
Homepage / LP / paid social landing	Web flow
Account-based outbound on LinkedIn	Message flow
Need brand theme & iframe	Web flow
Need connect → DM sequences	Message flow