How does Skai Chat differ from a button-based bot?+
The assistant converses in natural language, uses company materials and follows a defined objective. Communication rules, available actions and employee handover remain configurable. Button-based flows can suit simple choices, while AI handles more varied wording.
What can we upload to the knowledge base?+
The original product supports PDF, DOC, TXT, CSV, images and a separate product catalogue. Materials are linked to the appropriate assistants. Before launch, we check that sources are current, consistent and answer customers' main questions.
When does the assistant hand over to a human agent?+
At the customer's request, for complex or negative enquiries, when no adequate answer is available, or according to your rules. The employee receives the history and can continue the conversation. During setup, we define owners, handover conditions and actions outside team working hours.
Can we create several assistants for different departments?+
Yes. Sales, support, HR or individual products can have different roles, objectives, instructions and knowledge sources. Assistant counts depend on the plan. Access to materials and channels is organised according to each scenario's needs.
How are CRM, messaging and calendars connected?+
The product lists Bitrix24 and amoCRM, Google Calendar and Calendly, and messaging services, including through Wazzup. During implementation, we verify your configuration, permissions and available operations. Additional services and custom logic are assessed separately.
What counts as a conversation under a plan?+
A conversation is a chain of communication with one customer within a session. Before connecting, check the current plan in your account for session ending and resumption rules, human handover accounting and additional volumes. The stated limit applies to conversations, not individual messages.
Can Skai Chat be hosted on our company's infrastructure?+
Private cloud or on-premises hosting can be considered for enterprise projects. Solution scope, model access, integrations, data storage and support are agreed separately. Information security requirements and permitted external calls must be defined before architecture selection.
How long does launch take and what determines the cost?+
A basic scenario can be configured faster than a project involving several departments and integrations. Timelines depend on knowledge readiness, channel and action counts, quality requirements and hosting. A trial plan is available for independent exploration; company implementation scope is agreed separately.
Can we send campaigns and automatic reminders?+
Yes. You can prepare a template with variables, define a segment and configure an event- or condition-based trigger. For example, confirm a booking, remind someone of a visit, follow up an unfinished enquiry or invite a customer back. Each channel's sending capabilities, provider restrictions and recipient consents are considered.
How do surveys and feedback collection work?+
You create questions, choose an audience and period, then connect the survey to a notification rule. Surveys can follow a purchase, visit, cancellation or support enquiry. Responses inform service analysis, and a low rating can trigger employee handover.
Can we create our own dashboards?+
Yes. Describe the service metrics you want to see: enquiries by channel, bookings, survey results, human handovers or trends over a period. You can build separate dashboards and change widget contents and placement. External CRM data must first be connected and mapped.
How do we update knowledge and manage workflows?+
Materials are linked to the appropriate agent. Alongside document uploads, you can configure Google Docs and Sheets synchronisation, choose active sources and check processing status. Workflows define instructions, priorities and usage conditions. Test changes in a trial conversation before using them in live channels.