What HoneyBook gives you
HoneyBook has two customer-facing pieces that belong on a website. The contact form takes an enquiry and creates a project in HoneyBook with the client's details, so the proposal, contract, invoice and payment all continue from there. The scheduler lets a client pick a slot from your availability for a consultation, a portrait session or a tasting, with payment taken at booking where you set it. Both are available as hosted pages on HoneyBook's domain and as embed code for your own site. The client portal, where couples sign, pay and answer questionnaires, stays on HoneyBook.
The performance question is where the embeds go. A photographer's site lives or dies on how fast the portfolio loads, and a third-party script on every page works against that. The answer: on the pages where the client wants them, never on the pages where they are looking at the work.
The rule
Nothing from HoneyBook loads until the visitor arrives at a page whose purpose is to enquire or book. Portfolio, Packages and prices, About and Reviews are for looking and ranking; they link to the two pages that carry the embeds.
Page 1: Check my date
The contact form embed on its own page, with a one-line promise ("We reply within one working day") and nothing heavy around it. Configure the form in HoneyBook with the fields an events enquiry needs: date, venue, guest count, budget range, and a message. HoneyBook's form fields are set in your account, so the questions match what you would ask by email.
Package cards and portfolio galleries link here. Where HoneyBook's form does not support pre-filling the package, put the package name in the button text of the link and a line above the form ("Enquiring about the Full day package? Mention it below"), or use a site-built form that posts the lead to HoneyBook through its integrations and carries the package in a hidden field.
Reserve the embed's height in CSS so the page does not shift when the form appears, and preconnect to HoneyBook's domain in the page head so the script starts loading a moment earlier.
Page 2: Book a session
The scheduler embed on its own page, for the fixed-price work: engagement and portrait sessions for a wedding or portrait photographer, consultations for a planner, tastings for a caterer. Each session type is set up in HoneyBook with its duration, price and the calendar it books into, and the page links to the specific session type where HoneyBook provides a link per type, so a client who tapped "Book an engagement session" sees that session's slots, not a menu.
If some work is quoted and some is booked, keep the routes visibly separate: Check my date for the event, Book a session for the rest.
If the embed is heavy or does not fit
HoneyBook's embeds are reasonable, but they load their own script and styles, and inside Instagram's in-app browser they occasionally misbehave. Two fallbacks:
- Link out. The Check my date and Book buttons open the hosted HoneyBook page in the same tab, with a link back to your site on your thank-you settings. Nothing third-party loads on your site at all.
- A site-built form. Six to eight fields in your own style, posting to HoneyBook through Zapier or a similar integration so the project is still created. Full control of speed and design; the lead still lands in HoneyBook.
We use the embed where it behaves and the site-built form where the design or speed matters more.
Configure HoneyBook first
- Contact form fields matching your date check.
- Session types in the scheduler with durations, prices and calendars.
- Proposal, contract and invoice templates matching the packages on your site.
- Automations: enquiry acknowledgement, follow-up if no reply, balance reminders.
- Notifications to your phone for new enquiries and bookings.
Submit a test enquiry and book a test session from a phone before wiring the site.
Testing on phones
Safari and Chrome on iOS and Android, and inside Instagram's in-app browser, because that is where couples arrive from. Complete a date check and a session booking in each. Check the project appears in HoneyBook with the fields filled, the notification reaches your phone, and the confirmation email reads in your voice. If the in-app browser fails, link those entry points to the hosted page.
Tracking
date_checkwhen the contact form is submitted,booking_clickwhen a session is booked, each with the package or session type and the page the visitor came from.- HoneyBook's own lead source reporting for enquiries by origin.
- A thank-you page or event after submission so completions register in analytics.
- Monthly: enquiries and session bookings by page, so you know whether the portfolio or the packages page is doing the work.
Common mistakes
- The contact form embedded on every page, slowing the portfolio for the majority who are looking.
- A single form for weddings and portrait sessions.
- The hosted HoneyBook page as the Instagram link with no route back to the portfolio.
- Fields in HoneyBook that do not match the questions you actually ask, so the first reply still has to ask them.
- Nobody watching the HoneyBook notifications during shooting season.
Monthly check
From the home page, the packages page and a gallery, on a phone: tap Check my date and send one; tap Book a session and book one; confirm both arrive and the portfolio page still loads in under two seconds. Embeds update; find out before a client does. This is on the care plan for every HoneyBook site we look after.
Where this sits
HoneyBook is the tool we wire into photography and events websites most often, alongside Studio Ninja, Dubsado, Tave and Light Blue, and this setup, two dedicated pages, deep links from packages and galleries, fallbacks for in-app browsers, and tracking, is the version that keeps the portfolio fast and the enquiries landing as projects. HoneyBook runs the proposal and the deposit; the site gets the couple into it in one tap.