How your AI Employee handles customer conversations
Summary
The AI Employee processes incoming messages, checks its knowledge base, formulates a response based on your tone settings, and decides whether to reply, ask a qualifying question, or trigger a human handoff.
Who this article is for
This article is for business owners and managers who want to understand the conversational logic of the AI Employee.
Overview
Before you begin
- Review your AI's primary objective
- Understand the difference between a direct answer and a qualifying question
Step 1: Step 1: The Initial Inquiry
Step 2: Step 2: Knowledge Retrieval
Step 3: Step 3: Rule Evaluation
Step 4: Step 4: Response Generation
Step 5: Step 5: Waiting and Replying
Configuration note
We do not guarantee AI accuracy, lead conversion, bookings, customer satisfaction, response quality, revenue, support resolution, or business outcomes. The AI Employee does not fully replace human staff. AI behaviour depends on knowledge sources, instructions, handoff rules, enabled features, connected channels, permissions, configuration, testing, and ongoing monitoring. AI-generated responses should be reviewed before relying on them for sensitive, urgent, legal, financial, medical, billing, or policy matters. The AI Employee may need human handoff for these situations. Knowledge sources must be reviewed, updated, and tested regularly. Usage charges, feature access, fair use rules, or add-on requirements may apply depending on your account setup. Always test before going live. Contact support if an option is not visible. The AI maintains context within a single conversation thread. It remembers what was said three messages ago, allowing for natural, multi-turn conversations.
Important clarification
Assuming the AI will aggressively push for a sale. The AI is designed to be helpful and conversational. If you want it to push for appointments, you must explicitly set that as its primary objective.
Resolution guidance
Why did the AI stop replying in the middle of a conversation?
It likely hit a human handoff trigger (like detecting frustration or a restricted keyword) and went into 'sleep' mode for that contact, waiting for a human to take over.
Was this article helpful?
Need account-specific help?
If your question requires account access, billing review, workflow inspection, message delivery diagnosis, AI response review, or private configuration review, submit a support request with examples and screenshots.
