ChatGenius FAQ.

ChatGenius is an AI chat concierge that helps customers find answers from your business content. FAQs, menus, schedules, product details and policies give it the information to work with. It is designed for businesses that answer the same customer questions throughout the day, including events, venues, tours and service teams.

A scripted bot follows a fixed set of paths. ChatGenius uses your knowledge base and the conversation to respond to questions phrased in different ways. That makes source quality and testing important: review the answers against real customer questions before putting them in front of customers.

ChatGenius can be configured for website chat and messaging channels such as WhatsApp, SMS, Telegram, Signal and email. Available channels and connection methods depend on your setup. See Integrations, and tell us which channels your customers already use.

Not for website chat. Customers can open the chat on your site. On messaging channels, they use the app or service they already use for that channel; they do not need a separate ChatGenius customer app.

ChatGenius is designed for multilingual conversations. Include your customers' languages in the demo and test questions that use your business terminology. Language coverage and answer quality can vary with the model, source content and channel, so test the languages you need before rollout.

Start with the content customers need, the channels you want to use and a set of real questions to test. We review the scope, configure the proposed setup and check the answers with you. Timing depends on content readiness, channel access and integrations; agree the rollout schedule after that review.

No. Start with the material you already maintain, such as FAQs, menus, schedules and policies. Clear, current documents are more useful than trying to predict every possible question. Existing question-and-answer content is useful too; we can review the source formats during setup.

Update the approved knowledge-base content when prices, hours, schedules or policies change. How updates are imported and published depends on your setup. Test a few relevant questions afterward so you know the chat is using the new information.

Human handoff is part of the ChatGenius workflow. During setup, decide which questions should go to your team, who receives them and what happens outside staffed hours. Test the takeover and return-to-AI flow on the channels you plan to use.

• Auto: AI replies without an operator approving each message.
• Assisted: AI drafts a reply for an operator to review before sending.
• Manual: Your team handles the conversation directly.

Confirm which modes are available on your selected channels and how they are assigned in your setup. Choose the level of oversight to match the topic and your team's capacity.

Review conversations to find missing information, unclear wording and questions that need a human. Use those findings to update the knowledge base and test again. Ask which feedback features are enabled in your setup; do not assume that editing a reply automatically trains an AI model.

Yes. AI-generated answers can be incomplete or incorrect, even when source material is provided. Keep your content current, test common and difficult questions, and define when a conversation needs human review. Do not rely on an AI answer alone for sensitive decisions or commitments.

A local connection problem may prevent your operators from reaching the service. Whether customer messages and automated replies continue depends on the hosting, channel connections and services involved. Include outages and manual fallback in the rollout plan rather than assuming uninterrupted replies.

Check the AI provider, account settings and processing terms that apply to your deployment. Training and retention arrangements are not the same for every service or feature. Review Security and the Privacy Policy, and raise any no-training or retention requirements before sharing business or customer data.

Request the hosting region, storage locations and backup arrangements for the proposed setup. Enabled channels and external services can add their own processing locations. See Security for the items to review, and tell us if you have residency requirements.

That depends on the data you process, the channels you enable and the controls and agreements in place. Share your requirements before rollout so the proposed setup can be reviewed. The Privacy Policy and Security page are starting points, not a blanket compliance guarantee.

See Pricing for the current plans. Your channels, message volume, number of instances and integration work help determine the right scope. Confirm recurring fees, usage charges and any setup costs in the proposal before you commit.

Request a demo to discuss your use case and the questions customers ask most often. Use the demo to review answers, channels and the operator workflow. Ask about any available pilot or trial options and confirm their scope and terms before starting.

Check the plan or proposal for included instances, channels, message allowance, operator access, content updates and support. Integration work and third-party service charges may be separate. See Pricing or ask our team about the setup you have in mind.

Tell us whether you already have a WhatsApp Business account and which number you want to use. The account requirements, connection method and permissions depend on the integration. Plan a number for customer conversations, and review the access being granted before connecting an account. We will confirm the requirements for your setup.

A multi-instance setup can keep the content and channels for different locations, events or brands organized separately. Discuss who manages each instance and which operators need access. Review the separation and permissions you require, along with the number of instances included in the plan.

Integration depends on the system's API or supported connection method, the data available and the actions you want the chat to perform. Tell us the product name and workflow, such as checking availability or creating an inquiry. We will review the access and implementation scope; an API alone does not make every workflow ready to use. See Integrations.

Discuss announcements as part of your channel and workflow requirements. Availability, scheduling, recipient lists and sending limits depend on the selected integration. Review the audience and applicable channel rules, and confirm how replies will be handled before planning a campaign.

Image handling depends on the selected AI model, channel and configuration. Bring representative examples, such as a product photo or screenshot, to the demo and review the results. Reading an image is different from reliably verifying an identity, receipt or reservation, so define where human review is needed.

Where voice-note processing is enabled, audio can be transcribed so the question can be handled as text. Supported formats, languages and reply options depend on the channel and configuration. Test realistic recordings, including background noise, and confirm how unclear messages are handed to your team.