Venue agents · the wedge product

Your line, answered in character.

A persistent character answers your venue's phone — before opening, during the rush, and long after close. It takes bookings, reads the night's listing, handles lost & found, and hands anything sensitive to a person immediately. Your regulars get someone worth calling; your staff stay hands-free.

Working prototype — operate it on this site Design-partner program: onboarding a first cohort of venues Demo figures are illustrative sample data
Book a live demo Try the interactive demos
What it handles
Bookings & eventsReservations, private-event inquiries with date, headcount and callback captured and routed to your events inbox.
The night's listingTonight's event, dress code, door time — read from knowledge cards your staff edit; the next caller hears the change.
Lost & foundDescriptions and callbacks logged, matched by staff, caller texted either way.
Tickets & linksCalendar and ticket links texted mid-call, before the caller hangs up.
Vendors & applicantsSupplier requests routed; job applicants engaged and passed to the manager.
Hours & directionsDoor times, transit, parking, accessibility, weather-aware advice.
EscalationHarassment, incidents, safety concerns and anything unscripted ring the manager line at once — never answered by the agent.
The operator consoleWeekly analytics, live call board with takeover, and the editable knowledge base — the exact console in the demo, on your data.
Why character — and how we'll prove it

Generic phone bots exist. Our wager is that a persistent, on-brand character converts and retains better than an anonymous IVR: callers stay on the line, come back, and book. The design-partner program exists to measure exactly that — booking conversion, repeat callers, staff minutes returned, and escalation rate — venue by venue, before we publish a single claim about it.

What we instrument for every partner:

  • Calls answered and resolution on the line
  • Booking and inquiry conversion
  • Staff time returned (modeled, labeled as modeled)
  • Human-escalation rate on bounded workflows
  • Answer time and repeat-caller rate
Operations & guardrails

Bounded knowledge. The agent only says what is written in its knowledge cards. Anything not covered goes to the manager line instead of being guessed at. It never quotes prices it hasn't been given, never confirms bookings it can't hold, never speculates about people on the premises.

Human handoff. Take over any call from the live board. Safety topics escalate within seconds, with the transcript attached so the caller never starts over.

Consent & recording. Call-recording disclosures are configured per jurisdiction before launch; transcripts are retained under a data-retention policy you approve, and can be purged on request.

Integrations. Standard telephony (SIP / number porting or forwarding), reservation and CRM sync, and read-only POS access — the agent can read settled batches; it can never move money or alter a check.

No payment capture on the line. The agent texts links; it does not take card numbers, which keeps the phone line out of PCI scope.

The design-partner pilot
01A working session to write your knowledge cards and tune the character to your room — or design a new one from your venue's identity.
02Launch on a forwarded or after-hours line first; expand to the main line when you're comfortable.
03Weekly operator-console review of real figures — the sample dashboard on this site, on your calls.
04Month-to-month terms, cancel anytime, your number and your data stay yours.

Pricing is a flat monthly fee per line plus usage. Design-partner terms — discounted in exchange for measurement and a reference — are quoted on the demo call, and we'll publish reference pricing once the first cohort is live.

Operator questions, answered straight
Is Hank real?

Hank is a fully working prototype: the console and conversations on this site are the real software running on illustrative sample data. Design partners put an agent on a real line; we don't describe any venue as "live" until one is.

What happens when it doesn't know?

It says so and hands off. Unknown topics, safety concerns, and complaints ring the manager line immediately — that behavior is a hard rule, not a preference.

Can we edit what it says?

Yes — knowledge cards are plain text your staff edit in the console; the next caller hears the change. No scripting, no redeploy, no ticket to us.

What phone systems does it work with?

Standard SIP telephony: keep your number and forward it, port it, or give the agent the after-hours line only. Setup is measured in days, not months.

Languages?

English first; additional languages are scoped per venue during the pilot rather than promised in general.

What do you do with call data?

Transcripts power your console and your metrics. Retention windows are agreed per venue, data isn't sold, and community-sensitive calls are governed by our community principles.

Put a character on your line.

Thirty minutes: a live walkthrough of the console, the escalation model, and design-partner terms for your venue.

Book a live demo