Four questions decide how a fitting is booked: what the garment is, how many weeks remain before the wedding, whether the gown has arrived, and what work is needed. A form in GoHighLevel can use those answers to redirect the customer to the right calendar, with the right appointment length, and to send anyone with too little time to a person. The bottom line: a wedding gown and a bridesmaid dress need different appointments, and the calendar should not let a customer pick the wrong one.
What the timelines say
David's Bridal says most brides start alterations two to three months before the wedding, that the first fitting is best 8 to 12 weeks out, that the final fitting falls 1 to 2 weeks before, and that a made to order gown can take 4 to 6 months to arrive. It adds that simple hemming and minor tweaks can often be done within one to two weeks, but rushing may limit options and increase costs. Azazie's guides say most wedding dress alterations take 6 to 10 weeks from first fitting to pickup, with two or three fittings, and that a first fitting runs 1 to 1.5 hours, a second about an hour, and a final 30 to 45 minutes. Its bridesmaid guide says those dresses take 2 to 4 weeks, with a first fitting 4 to 6 weeks out and rush work costing 50 to 100 percent extra.
Those are retailers' figures, and your shop may differ, but the pattern is clear: gown fittings run longer and start earlier, bridesmaid fittings are shorter, and the last few weeks are where scheduling breaks.
The questions and where each answer sends the customer
| Answer | Result |
|---|---|
| Wedding gown, more than 8 weeks out | Redirect to the gown first fitting calendar, 90 minutes |
| Wedding gown, 4 to 8 weeks out | Redirect to the compressed schedule calendar, with a Message explaining fewer fittings |
| Bridesmaid or mother of the bride dress | Redirect to the short fitting calendar, 45 minutes |
| Any garment, fewer than 3 weeks out | Message asking the customer to call, and tag the lead Rush |
| Gown has not arrived yet | Message: book once it arrives, with a reminder option |
Build it in GoHighLevel
- Create the custom fields you will need first, under Settings, then Custom Fields, so the form has fields to map to.
- Go to Sites, then Forms, then Builder, create a new form, and map each question to its custom field.
- Add a garment dropdown, a weeks to the wedding dropdown with ranges (more than 8, 4 to 8, 3 or fewer), a gown arrived question, and a checklist of work needed.
- Create one calendar for each fitting type, with its own appointment length. GoHighLevel also has a Service menu calendar for shops that want customers to choose a service and a staff member.
- Open Conditional Logic and add Redirect rules that send each garment and timing combination to its calendar link. Use a dropdown for the weeks, because calendar fields are not supported in conditional logic.
- Add a Message rule for fewer than 3 weeks and for gowns that have not arrived.
- Add a workflow reminder for the second and final fittings after the first is booked.
- Preview the form and test every rule with real answers, including the ones that should disqualify.
- Build a workflow with the Form Submitted trigger, choose this specific form as the filter, and add the actions for your business: tags, an opportunity, an internal notification, and a reply to the customer.
GoHighLevel's help page on conditional logic says you add rules inside the Form or Survey Builder by clicking Conditional Logic in the top bar and then Add New Condition, and that each rule has an action: Redirect, Message, Disqualify, or Show/Hide. You choose a field, a field state such as is equal to or is empty, and a value. Rules run from the top down, later matches override earlier ones for Show/Hide, and the first match wins for submission actions such as redirects and messages. Text matching ignores case and extra spaces, calendar fields are not yet supported, and the page tells you to preview the form to check each rule. A third party setup guide adds that forms fire the Form Submitted workflow trigger, surveys fire a separate Survey Submitted trigger, and a trigger with no form selected fires for every form in the account.
What the workload looks like
For example, a shop with 40 gowns in a season books 120 fittings. At the lengths above, one gown needs about 2.5 to 3.25 hours of fitting time (1 plus 1 plus 0.5, up to 1.5 plus 1 plus 0.75), so 40 gowns need roughly 100 to 130 hours (40 times 2.5, up to 40 times 3.25). Booking each one into the correct length slot keeps those hours from spilling.
Mistakes to avoid
- One calendar for every garment. Lengths differ.
- Letting last minute requests book online. They need a person and possibly a rush fee.
- Forgetting the shoes and undergarments. Tell customers to bring them to every fitting.
- Booking before the gown arrives. The first fitting depends on it.
How this was handled before
Alteration shops booked by phone, and the person answering asked the same questions each time: what garment, when is the wedding, has it arrived. The answers decided the appointment. A form asks them once, sends the customer to the right calendar, and keeps the phone free for the rush cases that need judgment.
Check before you switch it on
US text messages sent from a standard 10 digit number need A2P 10DLC registration. The HighLevel support portal says registration is required for texts to US recipients from 10 digit long code numbers and that toll free numbers do not require it. HighLevel's opt in guidelines also say a person cannot be forced to agree to text messages in order to submit a form, so keep the consent box optional. One compliance guide separates informational texts, which need documented consent, from marketing texts, which need prior express written consent. Ask your attorney which category your reminders fall into. Brides often share a phone with a planner or a parent, so confirm who should receive reminders. This is general information, not legal advice.
Questions people ask
How many fittings does a wedding gown need?
Azazie says two or three, and David's Bridal describes three, with the final one to two weeks before the wedding.
Can a form send customers to different calendars?
Yes. GoHighLevel's Redirect action can send a person to a link based on an answer, but calendar fields are not supported in the rules, so use a dropdown.
What about rush requests?
David's Bridal says simple work can often be done in one to two weeks but may limit options and cost more. Route these to a person.
Ready to try it yourself? Start a GoHighLevel account here.
You can also see this in action in our GoHighLevel capabilities demo.