A chat bubble is the right shape when someone is already on your site and you want a fast back-and-forth. A landing page has a different job. It has to leave the offer on screen and ask for one next step.
That is how the SMOC contact page works. The headline stays. The card asks who you are.
Answer, and the next question replaces it. The page does not start over.
That page used to be a one-off. It is now a format you can create.
Chat, card, or message
Console → Create agent asks which kind of agent you want:
- Chat flow — the in-page conversation, on your site or in an embed
- Card flow — the stepped page, for a landing page or a contact form
- Message flow — LinkedIn outreach
Chat and card are both web flows. They use the same graph, the same nodes, and the same analytics. The difference is what the visitor sees.
On a card flow, Compose starts from Contact us form. On a chat flow, the templates are the lead-gen, quiz, and guide flows.
Room around the card
A card in the middle of a blank page is still a form. A landing page needs the argument beside it: who it is for, what happens next.
In Studio, Style → Page turns on text and design above, beside, and below the card. Beside can sit on the left or the right, and that copy is rich text, so it can hold a list or a short proof point. Each region can take a theme color or an image. An image above the card stays inside the area, like a logo. Leave a region off and the card stays centered.
The hosted link ends in /cards and shows those regions. The embed adds iframe_mode=true and shows the card alone, so a short iframe on a contact page stays a card.
When to use it
Use a card flow when the visit is the page: paid traffic to an offer, a contact page, a guided explanation. Use a chat flow when the conversation should sit inside a site the buyer is already reading. Use a message flow when the conversation starts in LinkedIn.
How to set it up: Card flows.
Shipped this month — September 2026 release log.
