Split With Chat Mockup

About this block

Split With Chat Mockup opens with the support experience instead of the product. The copy claims a four minute median reply and the mockup proves the texture: a chat window headed by a named agent with an online chip, a real seeming exchange about a DKIM record, and a closing timestamp line, first reply in 3 minutes, resolved in 11. The conversation is the demo.

The chat content is plain markup using the collection bubble pattern. The exchange must be technically plausible, the DKIM detail is what makes the mockup feel transcribed rather than written. The hero fills the viewport and ships without a header.

When to use

Reach for this block when support quality is the differentiator, products competing against vendors with ticket queues, or services sold on responsiveness. It is the only hero in the group that sells the relationship rather than the software, pair it with chat-style-quotes carefully, two chat motifs on one page need spacing.

A natural flow around it on a Marketing Pro page:

Before

• A navigation header to anchor the page before the hero fills the fold

After

• Stats backing the reply claim with the full numbers
• Testimonials widening from one exchange to many voices

What you can display

One strong use is a support led SaaS differentiation. Other conversations:

• Onboarding chat. A migration question answered mid import for a switching audience.
• Sales chat. An honest pre sales exchange including a this plan is enough for you moment.
• Expert service. A consultancy showing an actual advice exchange as the product.

Tip: include one technical noun in the exchange, DKIM does more credibility work than any adjective in the headline.