His daughter got engaged in April, and by the middle of July he had become the information desk for two hundred and forty people. He is a retired Navy chief who has lived in the same house off Central Avenue in Summerville for twenty-six years, which is the whole explanation. His is the number everyone in the family has had for three decades. The bride lives in Charlotte and the groom's people are in Ohio, so when an aunt wants to know whether the shuttle comes back to the hotel after the reception, she does not call the couple.
She calls him, at seven in the evening, while he is grilling. He counted one week in July out of curiosity: sixty calls and texts, and forty-one of them were the same nine questions. Which hotel and by when. What does black tie optional mean in October in South Carolina.
Are children invited. Where do we park downtown. Is there a plan if there is a storm, because October is still hurricane season and half the family has to book flights. What is the registry.
What time does anything actually start. Nine questions, asked over and over, most of them by people who had already been told and reasonably could not be expected to remember something they were told in May about something happening the following autumn. Their planner sent him to us in June, in part to get her own phone back. We built three surfaces.
The website carries the whole thing — schedule, travel, hotel blocks with their booking cutoffs, dress code with an actual explanation of what to wear rather than two words, parking, the shuttle, the weather contingency, the registry, the RSVP. A live chat on the site answers in a sentence instead of making a guest hunt through four pages on a phone. And there is a phone number, printed on the paper, that is not his: a receptionist that picks up, answers in a normal voice, and knows exactly what the website knows. The part that actually matters is the fourth thing, which is not a surface at all.
A wedding fourteen months out is not a static set of facts. It is a slow sequence of facts that turn over. Before the hotel cutoff the right answer is book by this date under this name. After the cutoff it is a completely different answer, and the old one is worse than useless because it sends someone to a rate that no longer exists.
Six weeks out there will be a shuttle schedule, and until then there is not one, and the honest answer is that it is coming. Menus firm up. A room block gets extended. The ceremony time moves by fifteen minutes.
So a scheduled task runs every week. It reads the current state of the plan, works out what has changed and what has simply come due on the calendar, and then rewrites all three at once — the page copy, the chat's prompt, and the phone script — in the same pass. That simultaneity is the entire engineering point. Three channels answering the same question is a system that drifts by default, and a website that says one thing while the phone says another is worse than having neither, because now a guest has been told twice and believes the wrong one.
There are things it will not touch. It does not answer who is invited, it does not adjudicate a plus-one, and it does not take a seating request or a dietary restriction and pretend that is handled. Those go on a list that goes to the planner and to the bride. It does not guess.
When it does not know, it says a person will follow up, and then a person does. Six weeks in, the line has taken ninety-six calls and the chat has answered three hundred and ten questions. His own phone went from sixty in a week to seven. The task has run nine times and made thirty-four changes, thirty-three of them small and one of them not, when the block cutoff moved and the page, the chat and the phone all changed the same morning.
The wedding is in October of 2027 and none of this is proven until then. In the meantime he answers his phone again.