Forms, booking and payments on your website: what a marketing platform covers and what it does not

By Ranjit Bhinge, founder of Blur Studio · Updated · 9 min read

Short answer: On most marketing website platforms, forms are built in, booking comes from a connected scheduling tool, and payments come from a separate payment or store service. A marketing platform here means a site builder made to bring in leads, not to run a shop or a customer portal. Ploy, a software subscription that builds and hosts a business website through an AI chat agent, follows this pattern: native forms, a Calendly (scheduling tool) connection for booking, and no checkout of its own.

Ranjit Bhinge

You want a site where a customer can ask a question, book a time and maybe pay a deposit. Before you pick a platform, find out which of those three it does itself.

I'm Ranjit, and I run Blur Studio: 15+ years building software, 120 apps taken live, and clients who have gone on to raise $10M+. I build AI systems and processes that help businesses do a lot more with a lot less time. I also work differently from most of what else is out there, more on that further down this page. Say hello.

Plan for three separate jobs. A form collects a request and sends it to a person. Booking lets a customer pick a time that is free on your calendar. A payment takes money safely. Most lead-focused platforms do the first on their own and rely on a connected tool for the other two. That is fine, as long as you know it before you build. This guide shows what is normally built in, what is normally connected, how to test each piece, and when a custom app is the better answer.

I use Ploy as the worked example because its docs are specific about these limits. The method works for any platform, and I name where another approach is better.

This page may contain affiliate links from which Blur Studio earns commissions.

Built in, connected or custom: a decision table

JobUsually built inUsually connectedNeeds custom work
Contact or quote formYes: fields, a submissions inbox, an email noticeForwarding to a CRM (customer record tool) or spreadsheetMulti-step quotes with price rules, file checks or approvals
Newsletter sign-upOften the formThe email tool, such as Mailchimp (an email marketing service)Rarely
Booking a timeSometimes a basic versionA scheduling tool embedded or linkedStaff rotas, resources, deposits tied to slots, multiple locations
Taking payment or a depositRarelyA hosted payment page or store serviceSubscriptions, invoicing logic, balances, customer logins
Selling productsRarelyA store service with its own cart and checkoutComplex catalogs, wholesale pricing, inventory sync

Always read the vendor's page for your plan, because "built in" often means "on a higher plan". For example, Webflow, a website builder, shows 50 form submissions on its free Starter plan and unlimited on its $15 a month Basic plan billed yearly, as of November 2026. A cap like that matters if a campaign sends you hundreds of leads.

Forms: what to set up and what to test

A good lead form is short. Ask only for what you need to reply: name, a way to reach them, and the one detail that sets the next step, such as the job type or postcode. Every extra field loses some people.

What Ploy's forms do, per its docs

  • Forms built into a Ploy site capture submissions automatically. You review them under Sites, then Dashboard, then Submissions, and add notification email addresses with the Notifications button.
  • If the form has a field for the submitter's own email (named Email, Email address, Your email or Work email), the notification uses it as the reply-to address, so you can reply directly.
  • Built-in forms send text fields. Each submission can be up to 128 KB. Built-in submissions have no file fields. To accept files, the site saves the form to a database table with a file column, and those rows appear in the table, not in Submissions or the notification email. Uploads work only once the site is published.
  • Every submission stays in Ploy, and the AI agent can also send a copy to another tool, such as Clay (a sales data tool), keeping the form working if that tool is down. Ploy's docs list HubSpot (a CRM), Attio (another CRM), Mailchimp and Pipedrive (a sales pipeline tool) connections elsewhere, on the plans noted on its integrations page. Check that page for yours.
  • You can test a form before it goes live. Submissions from the editor preview are saved and emailed just like live ones.
  • Ploy's database docs say public forms that accept files should have spam protection and tell you to ask the agent to add it. So treat spam protection as something you must request and check, not an assumed default.

For spam fixes that work on any platform, read how to stop spam on your contact form. For a form that collects what a quote needs, see how to make a quote request form that sends details to your team, and for photos or documents, how to let customers upload photos on a request form.

Why form emails go missing

Many missed leads are email problems, not form problems. Google's Gmail sender rules, in force since February 2024, require every sender to set up SPF or DKIM authentication (DNS records that prove an email really came from your domain), and keep reported spam rates under 0.30 percent. Senders of more than 5,000 messages a day to Gmail also need DMARC and one-click unsubscribe on marketing mail. A small form sends far fewer than that, but the platform's notification mail still has to arrive. Test it. If your notice lands in spam, add the sender to your safe list, send to a business address on your own domain, and keep a second copy of every submission in a dashboard or spreadsheet. Never let email be the only place a lead exists.

Privacy and accessibility on forms

If you collect personal data, tell people what you will do with it and link your privacy policy next to the submit button. Rules differ by country, so check local law and the regulator's current page. See cookie banners and consent for marketing sites. Label every field, make the form usable with a keyboard, and keep error messages clear. See website accessibility basics. Do not send marketing emails to people just because they filled in a contact form, unless your local rules allow it. See cold email and outreach laws.

Booking: connect a scheduling tool

Booking needs two things a plain form lacks: it must know when you are free, and it must stop two people booking the same slot. That is why platforms connect a scheduling tool instead of building one. Calendly is a scheduling service that lets people pick a free time on your calendar, and Cal.com is an open-source scheduling service that does the same. Ploy's integrations page lists Calendly (managing event types and scheduled meetings) on its Starter plan and above. Ploy's docs describe no built-in booking engine, so plan to embed or link a scheduling tool. Check the vendor page for the exact setup on your plan.

Rules that make booking convert:

  • Offer one or two clear event types, such as a 15-minute call and an on-site visit, not ten.
  • Put the booking link where the decision happens: the top of the service page and right after the form's thank-you message.
  • Connect it to your real calendar so busy times are blocked.
  • Send a confirmation and a reminder. Ask one qualifying question on the booking form.

The shorter the gap between the enquiry and the call, the better. See a speed to lead system for a small service business and how to send a booking link right after a customer calls.

Payments: keep card details off your site

Do not try to build payment handling yourself. Use a hosted payment page or a store service where the provider handles card data. Stripe is an online payment processor, Square is a payments and point-of-sale company, and Shopify is an online store platform. Each of these has its own fees and terms, so check the vendor page before you decide.

On Ploy, the documents are explicit. Ploy's own comparison with WordPress says it has no storefront or checkout and is built for marketing sites. Its Stripe and Square integrations are listed as read-only (Ploy can read payments, customers, subscriptions, orders and a catalog), and they sit on Pro and above. Shopify can run the store: Ploy hosts the pages and Shopify keeps products, inventory, payments, shipping and orders, with either links to your Shopify store or a Shopify cart on a Ploy page. Ploy's launch checklist says it is optimised for marketing sites, that transactional flows typically live on a separate subdomain or third-party storefront, and that it can proxy (forward) paths such as /shop or /checkout to your existing commerce platform. So if "a deposit button on the page" is a must, plan for a payment link from your payment provider, or a Shopify cart, and test the full path.

When you need a custom app

Connected tools break down when your process has rules of its own. Consider custom software if you need any of these:

  • A quote that is calculated from many options, with approvals before it is sent.
  • Bookings that depend on staff skills, travel time or equipment.
  • Customer logins to see jobs, documents or invoices.
  • Two-way sync between the site, your CRM and your accounting, with no copying by hand.
  • An AI agent that answers visitors using your own pricing and policies.

Read how to connect your website to a CRM, payment or booking tool before you decide, because a few well-chosen connections often solve it without a custom build.

Test plan with pass and fail rules

  1. Form to inbox. Submit the form from a phone and from a computer. Pass: the notice reaches your real inbox within a few minutes, with correct reply-to. Fail: it is in spam or missing.
  2. Form to record. Pass: the entry is in the platform's inbox and in your CRM or sheet. Fail: it only exists in email.
  3. Spam. Submit 3 junk entries with obvious spam text. Pass: spam protection blocks or flags them. Fail: all arrive.
  4. Booking. Book a slot, then try to book the same slot again. Pass: the second attempt is refused, and the calendar and confirmation email both show the first booking.
  5. Payment. Run one test payment in the provider's test mode, then one real small payment you refund. Pass: receipt arrives, the money shows in the provider, and your records match.
  6. Mobile. Complete all three on a phone. Fail: any step needs zooming or a second tab.
  7. Failure. Turn off the connected tool briefly. Pass: the form still saves the lead.

A worked example with made-up numbers

These numbers are invented to show the method. A made-up mobile dog groomer wants a request form, a booking link and a $20 deposit. The owner picks a platform with native forms, adds a scheduling tool for a 30-minute consult and uses a payment link from a payment provider for the deposit. On test day, the form works, the notice goes to spam, and the booking tool does not block the groomer's lunch break. She adds the sender to her safe list, copies each submission to a spreadsheet, and connects the real calendar. After the fixes, all seven tests pass. Total cost is the platform plan plus the scheduling and payment fees, which she checks on each vendor's page. No result is promised: the point is that three small tools did three jobs, and each had one test that caught a leak.

Who should skip what

  • Skip a platform with no checkout, Ploy included, if selling online is your main business. Use a store platform and add marketing pages around it.
  • Skip embedded booking if you take bookings by phone only and have few customers. A form with a call-back promise is simpler.
  • Skip forms-only setups if you promise same-day replies and have nobody watching the inbox. Add a text alert or call routing first.
  • Skip Ploy for this job if you want booking and payments inside one system with no connected tools. A store or booking platform may fit better.

How I'd approach this

I would write down the exact customer path first: question, form, reply, booking, payment. Then I would pick the lightest tool for each step and test the whole path with real devices. If your path is a marketing site with a form and a booking link, Ploy's Free plan lets you try its forms and agent without a card, but a custom domain needs a paid plan, so check the current plans. If the path has rules of its own, Blur Studio builds the custom version: AI agents that use your business knowledge, connections to your CRM and calendar, a half-built flow finished, and ongoing care. See what Blur Studio builds for business.

First-week plan:

  1. Day 1: write the customer path in five steps and mark which tool owns each step.
  2. Day 2: build or fix the form with five fields or fewer, and set two notification addresses.
  3. Day 3: connect the booking tool to your real calendar and place the link after the form.
  4. Day 4: add the payment link or store cart and run a refunded real payment.
  5. Day 5: run the seven tests above and fix every fail before you send traffic.

Decision rule: if any step needs copying data by hand more than a few times a week, connect it. If the connection needs rules your tools cannot express, ask about custom work.

Related guide: a website for consultants and coaches that books calls.

You may also want event and venue landing pages.

Questions people ask

Can a marketing website take bookings?

Yes, usually by embedding or linking a scheduling tool such as Calendly or Cal.com. Few lead-focused platforms have a full booking engine of their own. Check the vendor's page for your plan. For the wider setup see connecting a website to a booking tool.

Does Ploy have built-in booking?

Its docs do not describe a native booking engine. Their integrations list includes Calendly, on Starter and above. Check Ploy's integrations page for current plan limits.

Can I accept payments on a Ploy site?

Ploy has no storefront or checkout of its own, per its comparison with WordPress. You can add a Shopify cart or send people to a payment link. Its Stripe and Square integrations are read-only. See Ploy integrations.

Where do my form submissions go?

On Ploy, they are saved in the site's Submissions tab and can be emailed to the addresses you add, and the agent can send a copy to another tool. On any platform, keep a second copy outside email.

Why am I not receiving contact form emails?

Common causes are spam filtering, a wrong notification address, and missing sender authentication. Send a test, check spam, and keep a copy of each submission in a dashboard. See stopping form spam.

Can a form accept file uploads?

Often only with extra setup. Ploy's built-in submissions are text only, and file uploads go to a database table once the site is published. Add spam protection for any public upload. See photo uploads on a request form.

Do I need a cookie banner for a contact form?

It depends on the tracking on the page and where your visitors are. Check local law and the regulator's current page. See cookie banners and consent.

When should I build a custom booking or quote tool?

When your rules go beyond a calendar and a form, such as staff skills, calculated quotes, approvals or customer logins. Blur Studio builds these; see what it includes.

More in this topic: Websites: visitors, leads, hosting and AI search for owners (9 guides) →

Sources

Ready for the next step?

A 30 minute call. If you do not need me, I will tell you.

Ranjit Bhinge You talk to me, Ranjit. I reply within a few hours.

Not sure what you need? Tell me what is going on. I will point you the right way, even if it is not me.

Blur Studio · 30 minute call

Book a 30 minute call

You talk to me, Ranjit. If you do not need me, I will tell you.

  • We talk about your business and what is going on.
  • You leave with a clear next step, even if it is not me.
  • I reply to every message within a few hours.
Loading the calendar…