Our Email Agent Responds in Under 60 Seconds. Here's What It Took to Build That.

Event coordinators spend somewhere between 40 and 60 percent of their working day on email. Not planning. Not creative work. Email. Answering the same questions across five different groups of people, each with their own urgency, their own vocabulary, and their own expectations.

That number didn't surprise us. We'd heard it from organizers over and over before we built anything. What surprised us was how specific the pain was. It wasn't just the volume of emails. It was the context-switching. A sponsor asking about booth dimensions, an attendee asking about parking, a speaker confirming AV requirements, a vendor requesting a purchase order — all in the same inbox, sometimes in the same hour. Each one requiring you to recall a completely different slice of your event's details before you can write a useful reply.

We built Eventfold's Email Agent to solve exactly that problem. Here's what it actually does, and why it's harder than it sounds.

The Five-Group Problem

Most events involve at least five distinct groups of people sending email at any given time:

• Speakers and performers — asking about schedules, AV setups, accommodation, green room arrangements, and fee payments
• Sponsors — asking about booth placement, branding guidelines, lead retrieval, and invoice status
• Vendors and suppliers — asking about delivery windows, access times, setup logistics, and purchase orders
• Venue contacts — asking about capacity confirmations, catering headcounts, liability documentation, and overtime costs
• Attendees — asking about parking, dietary requirements, ticket transfers, accessibility needs, and refund policies

Each of these groups speaks a slightly different language and has different expectations around response time and tone. A sponsor contact at a large company expects a professional, structured reply. An attendee anxious about a dietary restriction wants reassurance, quickly. A venue operations manager asking about headcount changes needs a precise number, not a vague "we'll confirm soon."

Generic email tools treat all of these the same. Eventfold's Email Agent doesn't.

What the Email Agent Actually Does

When an email arrives, the agent reads it and immediately starts building a picture of what's actually being asked. Not just the surface-level question, but the intent behind it.

Understanding context, not just content

The agent knows your event. It has access to your attendee list, your speaker lineup, your ticket types, your venue details, your schedule, your sponsor agreements, and your vendor arrangements. When a sponsor named Henrik from TechCorp AB writes in asking about "the setup time for our booth in Hall B," the agent doesn't just see a generic question about booths. It sees a question from a specific sponsor, about a specific booth location, in the context of a specific event with a specific floor plan and a specific move-in window.

That context is the difference between a useful response and a useless one.

Classifying urgency

Not every email is equally pressing. A speaker asking about hotel options three weeks before the event is different from a speaker emailing the morning of to say they've missed their flight. The agent assesses urgency as part of its initial read, which determines how quickly it surfaces a draft for your attention and how it frames the response.

Drafting the response

The agent drafts a reply using the full context it has — and this is the hardest part to get right, which I'll come back to.

The draft goes to the organizer for review before anything is sent. That's non-negotiable. The human is always in the loop. The agent's job is to eliminate the cognitive overhead of pulling together the right information and writing a coherent first draft, not to replace the coordinator's judgment.

Why Generic AI Email Tools Can't Do This

Tools like Gmail's AI compose features or general-purpose AI writing assistants are good at writing emails. They're not good at knowing what to write about.

When a vendor asks "what time can we access the loading dock on setup day?", a general AI tool can help you phrase a polite response. But it has no idea what the answer is. It doesn't know your venue. It doesn't know your vendor agreement. It doesn't know your setup schedule. It will either generate a plausible-sounding non-answer or ask you to fill in all the blanks yourself — which defeats the point.

Eventfold's Email Agent knows the answer. Or if it doesn't, it tells you exactly what information is missing and why, rather than inventing something convincing.

This is what "event context" means in practice. It's not a marketing phrase. It's the difference between an assistant that makes you do less work and one that just reformats the work you were already going to do.

The Hardest Part: Not Sounding Robotic

Getting the information right is hard. Getting the tone right is harder.

Event coordinators often have established relationships with their contacts. Sponsors have been working with them for years. Speakers were personally recruited. Venue contacts have been collaborating with them through three annual events in a row. An email that sounds like it was written by a machine — even a very accurate machine — can undermine those relationships.

We spent a lot of time on this. The agent is instructed to match the register of the incoming message. If a speaker emails in a casual, first-name tone, the draft should reflect that. If a corporate sponsor writes formally, the draft should be formal in return. The agent pays attention to how the person writes, not just what they're asking.

It also avoids certain patterns that AI writing tends to fall into: over-qualified statements, hedging on things that don't need hedging, unnecessary affirmations before getting to the point, and an overall tone that reads as customer-service-scripted rather than human.

We don't always get this perfect. The human review step exists partly because of this. But our goal is that the draft requires edits, not a rewrite.

The Trust Architecture

Everything the Email Agent produces is a draft. No email goes out without the coordinator seeing it first and explicitly approving it.

This isn't just a safety feature — it's the product design. Event coordination is a relationship business. The coordinator's voice, judgment, and discretion matter. The agent is there to handle the information retrieval, the first-pass writing, and the prioritization. The coordinator is there to make sure the message is right before it goes to another human being.

When you open Eventfold and see a batch of incoming emails, each one already has a draft attached. You read the draft, make any changes you want, and hit send. Or you reject it and write your own. The agent never sends anything on your behalf without that approval.

This is what we mean by human-in-the-loop. It's not a checkbox. It's the design philosophy.

Three Scenarios That Illustrate This

Speaker cancellation the day before the event. A speaker emails at 7 AM saying they've had a family emergency and can't make it. The agent classifies this as high urgency immediately. It pulls up the event schedule, identifies which session is now empty, checks whether there are any other speakers whose topics overlap, and drafts a compassionate reply to the speaker while simultaneously surfacing a draft note to the relevant internal contact about the schedule gap. The coordinator sees all of this within 60 seconds of the email arriving.

Sponsor invoice question. A sponsor's finance team emails asking why they haven't received an invoice for their platinum sponsorship package. The agent finds the sponsor's agreement details, checks the associated billing information in the event record, and drafts a response that either confirms the invoice status or flags that the coordinator needs to follow up with their accounts team. No more digging through three different systems to answer a finance question.

Attendee dietary change. An attendee registered three weeks ago with no dietary requirements. They now email saying they've recently been diagnosed with a nut allergy and need to make sure catering is aware. The agent updates the attendee record, drafts a reassuring reply confirming the note has been added, and creates a task to notify the catering vendor. The coordinator approves the reply, and the follow-up is already queued.

What "Under 60 Seconds" Actually Means

The 60-second figure refers to the time from an email arriving in your inbox to a draft reply being ready for your review. That's the measure we optimized for, because it maps to the coordinator's actual workflow.

In practice, this means coordinators can now process a backlog of 20 emails in the time it used to take to respond to 3. They're not faster typists. They're spending their time on judgment — deciding whether a draft is right — rather than on retrieval and composition.

For some coordinators, it means they can actually step away from their inbox during event day without things piling up catastrophically. The agent keeps the queue moving. The responses are ready when they get back.

Part of a Larger System

The Email Agent is one of 20-plus specialized agents in Eventfold. Each one is built for a specific domain: ticketing questions, schedule changes, financial reconciliation, accessibility requests, and more. They share the same underlying event context, which means the Email Agent doesn't need to re-learn your event every time it handles a message. The context is already there.

We're a solo-founder company, built out of KTH Stockholm. We built the agent system this way because we believed — and still believe — that the biggest productivity gains in event management come from tools that understand the full picture of an event, not tools that address one slice at a time.

If you're an event coordinator spending your days buried in email, we'd like to show you what this looks like in practice. Get in touch with us — a demo takes less time than your average morning inbox session.