This is a sample use case featuring a fictional demo bot built to showcase what's possible with Boty. The event described is not real. Try the demo bot yourself.
TechUp Tel Aviv is a two-day technology conference that brings together developers, product managers, designers, and startup founders from across Israel and beyond. In 2026 the event expected around 800 attendees, 40 speakers, three parallel tracks, and a packed schedule that ran from 8 AM keynotes to late-night networking mixers.
The organizing team had five people. Five people responsible for sponsors, speakers, catering, venue logistics, A/V, and—oh yes—answering every question that 800 curious attendees could possibly think of.
If you have ever organized an event of any size, you already know the pattern. The moment registration opens, the messages begin:
These are perfectly reasonable questions. The problem is that every single one of them gets asked dozens of times. At TechUp 2025 (the previous year), the team counted over 600 WhatsApp messages in the two days leading up to the event and during the event itself. More than 80 percent of those messages asked one of roughly 15 recurring questions.
That meant organizers were spending hours typing the same answers, copying and pasting from a shared Google Doc, and still missing messages because they were busy dealing with a speaker whose laptop wouldn't connect to the projector.
Volunteers helped, but they needed training, they rotated shifts, and they sometimes gave conflicting information. One volunteer told attendees that parking was free. It wasn't.
Before TechUp 2026, the organizing team set up a Boty conference bot in under 30 minutes. They fed it every piece of information an attendee could need:
Schedule and sessions. The full two-day agenda with session titles, speaker names, room assignments, and time slots. When an attendee asked "What's happening at 2 PM on Day 1?", the bot pulled up the three parallel sessions running in that slot.
Venue logistics. Address, directions by car and public transit, parking options and pricing, building entrance instructions, floor maps, and which elevator to take to the third-floor workshops.
WiFi and connectivity. Network name, password, and a note about the backup network in case the main one got congested (it always does at tech conferences).
Food and dietary needs. The full catering plan, including breakfast, lunch, and coffee break times. Vegetarian, vegan, and gluten-free options clearly listed. Location of the water stations and the coffee bar.
Speaker information. Short bios for all 40 speakers, links to their social profiles, and which sessions they were presenting. Attendees could ask "Tell me about the speaker in Room B at 11 AM" and get a useful answer.
Networking events. Details about the evening mixer, the startup pitch competition, and the after-party. Dress code (casual), drink situation (open bar until 10 PM), and how to get home afterward.
Practical details. Where to find the coat check, whether power outlets were available at seats, the location of prayer rooms, nursing rooms, and accessibility information.
The bot was shared via a QR code printed on every badge, projected on screens between sessions, and included in the pre-event email. Attendees could scan and start chatting instantly through WhatsApp or a web link—no app download, no account creation.
Here is what a typical interaction looked like:
Attendee: "Hey, where do I park?"
Bot: "There are two parking options: (1) The underground garage at Azrieli Sarona, enter from Kaplan Street, NIS 15/hour capped at NIS 60/day. (2) Street parking on Derech Menachem Begin, free after 7 PM and on Saturdays. We recommend arriving before 8:30 AM for the best garage spots."
No waiting. No hoping a volunteer walks by. No texting the organizer group chat and waiting 20 minutes for someone to notice.
During the two-day conference, the bot handled over 1,400 conversations. The most-asked questions, in order:
That is 680 questions in the top five categories alone—questions that would have otherwise landed on the desks, phones, and shoulders of five organizers who had far more important things to handle.
The TechUp team reported three clear outcomes:
Organizer sanity. The number of direct WhatsApp messages to organizers dropped by roughly 75 percent compared to the previous year. The remaining messages were genuine issues—things like a speaker cancellation, a room change, or a medical situation—exactly the kind of things that need a human.
Attendee satisfaction. Post-event survey scores for "ease of finding information" jumped from 3.4 out of 5 in 2025 to 4.6 out of 5 in 2026. Multiple attendees specifically mentioned the bot in their feedback: "I loved that I could just ask the bot instead of hunting for a volunteer."
Zero volunteer info desk. For the first time, TechUp did not staff an information desk. The QR code on the badge was the info desk. This freed up two volunteers to help with session room management instead.
Three things made this bot effective rather than annoying:
First, the information was comprehensive and accurate. The team spent 30 minutes loading real, verified details into the bot. No placeholder text, no "check the website for details." Every answer was complete.
Second, the bot was accessible at the moment of need. A QR code on the badge meant attendees could reach it in three seconds, right when the question popped into their head. No searching for an app, no navigating a website menu.
Third, the bot handled ambiguity well. When someone asked "food?" instead of a full sentence, the bot understood the intent and provided the catering schedule. When someone asked a question the bot couldn't answer, it said so clearly and directed them to the organizer's phone number.
Want to see what the TechUp conference bot experience feels like? The demo is still live.
Planning your own conference, meetup, or tech event? You can build a bot like this in under 30 minutes—no coding required.