FANZ
FANZ

Changelog

Omnichannel Chatbot, Online Reputation, Sales Breakdown & Morev3.5.6Apr 9, 2026Ticket Office: Refund window enforcement, Close Yesterday & Admin image pricingv3.5.7Apr 9, 2026Image Carousel Block in Page Builderv3.5.5Mar 17, 2026Group Actions in Event Detail Tabsv3.5.4Mar 16, 2026Selective Event Duplicationv3.5.3Mar 13, 2026Discount Presets in the Promotional Code Formv3.5.2Mar 12, 2026Partner Program — Welcome banner, free ticket tracking & activation emailv3.5.1Mar 11, 2026Partner Program — Lifetime Partner Programv3.5.0Mar 10, 2026Chatbot Training FAQ Manager & Partial Reservation Completionv3.4.1Mar 8, 2026Segments, Flows & External Events Improvementsv3.4.1Mar 6, 2026Automation Flow Builderv3.4.0Mar 4, 2026Bounce & Complaint Tracking with Automatic Email Suppressionv3.3.0Mar 4, 2026Require Contact to Chatv3.3.1Mar 3, 2026Fanz Invoices Tab in Brand Settingsv3.3.0Feb 27, 2026Advanced Email Link Tracking & Recipient Activity Timelinev3.2.0Feb 11, 2026Date Generator, RSVP Question Ordering & Fanzly in Navigationv3.1.3Feb 10, 2026Events Filter Tabsv3.1.1Jan 26, 2026January 2026 Releasev3.1.0Jan 6, 2026November 2025 Releasev3.0.0Nov 7, 2025Block Purchases with Multiple Ticket Typesv2.6.1Oct 30, 2025Custom Web Pagesv2.6.0Oct 14, 2025Universal Multi-Event Discountsv2.5.0Sep 2, 2025Calendar Invite Customizationv2.4.1Jul 29, 2025New Weekly Calendarv2.4.0Jul 25, 2025Bulk Ticket Price Editorv2.3.1May 21, 2025Location Filter in Purchasesv2.1.2Jan 21, 2025Interface and Calendar Improvementsv2.1.1Jan 16, 2025Calendar and Location Improvementsv2.1.0Jan 10, 2025Fanz Core Featuresv1.0.0Jan 1, 2024
New Feature

Require Contact to Chat

v3.3.1March 3, 2026

Require Contact to Chat

A new chatbot capability that lets you collect visitor contact information before they start a conversation — giving you a guaranteed way to follow up.

🔒 New capability: Require contact to chat

A new toggle has been added to Website → Chatbot under Features.

How it works

When enabled, visitors see a contact form instead of the chat interface. They must provide their email, phone number, or both before the conversation unlocks.

DetailValue
LocationWebsite → Chatbot → Features
DefaultDisabled
Fields collectedEmail, Phone (at least one required)

What visitors see

  1. A branded contact gate screen explaining they can access AI support by providing their contact info
  2. Email and phone fields (at least one must be filled)
  3. After submitting, the chat unlocks and the conversation begins normally

Where contact data is stored

Contact information is saved on the conversation and visible in Chatbot, in the same "Contact captured" column used by Lead capture.

⚠️ Mutual exclusivity with Lead capture

Require contact to chat and Lead capture cannot be active at the same time. Enabling one automatically disables the other.

If you want...Enable
Contact info for every conversation upfrontRequire contact to chat
Contact info only when the bot can't answerLead capture

🎯 Why this matters

Some organizers need a reliable way to reach every visitor who uses the chatbot — for example, to correct an incorrect answer or follow up on a support issue. This feature ensures you always have a point of contact.

💡 Summary

  • New toggle — "Require Contact to Chat" in Website → Chatbot → Features
  • Contact gate — Visitors provide email/phone before chatting
  • Same contact data — Stored alongside Lead capture contacts in Chatbot conversations
  • Mutually exclusive — Cannot be active at the same time as Lead capture
  • Bilingual support — Contact gate displays in English or Spanish based on visitor language