Alhena
  • Introduction
  • Getting Started
  • Architecture
  • Reference
    • Website SDK
      • Configure Proactive Nudges
    • Product FAQs
    • Website chatsdk events
    • Website chatsdk APIs
    • Chat SDK api and events examples
      • Open other external widget once human transfer is initiated
      • Show the Alhena AI widget only when someone scroll the page by 5 px
    • Website SDK - Custom data
      • Website SDK - Customer data with Agent
    • Website SDK - Internationalization
    • API Reference
      • API calls
    • Device Compatibility
  • Tutorials
    • AI Training
      • Training Steps
      • Training Data Sources
        • Websites
        • Youtube videos
        • Google Drive
        • Twitter Pages
        • Discord Messages
        • Confluence Pages
        • Upload Documents
        • Github
        • Zendesk Tickets
        • Freshdesk Tickets
        • Freshchat Tickets
        • Custom data sources
        • Shopify API
        • Woocommerce API
        • PDF Crawling
      • Training Frequently Asked Questions
    • Tuning Alhena AI Post Training
      • Best Practices for configuring the Alhena AI’s personality and guidelines
      • Adding Human Feedback for improving specific Questions
      • Adding to your knowledge base with FAQs
      • Frequently Asked Questions - Tuning Responses
    • QAing Al Conversations
      • Smart Flagging: Streamline Your AI Quality Assurance
    • Integrations
      • Alhena Website Chat SDK
        • Customizing Your Alhena Chat Widget
      • Integrating Alhena AI With Slack
      • Integrating Alhena AI With Discord
      • Integrating Alhena With Freshdesk
      • Integrating Alhena AI With Zendesk
      • Integrating Alhena AI With Email
      • Integrating Alhena AI With Shopify
      • Integration Alhena AI With Trustpilot
      • Integrating Alhena With Gorgias
    • Notifications
    • Alhena Dashboard
      • Managing Team
Powered by GitBook
On this page
  • Configuring Email Support
  • Human Transfer
  1. Tutorials
  2. Integrations

Integrating Alhena AI With Email

Gleen AI can connect to your support email account on Gmail, Outlook, or other email providers, where you can then respond to tickets that need human attention through Gleen Ticketing.

PreviousIntegrating Alhena AI With ZendeskNextIntegrating Alhena AI With Shopify

Last updated 1 month ago

If you have a support email account and aren't already using a ticketing solution such as Zendesk or Freshdesk, then Alhena can directly connect to your email account.

Configuring Email Support

First, from the Alhena Dashboard, navigate to the Settings page and click on Integrations. Now, click on "Connect" under Email Support.

Confirm that the email account you intend to connect is a dedicated support email address. You shouldn't connect your personal account, as Alhena will automatically start replying to incoming messages once connected.

Enter your support email address and click Log In.

Now you'll be directed to your email provider to finish the authentication process.

Once completed, the integration is complete and your bot will handle any incoming customer questions sent to this email inbox.

Alhena will not respond to any emails that were created before the integration was set up, only new emails received after the setup was completed.

Human Transfer

Gleen will attempt to answer any questions based on your knowledge base, but will stop responding and let a human agent take over when needed. There are a few cases where Gleen will stop responding.

  • The user asks for a human agent, i.e. they type "I want to talk to a person" or something similar.

  • The bot wasn't able to find an answer in its knowledge base.

  • You sent a response to the customer directly from your email account.

For any tickets that need a human response, all admins and bot profile members will receive an email notification. You will see these tickets listed in the "Unassigned" tab on the Conversations page.

Gleen will ignore any email messages we suspect as being from some automated system, rather than an actual customer inquiry.

A custom rule you've added in the for your bot was triggered.

answering guidelines