Skip to main content
Plan a funnel that helps a visitor understand your offer, book a sales call, and prepare for the conversation. This example uses the Wireframe beta skill to draft each page in Agent chat.
Beta: Generate one page at a time. Each result is a saved wireframe. Connecting the pages, calendar, and follow-up happens separately in Build. Use Agent chat on desktop; if /wireframe is missing, contact Support to check availability.

​
The original Olympus example

This preview comes from the saved Olympus · Approved page wireframe reference, created as a visual reference in September 2026. It keeps the original sales-page copy in place and uses outlined placeholders to describe the visuals. The full reference includes the opening headline, proof, the problem and solution, product explanations, pricing, and calls to action. Use it to see how written copy and visual briefs fit together.
This is a historical design example. Its prices, results, guarantees, and product claims are reference copy, not current product documentation or evidence to reuse for your business. It is not an output generated by the current beta skill.
Original Olympus sales-page wireframe showing its headline, calls to action, and outlined visual placeholders.

The opening of the original Olympus sales-page wireframe, captured from the saved HTML.

View the full original page to inspect the section order, copy, and asset briefs. The preview is a static image; its controls do not accept bookings.

​
Recreate an existing page

To wireframe another site’s page, select /wireframe and send its exact public URL:
The agent captures that page’s content and desktop/mobile views through Context.dev. You do not need to choose your own offer or audience. The Olympus example above illustrates the wireframe presentation; its text does not replace the page you supplied.

​
Plan a new funnel

Before starting, choose your offer and audience. Decide what the call is for and gather any approved proof you want to include. Leave unavailable testimonials, prices, or guarantees as placeholders.

​
Draft the pages in chat

1

Create the sales page

Type /wireframe, select Wireframe, and send this brief after adapting it to your offer:
Answer any questions and approve the action if prompted. Review the completed page before continuing.
2

Draft the booking page

Select /wireframe again and request a separate page:
The calendar placeholder describes the required connection. You will configure the working calendar when you finish the funnel.
3

Draft the confirmation page

Select /wireframe and send:
Check that the copy matches what your team will actually send and discuss. Appointment details remain placeholders until you connect the booking flow.

​
Refine the result

Select a copy field to edit it and click Save, or ask for a scoped revision:
Each save creates a new version. When you are ready to review with your team, use Download HTML or Print / Save as PDF on each saved page.

​
Finish the funnel in Build

Start with the sales-page version you want to use:
After any required approval, open the draft in Build. Use the booking and confirmation wireframes as references for the remaining funnel steps. The beta handoff creates a new draft from one page; it does not automatically assemble these three artifacts into a connected funnel. Before publishing:
  • Add the booking and confirmation steps and connect the sales-page CTA to booking.
  • Configure the calendar and its confirmation destination.
  • Replace visual placeholders and confirm any appointment details, links, and follow-up messages.
  • Preview the complete journey and verify that a test booking reaches the intended confirmation page.
Publish through the normal Build workflow after you have checked the connections.