// INTEGRATIONS
Connect chat to the way you work.
A useful chat needs more than answers from a document. It may need a calendar, a customer record, or a way to reach your team. Start with the channels you want to use, then tell us which tools need connecting. We’ll check the available integration, permissions, and plan requirements with you.
// 01 — CHAT CHANNELS
Choose where the conversation happens.
Connect WhatsApp when it’s a channel your customers already use. Review the account, phone number, connection method, and messaging requirements during setup. Test the conversation and team handoff before sharing the number.
SMS requirements
Need SMS? Ask us to review the use case before treating it as an available customer channel. A Twilio account alone does not establish ChatGenius support; coverage, registration, consent, and integration requirements also need checking.
Telegram bot
A Telegram bot gives customers another way to reach the chat. Connect the bot account and test the information it can access, the replies it sends, and any planned announcements.
Signal
Discuss a Signal connection if it fits your customers or staff. Review how messages are processed once they reach the AI and connected tools; the messaging app alone does not establish privacy or compliance for the full workflow.
Discuss a connected inbox for customer conversations or follow-up. Confirm the available threading, attachment, and reply behavior for your plan and email setup before relying on it.
Website chat
Add the widget to your site so visitors can ask in a browser. Review branding options and test the placement on desktop and mobile. Website chat can be used without a separate messaging account.
// 02 — WEBSITE + CMS
Add chat to your existing website.
WordPress
Add ChatGenius through a plugin or website embed. We’ll review the installation method for your site and any extra data the chat needs, such as WooCommerce products or order information.
Shopify
Discuss adding the website embed to your storefront. Product and order questions need the relevant data connection and permissions. Confirm the installation route for your store rather than relying on a future app-marketplace release.
Wix, Squarespace & custom sites
Use a custom-code area where your platform and plan allow scripts. For a custom interface, your developer can discuss API and webhook options with us. Check site restrictions before choosing an approach.
// 03 — BUSINESS SYSTEMS
Give the chat access to the right information.
Booking systems
Using Cloudbeds, Mews, Little Hotelier, Rezdy, FareHarbor, or Xola? Tell us which one and what the chat should do. Checking availability, holding a place, and confirming a booking are separate actions that need supported APIs and permissions.
Point of sale
For Square, Toast, Lightspeed, Clover, or another POS, start with the specific question you want answered. Order status, balances, and loyalty information have different access requirements. We’ll review the available data before confirming the connection.
Customer relationship management
Discuss your workflow in HubSpot, Salesforce, Pipedrive, Attio, or Airtable. Decide which details should be saved and when a conversation should create or update a record. Check consent, field mapping, and duplicate handling during setup.
Helpdesk
If your team uses Zendesk, Freshdesk, Intercom, or Help Scout, review how handoffs should reach it. Ticket creation and updates depend on the available integration. Agree the context to include and who owns the follow-up.
// 04 — CUSTOM CONNECTIONS
Build the connection your workflow needs.
Model Context Protocol (MCP)
MCP can provide a way for the chat to call tools exposed by another system. An endpoint still needs compatibility checks, authentication, and a clear list of permitted actions before it can be used.
REST API
Discuss the endpoints needed for your workflow, whether that involves conversations, customer records, or knowledge content. Agree authentication, data formats, and error handling against the current API documentation.
Zapier, Make & n8n
Use an automation platform where the required API or webhook connection is supported. Confirm connector availability and the events you need. Test retries and duplicate handling before enabling actions that change customer data.
// 05 — ROADMAP · AVAILABILITY TO CONFIRM
What we’re exploring next.
Voice calls
Voice is a roadmap area, separate from text chat and voice notes. If phone handling matters to your project, ask about current status and scope. Do not assume it is included or available for launch.
Instagram direct messages
Instagram messaging is a planned area of work. Ask about current testing access and account requirements before planning a rollout; beta access and release timing need confirmation.
Two-way conversations through Slack
This roadmap item concerns staff replying to customer conversations from Slack. It is separate from sending a handoff notification into a channel. Ask which behavior is available for your setup.
Industry-specific connectors
We’re exploring ways to package connections around common industry workflows. Share what would help your team through the roadmap. Planned features are not a commitment to a delivery date.
Have a tool in mind?
Tell us which system you use and what you want the chat to read or do. A link to its API documentation helps. We’ll review the options and agree the scope and timeline before committing to a custom integration.