Asking an existing event production briefs contact to re-introduce themselves was always faintly insulting. The separate path fixed it.
Zachary NightingaleFront office lead, charity gala production company
CS1710 working daysNorth Dakota
Existing event production briefs conversations stay findable
Charity gala production company, Fargo, North Dakota. A clearly labeled follow-up path now asks for a reference where one exists, plus the question itself.
- Client
- Charity gala production company
- Region
- Fargo, North Dakota
- Team
- 13 staff; one locally managed operation
- Timeline
- 10 working days after content approval
Q0200:02:00Before
Where they started, and what kept going wrong
Starting point
Whether someone was starting fresh or following up on event production briefs, the site gave them the identical form to complete.
The problem
For event production briefs, follow-ups arrived dressed as new business. Staff matched names to old threads before anyone could address the actual question.
Q0300:04:30Build
What we built
Answer: A clearly labeled follow-up path now asks for a reference where one exists, plus the question itself. New requests keep their own route, collecting event format, venue and technical requirements, and the two message types arrive under different subjects.
Features used
Existing-request contact route
Optional reference field
Separate email subjects
New-inquiry form
Q0400:07:00Schedule
10 working days, approval to handover
Answer: 10 working days after content approval, including staff review and handover.
- Day 0
Content approved
The clock starts once the client approves the content the work is built from.
- Build
What we built
Existing-request contact route, Optional reference field, Separate email subjects, and more.
- Review
Staff review
The charity gala production company's own team checks the work before it goes live.
- Day 10
Handover
Handed over 10 working days after content approval.
Q0500:09:30After
What changed
Answer: Day to day with event production briefs, new business and ongoing conversations sort themselves before staff get involved. Customers with a history are no longer processed as strangers.
Q0600:11:40Q and A
Questions about this case study
How long did this project take?
10 working days after content approval, including staff review and handover.
Which plan includes this work?
Everything this project used is included on every EventWebStudio plan (Load-In, Showtime, Encore), from $127 a month with the $697 build fee invoiced after launch.
Why is the client not named?
On purpose. The case study names the type of business (charity gala production company) and the region (Fargo, North Dakota) only, so no business name, web address or logo appears. The quote is Zachary Nightingale's own words, used with permission.
Q1300:29:00Curtain
See what this would look like for your event business
A 30-minute walk-through on your screen, starting from this case study. Plans from $127 a month, the $697 build fee invoiced only after launch.