Foyer

What is Foyer?

Foyer is a voice sales agent you embed on your website. It answers visitor questions, navigates the site in real time, and captures leads through a voice conversation.

The core purpose is to turn a website from a static brochure into an interactive, on-site sales interaction that can run continuously once the widget is installed.

Key Features

• Voice sales agent for your website: Visitors click a floating voice button and speak naturally while the agent handles answering, navigating, and lead capture.
• Site-based knowledge base (real-time RAG): Foyer crawls your site and uses a private knowledge base so responses are grounded in your content.
• Real-time page navigation while speaking: When users ask about pricing, features, or examples, the widget scrolls/highlights relevant parts of the page during the conversation.
• Lead capture inside the conversation: The agent collects a visitor’s name and email when the visitor is ready to convert, rather than relying on a separate form.
• Searchable conversation history and transcripts: The dashboard records each conversation and makes transcripts available for review.
• Lead context and export: Leads (name/email) are shown with conversion context, and lead export (CSV) is available on the Starter plan.

How to Use Foyer

1. Create an agent in the Foyer app and copy the install snippet.
2. Paste the provided script tag into your site where you want the widget to appear. The source specifies:

   <script src="https://app.foyer.ink/static/widget.js" data-agent-id="your-agent-id" data-server="https://app.foyer.ink" async></script>
   

3. Index your site: After installation, Foyer crawls the pages and builds a private knowledge base from your content.
4. Test and launch: Once live, visitors use the floating voice button to start a conversation; you can monitor conversations and leads in the dashboard.

Use Cases

• Pricing questions during browsing: A visitor asks how pricing works; the voice agent answers and scrolls to the relevant pricing section.
• Feature discovery and comparisons: A visitor asks about a feature; Foyer highlights the specific area on the page while explaining it.
• Examples and “show me” requests: When a visitor requests to see an example, the agent navigates to the appropriate content within the site.
• Capturing leads without a separate form step: Instead of abandoning a page when a visitor has questions, the voice conversation collects name and email when they are ready to convert.
• Reviewing what prospects ask: Teams can use searchable transcripts and analytics to understand which questions appear most and which pages visitors ask about.

FAQ

• Does Foyer require frameworks like npm or a specific site platform? The page states there is no npm and no framework lock-in, and that it works on Webflow, WordPress, Shopify, Framer, React, and plain HTML.

• What content does the agent use to answer questions? Foyer crawls the site and builds a private knowledge base; the agent answers using content from your site (the page also states “trained on your content only” and “nothing is shared” when indexing).

• When does the widget appear and how do visitors start? After installation, a floating voice button appears on the site; visitors click it to start a voice conversation.

• How are leads stored and what outputs are available? The dashboard records conversations and captures leads during the conversation. The page specifies lead export (CSV) on the Starter plan and mentions export to any CRM, without detailing how that is configured.

• Is the product designed for ongoing availability on the site? The page describes the agent as 24/7 on your site, with the widget handling answering, navigation, capture, and conversion after installation.

Alternatives

• On-site chatbots (text-based): A text chatbot can answer questions, but the workflow differs because Foyer is voice-based and can navigate the page while the conversation happens.
• Static FAQ pages and help centers: These provide information but don’t capture leads inside an ongoing conversation or guide visitors to relevant sections in response to spoken questions.
• Dedicated sales/support chat: A human agent can respond to complex questions, but it typically requires staffing rather than running as an always-on widget.
• Form-based lead capture: Contact forms can collect emails, but they don’t provide real-time voice Q&A or in-page navigation tied to each visitor’s questions.