All guides
Using Frontpage 6 min read

How to use Modules

A good-looking site that can't take a lead, a booking, or a payment is just a brochure. Modules give your pages real, working functionality, and you add them the same way you build everything else: by asking.

Most website builders make you bolt on a separate app for every bit of functionality: one tool for forms, another for scheduling, a plugin for payments. Frontpage Modules are built in. You describe the functionality you want and the agent wires up the real, working version: the platform handles the behavior, you own how it looks. Here's what's available and how to use each one.

What a module is

A module is a piece of genuine, full-stack functionality the platform runs for you, surfaced on your page through simple markup the agent writes. The split is clean: the platform handles the behavior (storing submissions, emailing you, taking payment, tracking conversions) and you own the presentation, so a form or a booking widget looks like part of your site, not a third-party embed.

Crucially, none of it is fake. A form really reaches your inbox; a payment button really charges a card. You'll never get a dead placeholder or an "integration coming soon" stub.

The modules you can add

There are six, and each is added just by asking for the thing it does:

  • Forms — contact, quote, and lead forms. Submissions are stored, spam-filtered, emailed to you, and counted as conversions. Ask for "a contact form" or "a request-a-quote form with name, email, and project details."
  • Signups — email capture for a newsletter, waitlist, or launch list. Entries land in a list you own and can export. Ask for "an email signup for my newsletter."
  • Booking — appointment requests you confirm in one click, after which the visitor gets a calendar invite. Ask for "a booking form so people can request a consultation."
  • Call bar — a sticky tap-to-call (and text) bar on mobile, ideal for local businesses. Ask for "a tap-to-call bar with my phone number."
  • Payments — real payment buttons running through your own Stripe, for deposits, one-off charges, or tips. Ask for "a $50 deposit button."
  • Store — a product catalog with a cart and Stripe checkout. Ask for "a shop with these three products."

Adding a module: just ask

You never edit markup or paste a snippet. Describe what you want where you want it and the agent builds it:

  • "Add a contact form to the bottom of the home page."
  • "Put an email signup in the footer with a 'Join the list' button."
  • "Add a booking form to the services page for a free consultation."
  • "Add a tap-to-call bar for mobile using (555) 123-4567."

Because you own the presentation, you can keep refining the look by chatting: "make the form two columns," "move the signup above the footer," "change the button to say Get early access."

Zero-setup vs. connect-once modules

Modules come in two flavors, and the difference is just whether money is involved.

Work immediately

  • Forms
  • Signups
  • Booking
  • Call bar

Need a one-time connection

  • Payments (connect Stripe)
  • Store (connect Stripe)

The first group activates the moment it's added, nothing to configure. Payments and the store need you to connect your own Stripe account once. When you ask for either, the agent builds the whole thing right away, then a prompt appears in your status bar to finish the Stripe connection, which takes a few minutes. The payment elements stay hidden from visitors until that's done, then go live automatically.

Where everything lands

The point of a module is that the results reach you. Form and booking submissions are emailed to you and logged as conversions in your analytics. Signups build an exportable list you own. Payments settle into your Stripe account. You're never logging into a separate dashboard to find your leads.

Change settings by chatting

Want leads to go somewhere specific? Say "send my form submissions to sales@mybusiness.com." Need to update the call bar number or turn a module off? Just ask, and it's done, no settings menu to dig through.


A quick checklist

  • Decide what each page needs to do: collect a lead, book a call, take a payment.
  • Ask for that functionality in plain English, where you want it.
  • Refine the look by chatting, since you own the presentation.
  • For payments or a store, finish the one-time Stripe connection from your status bar.
  • Point your notifications wherever you want leads to land.

New to building here? Start with Getting started with Frontpage, and learn the prompting habits in How to edit your site just by talking.

Frequently asked questions

How do I add a module to my site?

Just ask for the functionality in plain English: 'add a contact form,' 'put a booking calendar on this page,' or 'add a tap-to-call bar for mobile.' The agent writes the working markup for you. You never touch code or configure an integration by hand.

Where do form submissions and signups go?

Straight to you. Form entries are stored, spam-filtered, and emailed to you automatically, and they're tracked as conversions in your analytics. Email signups land in a list you own and can export at any time. You can change the notification email just by asking.

Which modules need setup before they work?

Forms, signups, bookings, and the call bar work the moment they're added, with nothing to connect. Payments and the store need a one-time connection to your own Stripe account. The agent builds everything first, then asks you to finish the Stripe step from your status bar, which takes a few minutes.

Are these real features or just placeholders?

Real. A Frontpage form actually delivers to your inbox, a booking is genuinely confirmable in one click, a payment button charges through your Stripe. The platform never fakes functionality with dead forms or dummy checkouts, so what visitors see is what actually works.

Build it while the idea is fresh.

Describe the site you want and watch Frontpage build it live, in front of you.