Wedding portals such as Hitched and Bridebook send a steady flow of enquiries, but each one arrives as an email that someone has to read, copy and type into the sales system. When the office is busy, that copying is where enquiries wait, details get mistyped and replies go out late.
This guide covers what to capture, how to avoid duplicates, and how to reply when the portal gives you a relay address instead of the couple's email.
Why portal enquiries deserve their own process
A portal enquiry is different from a phone call or a website form. The couple often sends the same enquiry to several venues in one go, so the first useful reply has a real advantage. At the same time, the enquiry comes to you through a third party, in that portal's own email format, and sometimes without a direct email address.
If the team treats these emails like any other message in the shared inbox, three problems tend to appear:
- Delay. The email sits in the inbox until a coordinator has time to create the enquiry record.
- Typing errors. A date copied by hand can be wrong, which leads to a wrong availability answer.
- Lost reporting. If the source is not recorded every time, you cannot tell later which portal brings enquiries that actually book.
What a portal enquiry email usually contains
Most portal emails follow a fixed layout for each portal. You will typically find the couple's name, a wedding date or a rough period, an approximate number of guests, and a short message. Some include a phone number. Some include the couple's own email address; others give you a relay address that forwards your reply through the portal.
Because the layout is consistent, the details can be read in a structured way rather than retyped.
A simple process for every portal enquiry
- Receive all portal emails in one shared mailbox. Do not let enquiries land in personal inboxes, where they disappear when someone is on holiday.
- Capture the core details. Name, email or relay address, phone, date, guest numbers, event type and the portal it came from.
- Check for missing information. If the date or guest count is missing, the first reply should ask for it, and the record should show that it is incomplete.
- Check for duplicates. Couples sometimes enquire through a portal and your website, or send a second portal message a few days later. Add it to the open enquiry rather than creating a second one.
- Assign an owner. Every enquiry needs one named coordinator, or a clear rule for who picks up unassigned ones.
- Reply quickly with something useful. Confirm whether the date looks free, mention the next step (a show round, a call, a brochure) and ask one clear question.
- Record the source. Hitched, Bridebook or another directory, on every enquiry.
Automatic or reviewed?
Some venues are happy for portal enquiries to become leads straight away. Others prefer a coordinator to glance at each one first, for example to remove test messages or supplier pitches. Both work, as long as the choice is made on purpose.
| Approach | Works well when | Watch out for |
|---|---|---|
| Create the lead immediately | The portal sends clean, consistent enquiries and speed matters most | Occasional non-enquiry emails that need closing |
| Review first, then create | A portal sends mixed messages, or details are often incomplete | Someone must check the review list every working day |

Replying through a portal relay address
Some portals do not pass on the couple's email address. Instead, you reply to a relay address and the portal delivers your message to the couple inside its own messaging system. This protects the couple's privacy, but it changes how your email should look.
Portal messaging usually shows plain text. Designed emails with images, columns and buttons can arrive broken or stripped down, and a link hidden behind a button may not survive at all. A few rules help:
- Keep it short. Three or four short paragraphs read better in a portal inbox than a full brochure-style email.
- Write links out in full. Put the name of the link and the web address on its own line, for example "Our wedding brochure:" followed by the address.
- Do not rely on open tracking. Emails through a relay often cannot be tracked, so do not read anything into a "not opened" status.
- Invite the couple to share their own email or phone number. Ask politely, as a convenience for them, not as a condition of replying.
- Keep the thread together. When the couple later writes from their own address, update the contact so future emails go there directly.
What a good first reply contains
Whether you write to a relay address or a direct email, a strong first reply to a portal enquiry usually answers these points:
- Thanks for the enquiry, using the couple's name.
- Whether the date is available, and if not, the nearest free dates on the same day of the week.
- One or two facts that matter for their guest numbers, such as which room suits that size.
- A clear next step: a link to book a show round, or a suggestion for a short call.
- Your name and direct contact details.
Measure what each portal brings
Portal subscriptions cost money, so it is worth knowing which ones produce bookings rather than only enquiries. With the source recorded on every lead, you can compare enquiries, show rounds and confirmed weddings from each portal over a season. Track response time too, because it is the part the team controls directly.
A portal enquiry is only as good as the speed and accuracy of the first reply. Capture it without retyping, check what is missing, and answer with the date and a next step.
Checklist
- All portal emails arrive in one shared mailbox.
- Name, contact, date, guests and source are captured on every enquiry.
- Missing details are flagged and asked for in the first reply.
- Repeat enquiries from the same couple join the existing record.
- Every enquiry has an owner.
- Replies to relay addresses are short, plain and have links written out.
- Source and response time are reviewed at least once a season.
How Staybase handles this
In Staybase Sales & Events, portal enquiries are read from the connected shared mailbox. You tick Hitched and Bridebook in the settings, and you can add other directories by their sender address and a source name. Staybase reads the name, email, phone, date and guest numbers from each portal email and creates the lead, so nobody retypes it.
For each portal you choose whether leads are created straight away or shown on the dashboard first for a coordinator to check, and you set defaults such as the stage, event type, estimated value and title prefix. Missing details become a Check details next action on the lead. If the couple already has an open lead from the last 30 days, the new enquiry is added to it. The original email stays on the timeline, the lead follows your default coordinator and automations, and the source can be used as an automation filter.
When a portal such as Bridebook gives only a relay address, the lead is marked reply via portal. Emails to that address go out as plain text with links written as name and address, and your signature is included as text. When the couple writes from their own address in the same conversation, Staybase updates the contact's email automatically. Response time reports then show how quickly the team answered each enquiry.
To see portal enquiries arriving as leads in your own pipeline, book a demo at staybase.co.uk.
