AI Employee final launch checklist

    CategoryAI Employee
    Article typeDocumentation
    Estimated reading time 5 min
    Last reviewedRecently reviewed
    Applies toGEVADE CRM accounts where the feature is enabled
    Access requiredAccess may depend on your user permissions
    Plan/configuration noteFeature availability may depend on your selected plan and account configuration

    Summary

    Before going live, verify your business profile, calendar settings, knowledge base, business rules, human handoff triggers, and complete a full simulation test.

    Who this article is for

    This article is for administrators preparing to activate the AI Employee on live communication channels.

    Overview

    Launching your AI Employee to the public is a significant step. This final checklist ensures you have configured all necessary safeguards, training data, and routing rules to provide a seamless customer experience.

    Before you begin

    • Verify Business Profile and Timezone
    • Check Calendar availability and conflict settings
    • Confirm Knowledge Base is synced
    • Test Business Rules and Fallback responses
    • Verify Human Handoff routing
    • Complete a full simulator test

    Step 1: Step 1: Core Settings Check

    Ensure your GEVADE CRM Business Profile is complete, the timezone is correct, and your team calendars are properly configured to prevent double-booking.

    Step 2: Step 2: Knowledge Base Verification

    Review the Knowledge Base tab. Ensure all URLs are accessible, old documents are removed, specific FAQs are added, and you have clicked 'Sync'.

    Step 3: Step 3: Rules and Boundaries Check

    Review your Business Rules. Confirm that restricted topics are clearly defined, the fallback response is polite and helpful, and you have explicitly forbidden the AI from guessing.

    Step 4: Step 4: Handoff and Escalation Check

    Verify your Human Handoff triggers. Ensure that when a handoff occurs, an internal notification is routed to the correct team member or Slack channel so the customer isn't left waiting.

    Step 5: Step 5: Tone and Formatting Check

    Review your Custom Instructions. Ensure the AI is instructed to be concise, maintain context, and use formatting (like bullet points) when appropriate.

    Step 6: Step 6: The Final Simulation

    Use the AI Simulator to run through a 'happy path' (e.g., booking an appointment), an 'edge case' (asking a vague question), and a 'failure path' (asking about a restricted topic). If all tests pass, you are ready to launch.

    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. Start small. Consider launching the AI on a single channel (like Web Chat) before enabling it on high-volume channels like SMS or Facebook Messenger.

    Important clarification

    Skipping the final simulation test. Testing is the only way to verify that your rules, knowledge, and tone instructions are working together correctly.

    Resolution guidance

    I launched, and the AI immediately made a mistake.

    Don't panic. Pause the AI, review the conversation log to identify the root cause, update the knowledge base or rules, sync, test, and re-enable.

    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.