The final week before a wedding is when a planner’s phone becomes the problem. The same questions arrive all day, from people who will not read the invitation twice. What time does the ceremony start. Where do we park. What is the dress code. Can we bring the kids. The Alfie AI guest host exists to take that job off the planner’s phone and put it on WhatsApp, where the guests already are. It answers from the event information the planner wrote, it sends RSVP links and broadcasts, and it hands the planner only the questions it cannot answer.
That is the whole idea, and it is worth stating plainly before any detail. The Alfie AI guest host is not planning software. It does not build timelines, draw seating charts, or chase invoices. It is a guest host. One dedicated WhatsApp number serves the whole event, guests text it, and Alfie replies in the guest’s own language, at any hour. The planner stops being the help desk for answers the event information already holds. For a studio running twenty weddings a year, that change is measured in evenings given back, not in features.
This post explains what Alfie does, how it works, what it does not do, and who should use it. Every fact here comes from Alfie’s own site, textalfie.com, and the numbers Alfie publishes are presented as its claims, not as independent findings. Pricing is not published on the site, so this post gives no price for Alfie. Planners who want a number should talk to the team for a quote.
What the Alfie AI Guest Host Actually Does
The Alfie AI guest host answers practical guest questions on WhatsApp. The answers come from the Event Info the organizer supplies, which is the planner’s own document, event site, or notes covering the schedule, venues, dress code, travel, and practical instructions. Alfie does not search the internet for answers. That single rule is what makes it safe to put in front of guests. Every reply is grounded in what the organizer wrote, and anything outside that information goes to the organizer instead of receiving a guessed answer.
The job covers the questions that repeat at every wedding. Timings and the order of the day. The ceremony start and when doors open. Transport, parking, and shuttles. Hotels and where to stay. Dress code and what to wear for an outdoor ceremony. Plus-ones, children, and dietary needs. These are simple questions with event-specific answers, and they arrive at midnight, in several languages, from guests who expect a reply. Alfie answers them around the clock, in the guest’s own language, without the planner touching the phone.
RSVPs run through the same number but on a different mechanism. Alfie sends each guest a personal RSVP link through an approved WhatsApp invitation template. The guest opens the link and completes the form, and the response lands in the dashboard. A chat message or a read receipt is not treated as an RSVP, and Alfie’s own guide says so. That distinction matters, because a planner who counts chat replies as acceptances ends up with a guest list that is wrong in the final week.
Broadcasts handle the moments when plans change. The organizer picks an approved template, fills it with guest fields, filters recipients by day attendance, dietary need, tag, or language, previews the message as a specific guest, then sends it now or schedules it. Delivery and read counts appear afterwards, so the organizer knows what actually reached the guests. One planner quoted on the site, Sofia B. in Lake Como, moved a ceremony on the day of the event and reached every guest with one broadcast.
Behind all of it sits a dashboard that holds the whole event. RSVPs, broadcasts sent, delivery rate, messages handled, and unanswered questions appear in one view. One login can run one event or twenty, each on its own card with its own status, guests, and WhatsApp number. When Alfie cannot answer a question, it appears in the dashboard and pings the organizer’s WhatsApp. The organizer decides the response and can take over any thread directly, with the full history kept in the dashboard.
The Guest Question Problem, in Numbers
Guest questions look small one at a time, and that is why planners underestimate them. A single question takes a minute to answer. Four questions per guest across a 200-guest wedding is 800 answers, and every one of them arrives in the final weeks, when the planner’s time is already committed to the venue, the vendors, and the couple. The work is not hard. It is relentless, and it lands at hours when no office is open.

Alfie publishes its own averages from more than 100 weddings run on the service, and they describe the shape of the problem rather than any single event. Around 300 guest questions answered per event, automatically. Four messages per guest before the wedding. Two and a half reminders before a guest sends their RSVP. These are Alfie’s numbers, presented as its claims, and a planner who has run a full season will recognize the pattern even if their own counts differ. The questions are the same at every wedding, the volume scales with the guest list, and the reminders are the part nobody budgets for.
The cost of that volume is not only time. It is attention. A planner who answers dress code questions at 11.47 pm is a planner who arrives at the wedding already tired, and a slow reply to a genuine question reads to a guest as indifference, even when the planner is simply asleep. The week before a wedding is when the planner’s judgment matters most, and it is the week when the phone demands the most. That is the problem the Alfie AI guest host is built to remove, and the numbers above are the measure of it.
Camille R., an event planner in Paris quoted on Alfie’s site, describes the before and after in one sentence. The week before, she would normally field 200 messages, and this time almost none reached her. The quote is Alfie’s, from its own site, and it is the clearest statement of what the tool is for. The planner did not get a new skill. She got her week back.
How Alfie Works in Five Steps
Setting up Alfie follows five steps, and the shape of them tells you what kind of tool it is. Nothing here is a planning workflow. Every step is about loading information and guests so the guest host can start answering.
- Create the event with its name, dates, venue, and timezone.
- Load the Event Info, which is the existing planner document, event site, or notes covering the schedule, venues, dress code, travel, and practical instructions.
- Add the guests by importing a CSV or Excel file, or one by one, with tags, meal choices, language, and custom columns.
- WhatsApp goes live, and guests start asking questions on the event’s dedicated number.
- Operate everything from one dashboard, where RSVPs, broadcasts, and unanswered questions sit together.
Alfie says most events go live in under two days after it receives the Event Info. That timing depends on the organizer supplying complete information, and the honest reading is that the Event Info is the work. A thin document produces thin answers, and a careful document produces a guest host that rarely needs help. Planners should load the Event Info early and read it as a guest would, because every answer Alfie gives comes from what was written there.
The fifth step is where the planner’s role changes. Instead of answering, the planner supervises. Unanswered questions arrive in the dashboard and ping the organizer’s WhatsApp, and the organizer decides the response. The organizer can take over any thread and reply directly, and the full history stays in the dashboard for every event. Nothing is hidden. The planner sees what guests asked, what Alfie answered, and what came back to a human. That visibility is what separates the Alfie AI guest host from a black box, and it is the detail a planner should test first.
The setup also explains who Alfie is built for. The five steps are also walked through on Alfie’s how-it-works page, and the full feature set is described on the platform page. It is built for the organizer who already has the information, in a document or an event site, and needs it answered at scale. It is not built for the organizer who has not written anything down, because there is nothing for the guest host to answer from. The tool does not create knowledge. It delivers the knowledge the planner already holds, to guests, at hours the planner cannot.
RSVPs on Personal Links, Not on Chat Messages
An RSVP is a commitment, and Alfie treats it like one. The organizer sends an approved WhatsApp invitation template with a personal RSVP link for each guest. The guest opens the link and completes the form, and the response appears in the dashboard, where the funnel shows invited, attending, declined, and awaiting, updated as guests reply. Pending guests can be chased in one click. The funnel is the point. A planner can see at a glance who has answered and who has not, instead of scrolling through chat history to reconstruct the list.
The distinction Alfie draws is worth repeating, because it is where most guest communication goes wrong. A chat message is not an RSVP. A read receipt is not an RSVP. A guest who writes “see you there” in chat has not completed the form, has not confirmed a meal choice, and has not been counted in the numbers the caterer needs. Alfie’s own guide says so, and the system is built around it. The link is the RSVP, and everything else is conversation.

The chat above shows what that looks like in practice. A guest confirms the RSVP, then asks what time the ceremony starts, then asks about parking, and each question gets an answer from the event information. The planner does not appear anywhere in that exchange. That is the Alfie AI guest host working as intended. The guest gets answers in minutes, the planner gets a completed RSVP in the dashboard, and the conversation that would have been five messages on the planner’s phone never reaches the planner at all.
There is a second benefit that matters more than speed. A personal link per guest means the RSVP belongs to the right person, with the right meal choice and the right plus-one, and it cannot be confused with another guest’s reply in a group thread. Group chats are where RSVP counts go to die, because one guest’s answer sits next to another guest’s question and a third guest’s photo. Alfie keeps each guest on their own link and their own thread, and the dashboard counts what the links return.
Reminders are part of the same system. Alfie’s published averages say a guest needs two and a half reminders before sending their RSVP, and the funnel makes those reminders a single action instead of a round of individual messages. The organizer sees who is still awaiting, chases them in one click, and watches the funnel move. It is not glamorous work. It is the work that decides whether the final guest count is right, and it is the work planners most often leave until too late.
Broadcasts for the Moments When Plans Change
Weddings change. A ceremony moves by an hour. A venue entrance closes. A shuttle time shifts. A storm moves the reception indoors. When that happens, every guest needs to know, and the planner needs to know that every guest knows. A broadcast is how the Alfie AI guest host does it, and the mechanics are deliberately careful.
The organizer picks an approved template, fills it with guest fields, and filters recipients by day attendance, dietary need, tag, or language. The message can be previewed as a specific guest, so the organizer sees exactly what that guest will see, with their name and details filled in. Then it is sent now or scheduled. Delivery and read counts appear afterwards, so the organizer knows what actually reached the guests instead of assuming the message landed.
Sofia B. in Lake Como, quoted on Alfie’s site, moved a ceremony on the day of the event and reached every guest with one broadcast. No panic, no phone tree. The story is Alfie’s, and it is the right example, because a same-day change is the hardest test of any guest communication system. A planner with a phone list and a group chat can reach most guests most of the time. A broadcast with delivery counts can show which guests were reached and which were not, and that difference is what lets the organizer follow up with the few instead of worrying about the many.
The filter matters as much as the send. A change that affects only the Saturday guests should not wake the Friday guests. A message about the vegetarian menu should not go to the whole list. Alfie’s recipient filters exist for that reason, and a planner who uses them well sends fewer messages that land better. The preview step matters too. A template with a guest field filled wrong is worse than no message, because it tells the guest the organizer does not know who they are. Previewing as the guest catches that before it goes out.
Broadcasts are also where the delivery and open numbers come from. Alfie claims a 99 percent message delivery rate and a 98 percent open rate on WhatsApp broadcasts, and those are its claims, not independent findings. The numbers are plausible for WhatsApp, where messages are delivered to a phone people check constantly, and they are the reason a broadcast beats an email for a same-day change. An email can sit unread for a day. A WhatsApp message is usually read within the hour. For a ceremony that moved, that gap is the whole decision.
One Dashboard for Every Event
The dashboard is where the whole event sits, and its design reflects the job. RSVPs, broadcasts sent, delivery rate, messages handled, and unanswered questions appear in one view. The planner does not need to open five screens to understand one wedding. The funnel shows who is coming. The broadcast log shows what was sent and what was read. The unanswered queue shows what needs a human. Everything else is detail for when it is needed.
One login can run one event or twenty, each on its own card with its own status, guests, and WhatsApp number. That matters for a studio, because a planner running twenty weddings a year is not running twenty copies of the same event. Each has its own guests, its own Event Info, and its own number, and the dashboard keeps them separate. A guest texting about one wedding never reaches the information of another, because the number they text belongs to one event only.
The unanswered queue is the most important part of the dashboard, and the part a planner should look at first. When Alfie cannot answer a question, it does not guess. The question appears in the dashboard and pings the organizer’s WhatsApp, and the organizer decides the response. The organizer can take over any thread and reply directly, and the full history stays in the dashboard. Over time, the queue also shows what the Event Info is missing. If five guests ask the same question Alfie could not answer, the answer belongs in the Event Info, and the next five guests get it straight away.
Guest data is deleted 30 days after the wedding date under Alfie’s terms. That is a clean rule, and a planner should know it before the event, not after. The guest list, the conversations, and the event information are removed a month after the day, which fits the job. A guest host is needed for the wedding and the weeks around it, not forever. Responses are generated by OpenAI GPT-4.1 via API, named on Alfie’s sub-processor list, which is the kind of detail a planner who cares about data handling should check on the site before signing.
What Alfie Does Not Do
What Alfie does not do matters as much as what it does, and the site states it plainly. Alfie handles guest communication, not wedding planning, supplier bookings, or on-site coordination. Sharing hotel or transport information is not the same as booking it for guests. It is not an emergency service, and for urgent help on the day guests need an appropriate on-site contact. It does not replace a wedding planner. It replaces the part of the planner’s week that no planner should be spending on repeated questions.
The boundary is worth spelling out, because a tool that answers guests can look like a tool that runs the wedding. It does not. Alfie will tell a guest where the hotel is. It will not book the room. It will tell a guest what time the shuttle leaves. It will not hold a seat on it. It will tell a guest the dress code. It will not choose the outfit. Every answer comes from the Event Info, and the Event Info is information, not action. A planner who understands that boundary will use the tool well. A planner who expects it to do the planning will be disappointed, and the disappointment will be the planner’s fault, not the tool’s.
The emergency limit deserves its own sentence. If a guest is lost, ill, or in trouble on the day, Alfie is not the number to call, and the Event Info should say so, with the right on-site contact named clearly. An AI guest host is the wrong place for urgency, and Alfie’s site says so. The planner should make sure the Event Info carries a real human contact for real problems, and that guests know the difference between a question and an emergency before the day arrives.
There is one more limit, and it is a condition rather than a flaw. Alfie’s terms describe the service for planners operating in Europe, the United Kingdom, and Switzerland, while guests can be anywhere in the world. If a studio is outside that area, it should confirm availability with the team first. The restriction is about the planner’s location, not the guests, and it is stated on the site rather than discovered after signup. A planner outside the area who wants the tool should ask before assuming it is available.
Who Alfie Is For, and Who Should Skip It
The Alfie AI guest host is for the planner whose week is eaten by guest questions. That is the whole test, and it is a simple one. If the final week before a wedding means a phone full of the same five questions, Alfie will change the shape of that week. If the planner runs twenty weddings a year, the change is large. If the planner runs five, it is still real, because five weddings still produce hundreds of questions, and the questions still arrive at midnight.
It is also for the couple who are handling their own guests. A couple planning their own wedding faces the same flood, with less help, and a guest host that answers from their own event information does the same job for them. The planner and the couple are the two audiences on Alfie’s site, and both need the same thing. Someone to answer the guests, accurately, at any hour, without bothering the people running the wedding.
It is for the destination wedding in particular. When half the guest list is flying in, the questions multiply. Flights, hotels, transport from the airport, what to wear in a climate they do not know, and whether the ceremony is outdoors. Guests who are travelling ask more, and they ask earlier, and they ask in more languages. Alfie answers in the guest’s own language, which matters most when the list is international. A planner running destination weddings should test the tool on a real guest list before the season starts.
Who should skip it. A planner whose guests rarely ask questions does not need a guest host, and that planner is lucky. A wedding with forty guests who all know the venue needs less help than a wedding with two hundred guests who have never been to the country. A planner who has not written down the event information should also wait, because Alfie answers from what the organizer supplies, and an empty document produces an empty guest host. Write the Event Info first, then bring in the tool. And a planner outside Europe, the United Kingdom, and Switzerland should confirm availability before building a plan around it.
The honest summary is that Alfie fits the planner who already has the answers and needs them delivered. It does not fit the planner who has not decided the answers yet. The tool is a delivery mechanism for the planner’s own knowledge, and its value rises with the quality of the information loaded into it.
Alfie vs Answering Guests Yourself
The comparison below is not against another product. It is against the way most planners still handle guests, which is personally, on their own phone, whenever a message arrives. That is the real alternative, and a planner should judge Alfie against it.
| Job | Alfie | Answering guests yourself |
|---|---|---|
| Answering at midnight | Replies at any hour, from the Event Info | Waits until morning, or costs the planner sleep |
| Answering in another language | Replies in the guest’s own language | Needs the planner to speak it, or a translation step |
| RSVP tracking | Personal links, funnel shows invited, attending, declined, awaiting | Chat history, reconstructed by hand |
| Chasing pending RSVPs | One click from the funnel | Individual messages, one guest at a time |
| Same-day changes | Broadcast with delivery and read counts | Group chat, with no proof of who saw it |
| Unanswered questions | Surface in the dashboard and ping the organizer | Arrive mixed with everything else, easy to miss |
| After the wedding | Guest data deleted 30 days after the date | Guest messages stay on the planner’s phone |
The table does not flatter the manual way, and it should not. Answering guests personally is warm and human, and for a small wedding with guests the planner knows well, it is often the right choice. But it does not scale, and it does not sleep. A planner running twenty weddings a year cannot answer four thousand guests personally without the job becoming the whole week. Alfie exists for the planner who has reached that point and wants the personal touch kept for the guests who actually need a human, while the repeated questions go to the guest host.
The other way to read the table is as a list of what to test. A planner considering Alfie should test each row with a real event. Send the event number to two colleagues as test guests. Have them ask about the dress code in another language. Have them ask about parking at midnight. Ask the question the Event Info does not cover, and check that it reaches the organizer instead of receiving a guessed answer. That one exercise tests more than any feature list, because it tests the boundary between the guest host and the planner, and that boundary is the product.
Setup Checklist for Your First Event on Alfie
Use this sequence for the first event, and do not skip the test step. The checklist is short because the setup is short, and the test is where the value is proven.
- Write the Event Info as a guest would read it, covering the schedule, venues, dress code, travel, hotels, plus-ones, children, and dietary needs. Read it once as a guest who knows nothing about the wedding.
- Create the event with its name, dates, venue, and timezone, then load the Event Info.
- Import the guest list from a CSV or Excel file, or add guests one by one, with tags, meal choices, language, and custom columns. Check that every guest has the right language set.
- Send the event number to two colleagues as test guests. Have them ask the questions real guests will ask, in their own words, and read every answer before the event goes live.
- Add anything Alfie could not answer to the Event Info, so the next guest gets the answer straight away.
- Send the approved invitation templates with personal RSVP links, and watch the funnel fill. Chase pending guests from the funnel, not from chat history.
- Before the day, write the on-site emergency contact into the Event Info, so a guest with a real problem reaches a human, not the guest host.
- After the wedding, check the dashboard once more for unanswered questions, then let the guest data delete 30 days after the date under Alfie’s terms.
Frequently Asked Questions
Does Alfie replace a wedding planner
No. Alfie handles guest communication, not wedding planning, supplier bookings, or on-site coordination. That is the wording on Alfie’s own site. The planner still plans the wedding, manages the vendors, and runs the day. Alfie takes the repeated guest questions, so the planner’s time goes to the work only a planner can do.
How fast can Alfie go live for an event
Alfie says most events go live in under two days after it receives the Event Info. The organizer supplies the guest list and the event details, covering the schedule, venues, travel, dress code, and RSVP arrangements, and Alfie builds the event around them. Load the Event Info early and check it before going live, because every answer Alfie gives comes from what was written there.
Is Alfie only for weddings
Alfie is built for weddings first, and its terms and guides are written around wedding planning, but the same guest host works for other events. The service is described for planners operating in Europe, the United Kingdom, and Switzerland, while guests can be anywhere in the world.
What happens when Alfie cannot answer a question
It does not guess. The question appears in the dashboard and pings the organizer’s WhatsApp, and the organizer decides the response. The organizer can take over any thread and reply directly, and the full history stays in the dashboard. If the same question comes up more than once, the answer belongs in the Event Info, so the next guest gets it straight away.
How much does Alfie cost
Pricing is not published on Alfie’s site, so this post gives no price, no tiers, and no trial claim. Planners who want a number should talk to the team for a quote. The site offers an interactive demo with no signup that runs a real WhatsApp flow, which is the fastest way to judge the tool before asking about price.
Where can I see how Alfie fits with planning software
Alfie covers guest communication, which planning tools do not cover on their own. Our guide to the Best Planning Software for Wedding Planners puts Alfie at number one for the guest layer, with fifteen planning tools for timelines, seating, budgets, and bookings. Read the two together to see the full stack.
The Verdict
The Alfie AI guest host earns its place by removing the most repeated job in wedding planning, and by refusing to pretend it does anything else. It answers guests on WhatsApp from the organizer’s own information, in the guest’s language, at any hour. It sends personal RSVP links and broadcasts with delivery counts. It hands the organizer only the questions it cannot answer, and it deletes guest data thirty days after the wedding. That is a narrow job, done carefully, and the narrowness is the point.
A planner should try it the way the tool asks to be tried. Load the Event Info for a real wedding, import a real guest list, and send the event number to two colleagues as test guests. Have them ask the hard questions, in their own words, at an awkward hour. Read every answer. Add what is missing to the Event Info. Then decide. If the test guests get accurate answers and the planner’s phone stays quiet, the tool has done its job, and the next wedding will feel different in the final week.
The final word is the one Camille R. gave on Alfie’s site. The week before, she would normally field 200 messages, and this time almost none reached her. That is not a claim about software. It is a claim about a week, and any planner who has lived through that week will know exactly what it is worth.