An AI concierge that knows your tournament in real time.
Pairings, tee times, live scores, weather at the first tee, delays, tickets, results — pulled from your systems and answered the moment a player asks, on WhatsApp, Telegram, Signal or the web. From Friday warm-up to Sunday trophy.
Live sync
Pairings, tee times, scores — from your scoring backend.
Tickets + credentials
QR lookup, waitlist promotion, credential routing.
Schedules + delays
Frost delays, tee push, personal schedule.
Weather that helps
Forecast at course coordinates, not the city 20mi away.
Auth-gated data
Players see only their own scores + prizes.
Vision
Leaderboard photos decoded on the spot.
Tournaments compress every hard part of customer service into 72 hours.
A 200-2000-player burst
Parents, spouses, caddies, officials and marshals pile on top. Human ops can't scale to that burst; static FAQ pages don't move at that speed.
Live data that changes hourly
Tee times shift. Delays land. Cut lines move. Weather flips. The AI has to pull from live systems, not a stale KB.
The same 8 questions × 500
Tee times, pairings, parking, rules, cut line, weather, dress code, caddie policy — hitting your director's phone until the phone dies.
Multiple languages, channels, courses
WhatsApp for the international field, Telegram for tech, Signal for VIPs. Two courses running in parallel. Six languages by 8am Saturday.
No slack in the schedule
If the answer is one minute late, the player has already walked past the check-in tent. Real-time or nothing.
Post-round chaos
Result checks, prize queries, photos of leaderboards, "am I in the playoff?" — all in a 20-minute window.
Pull data from your systems, answer the moment they ask.
Pairings + tee times
Synced from your scoring backend on a bucketed cadence — tighter near tee-off, looser further out. Multi-course events supported natively.
Divisions-aware
Future Stars, Middle School, High School, Open, Senior — each player's division determines what they see + how the AI frames it. Parent-friendly for juniors, logistics for caddies.
Live scoring
Hole-by-hole scores, current position, gap to leader, strokes-gained, consistency, trend — pulled the instant the player asks.
Field + WD + cut line
Withdrawal status, projected cut, field size. Real numbers, not estimates.
Weekly digests, automatic
A compact digest of upcoming tee times + last-round results lands in the tournament KB every week. Re-pushes replace in place — the KB stays lean.
Bucketed scrape cadence
Tighter close to tee-off, looser further out. Balances freshness against your scoring backend's rate limits.
The spectator side of the operation.
Ticket lookup
Spectators + player parents check ticket status via emailed QR scan or name lookup after auth. No queue at the will-call window.
Credential routing
Media, caddie, VIP, hospitality — routed to the right operator when needed, handled by the AI otherwise.
Registration status
"Am I confirmed?" "Did my payment go through?" "When do I get my confirmation?" — answered from your registration data.
Waitlist promotion
If a player WDs, ChatGenius messages the top of the waitlist on the channel they registered with, in their language.
Every schedule shift, propagated in a minute.
Personal schedule
"When do I tee off tomorrow?" "When is the awards ceremony?" — answered from the player's own agenda, not the generic one.
Delay push
"Frost delay, 45-minute push" sends across every channel at once. The AI handles follow-ups ("does this affect my pairing?") automatically.
Scheduled announcements
Write once. Target a segment (all players, one division, one course). Pick a send time. Replies flow into the same threads.
Weather at exact coords
Live forecast at the course's exact coordinates, not the city 20 miles away. Google Weather integration, updated on every ask.
Timed forecast
"Will it rain during my tee time?" asks the forecast at that specific time. Frost-delay probability surfaces at 5am so directors can decide.
Storm alerts
Proactively pushes lightning advisories to opted-in players when a cell moves into range.
International field.
Local weather.
Portuguese conversation.
Miguel is playing his first US junior tour event. English isn't his first language, and he wants two answers before breakfast: tee time + weather. ChatGenius pulls both — pairing, forecast at the course, and the temperature — in Portuguese, before Miguel has poured coffee.
The quiet features that matter on Sunday.
Auth-gated personal data
Players see their own scores, pairings, tee times, prize status — no one else's. Public data (leaderboard, cut line, weather) needs no auth.
Leaderboard photos decoded
Player snaps the on-course monitor; ChatGenius reads it and confirms their position + what they need on the back nine to make the cut.
Scorecard scans
Photograph a signed card, the AI extracts the numbers. Backup for scoring-system entry.
Junior coaching lens
Parent-friendly framing, development-focused. Stats via the three-priority coaching framework: reduce big mistakes → make more pars → create birdie chances.
Marshal ticket filing
"Sprinkler broken on 14 fairway" from a marshal's phone with a photo files ticket #4291 in the admin system with location + image. Operators can update tickets from chat too.
Admin bot on Signal/TG
Directors query "how many WDs today?" "message volume?" "tickets open?" from Signal or Telegram. The AI reads live system state and answers.
The players use what they use.
Bridge model — operator scans a QR from your dashboard, WhatsApp installed on their phone, live in ~15 minutes. Each tournament gets its own dedicated bridge.
Telegram
Telegram Bot API. Create a bot, paste the token into your ChatGenius dashboard, live in 60 seconds.
Signal
signal-cli integration. For privacy-first + VIP fields.
SMS (Twilio)
Full SMS coverage in the US, Canada, UK, EU. Your Twilio account or we provision.
Custom inbox address, threaded replies, attachment support.
Web widget
Single-line JS embed on your tournament microsite. Fully white-labeled.
Tournament FAQ.
Does it plug into my scoring system?
Yes — via a well-defined integration contract (~20 lines of glue for a typical REST backend). We regularly integrate custom scoring stacks; common ones we've done before include BlueGolf, Golf Genius, USGA TPP, and custom builds.
How fresh is the data?
Live on-demand for real-time queries. Weekly digests refresh the KB automatically for tee-time + results data with a bounded row count — no clutter, no stale entries. Bucketed scrape cadence: tight close to tee-off, looser further out.
Multi-course events?
Yes. Every course configuration is pulled and unioned; players on the non-default course don't disappear.
How fast is it during peak burst?
Per-instance bursts of hundreds of concurrent messages are handled without degradation. Each tournament gets its own bridge so your weekend traffic never competes with another operator's.
Can players only see their own scores?
Yes. Auth-gated queries verify the player before returning personal data. Public data (leaderboard, cut line, weather) needs no auth.
What about spectators, parents, caddies, media?
Same channel, different persona. Parents get parent-appropriate framing; caddies get logistics; media routes to credentials ops when needed.
Can I schedule the frost-delay message?
Yes, and it hits every channel simultaneously. Replies flow back into the same threads and the AI handles the follow-ups automatically.
Ticket lookup for spectators?
Yes — QR scan or name lookup after auth, straight from your ticketing system.
Waitlist automation?
Yes — a WD triggers a message to the top of the waitlist on their preferred channel, in their language.
What happens after the tournament ends?
Conversation history follows the retention window set on the instance (default 12 months, configurable from 30 days to unlimited — see /privacy). Your knowledge base + configuration stay until you delete them, so a dormant instance can be reactivated for next year's edition without re-onboarding. Full export + purge available on request.
Do I need a WhatsApp Business API contract?
No. Setup is a QR scan from the operator's WhatsApp app (Business preferred) — same mechanism as WhatsApp Web. Live in ~15 minutes. No Meta approval, no Cloud API contract, no 3-5 day wait.
Ready for a tournament weekend where the answer beats the question?
20-minute demo, live from a real tournament instance. Bring your scoring backend URL, we'll show you every ask + reply in real time.