THE FUTURE MARKETACADEMY
Your classroomRoom 07 · Tech Lab
School of Data & Tech

Site Systems: bookings, payments and integrations

Step 7 of 8 in Tech Lab

Next in your path: 7.7.3 Full-Stack Basics: servers, databases and deployment

What you'll be able to do
  • Map your customer's path through your site and choose the right tool for each step.
  • Add an online booking page with sensible availability, buffers and a short booking form.
  • Take online payments safely with a hosted payment page, and test them without real money.
  • Write clear prices, refund and cancellation policies, and handle refunds and disputes.
  • Run an email list properly: sign-up, double opt-in, a welcome email and sender authentication.
  • Connect tools with integrations and automations, and keep a list of what is connected.
  • Handle the privacy side of these systems: what you collect, who processes it, how long you keep it and what to do after a breach.
  • Check that your forms, booking pages and checkout work for people with disabilities.

Before this course: Business Websites: design, SEO and forms (course 7.6.2). You should already have a published multi-page site with a contact form, a privacy page, Search Console and Analytics. This course adds the "machinery" behind the site: bookings, payments, email and connections between tools. It does not repeat page design, SEO or the basics of anti-spam rules from courses 7.6 and 7.6.2.

We use Google Calendar appointment schedules, Stripe Payment Links, Google Forms and Sheets, and Zapier as worked examples, because their official help pages describe each step. Wix, Squarespace, WordPress.com and other builders have their own booking, payment and email tools; the ideas are the same, but menu names differ by tool and version. Prices, fees and which countries a tool works in change often: check each tool's own pricing and availability pages before you choose.

This course teaches how these systems work. It is not legal, tax or financial advice. For your own business rules, check your government's official sites and ask a licensed professional when unsure.

Words in this course 65Open the Vocabulary Hall
01

Plan your site system

In simple words

A website with bookings and payments is like a small restaurant. The menu is your site, the reservation book is your booking tool, the till is your payment tool, and the waiter who sends thank-you notes is your email tool. Before you buy equipment, walk through the restaurant as a customer and write down every step.

Key facts
  • A site system is your website plus the tools behind it: bookings, payments, email, spreadsheets and the connections between them.
  • Start with the customer journey: every step a customer takes, from finding you to paying and coming back. For a tutor it might be: read Services, pick a time, pay, get a confirmation, get a reminder, attend, get a receipt, get a follow-up email.
  • For each step, write: which tool does it, what data it collects, who sees that data, and what happens if the step fails.
  • Built-in or connected? Many builders include bookings, payments and email (fewer logins, one bill). Separate tools (for example a calendar, a payment provider and an email tool) can be more flexible but need connecting. Neither is always better; choose by what your journey needs.
  • Hosted pages keep the risky part off your site. A hosted payment page (such as a Stripe Payment Link) or a hosted booking page (such as a Google Calendar booking page) is run by the provider; your site only links to it.
  • Test before you go live. Use each tool's test or sandbox mode, and test with your own email and phone before you tell customers.
  • Own your accounts. Create business tools with a business email address you control, turn on two-step verification, and write down who has access. If a helper builds your system, make sure the accounts are in your name.
  • Keep a simple systems sheet: tool, what it does, account owner, plan and price, what data it holds, renewal date.
  • Fewer tools means fewer things to break, fewer bills and fewer places where personal information is stored.
Journey stepTool (example)Data collectedIf it fails
Choose a timeBooking pageName, email, chosen timeContact form as backup
PayHosted payment pagePayment details (kept by the provider)Invoice by email
ConfirmationBooking tool emailEmail addressCheck the calendar daily
Follow-upEmail toolEmail address, consentSend by hand
Step by step
  1. Write your customer journey as 6 to 10 numbered steps, from "finds my site" to "comes back".
  2. Next to each step, write the tool that will do it (or "by hand" for now).
  3. Add the data each step collects and who can see it.
  4. Circle any step where the customer could get stuck, and write a backup (for example a contact form or an email address).
  5. Make your systems sheet in a spreadsheet with the columns: tool, job, account owner, plan, data held, renewal date.
  6. Check every account in the sheet uses a business email you control and has two-step verification turned on.
  7. Check: someone who does not know your business can read your journey and say which tool handles each step.
LESSON 01Plan your site system
LESSON 01 / ANIMATED LESSON / AI VOICE00:00 / 01:00
Read the video script
[Host] "Before you add bookings or payments, walk through your business as a customer."
[Text on screen: Find → Book → Pay → Confirm → Remind → Follow up] "Write every step. For each one: which tool, what data, and what if it fails."
[Screen: a simple systems sheet with tool, owner, data, renewal] "Keep a systems sheet, so you always know what is connected and who owns it."
[Text on screen: Hosted pages = less risk on your site] "Hosted booking and payment pages keep the sensitive part with the provider."
[Host] "Test everything in test mode, with your own email, before customers see it."
Try it now

Draw the customer journey for your own or a practice business, with at least six steps. Fill in your systems sheet for the tools you plan to use. Mark which steps you will build in this course and which you will keep by hand for now.

ClaudeStuck? Copy a ready-made prompt for Claude

Copy this, open Claude, paste it, and Claude will walk you through the lesson step by step.

For a grown-up: Claude is for adults (18+). Copy this, paste it into Claude, and use the answer to explain the lesson to your child.

I'm learning "Site Systems: bookings, payments and integrations" on The Future Market. Lesson 1: "Plan your site system".

What the lesson teaches:
- A site system is your website plus the tools behind it: bookings, payments, email, spreadsheets and the connections between them.
- Start with the customer journey: every step a customer takes, from finding you to paying and coming back. For a tutor it might be: read Services, pick a time, pay, get a confirmation, get a reminder, attend, get a receipt, get a follow-up email.
- For each step, write: which tool does it, what data it collects, who sees that data, and what happens if the step fails.
- Built-in or connected? Many builders include bookings, payments and email (fewer logins, one bill). Separate tools (for example a calendar, a payment provider and an email tool) can be more flexible but need connecting. Neither is always better; choose by what your journey needs.
- Hosted pages keep the risky part off your site. A hosted payment page (such as a Stripe Payment Link) or a hosted booking page (such as a Google Calendar booking page) is run by the provider; your site only links to it.
- Test before you go live. Use each tool's test or sandbox mode, and test with your own email and phone before you tell customers.
- Own your accounts. Create business tools with a business email address you control, turn on two-step verification, and write down who has access. If a helper builds your system, make sure the accounts are in your name.

The exercise I'm working on:
Draw the customer journey for your own or a practice business, with at least six steps. Fill in your systems sheet for the tools you plan to use. Mark which steps you will build in this course and which you will keep by hand for now.

I'm stuck. Please:
1. Explain the main idea in plain, simple words with one everyday example.
2. Walk me through the exercise one small step at a time. Ask me what I've done so far before giving the next step.
3. Don't just give me the final answer. Help me do it myself, and check my work when I share it.
I'm a parent helping my child (about 8 years old) with a lesson called "Plan your site system" from the course "Site Systems: bookings, payments and integrations".

Here's what the lesson says:
A website with bookings and payments is like a small restaurant. The menu is your site, the reservation book is your booking tool, the till is your payment tool, and the waiter who sends thank-you notes is your email tool. Before you buy equipment, walk through the restaurant as a customer and write down every step.

The activity:
Draw the customer journey for your own or a practice business, with at least six steps. Fill in your systems sheet for the tools you plan to use. Mark which steps you will build in this course and which you will keep by hand for now.

Please explain this so an 8-year-old understands: short sentences, a fun everyday example, and no hard words.
Then give me 3 simple questions I can ask my child to check they understood, and a way to do the activity together, one tiny step at a time.
Open Claude
Sources
My notes
02

Online bookings

This lesson is part of full access: every course and every level for one payment.

03

Online payments with a hosted payment page

This lesson is part of full access: every course and every level for one payment.

04

Prices, refunds and policies customers can trust

This lesson is part of full access: every course and every level for one payment.

05

Email tools that respect people

This lesson is part of full access: every course and every level for one payment.

06

Integrations and automations

This lesson is part of full access: every course and every level for one payment.

07

Privacy for site systems

This lesson is part of full access: every course and every level for one payment.

08

Accessible forms, bookings and checkout

This lesson is part of full access: every course and every level for one payment.

++

Final project

This lesson is part of full access: every course and every level for one payment.

??

Quiz

  1. What should you write next to each step of your customer journey?

  2. Why use a hosted payment page instead of a card form on your own site?

  3. How should you test online payments?

  4. What is buffer time in a booking tool?

  5. What should customers see before they pay?

  6. What is a dispute (chargeback)?

  7. What is double opt-in?

  8. What do SPF, DKIM and DMARC do?

  9. In Zapier, what are a trigger and an action?

  10. What three things should you know for every place personal data is stored?

  11. Name a quick way to test whether a booking form is accessible.

  12. What should you do if an embedded booking or payment tool is not accessible?

EX

Final exam

This lesson is part of full access: every course and every level for one payment.

CE

Certificate

This lesson is part of full access: every course and every level for one payment.