4chaty integrations

Email & Calendar

Whatever gets decided in the conversation lands in your team's mailbox and calendar on its own — no copying between screens.

Team notifications go out through 4notify — every escalated conversation reaches email, SMS or push instead of sitting unread.

Bookings asked for in conversation land in 4appointments.net, and the confirmation comes back into the chat.

Customer communication

The assistant answers on your site today, through the web widget; the WhatsApp and Messenger integration is in the works — one knowledge base, the same refusal and escalation rules, one shared team inbox.

You won't set up your FAQs three times: every channel will read the same knowledge base and every answer will cite the same source.

Notifications and transactional messages for the callbacks you promise outside working hours will go out through 4notify.net (email, SMS, push) — coming soon.

Once the messaging channels launch, your team will see the full thread — site, WhatsApp, Messenger — in one place, whichever channel it started on.

Automations & migration

Escalation and request-type routing rules run natively inside 4chaty. Zapier and Make connectors, for custom no-code flows, are coming soon.

The knowledge base is built today from your own site pages, your uploaded documents and the FAQs you write. Moving questions and macros over from Intercom, Tidio, Zendesk or Crisp is done by our team together with you; an automated importer is in the works.

Built-in rules (escalation, routing by request type) run natively, so core flows depend on no external connector.