Skip to main content
The AI can work on email your Genesys email route receives, in one of two ways. It’s off by default.
  • Suggestions only: the AI writes a suggested reply on each email in a queue your agents already work. Your routing doesn’t change, and the AI never sends or moves anything.
  • The AI answers: Genesys has no bot step for email, so the email waits in a queue with no agents while the AI answers, then moves to a human queue if it hands off.

Suggestions only

Open the Channels tab, then Native email. Turn on AI answers Genesys email, set AI replies from to Suggestions only, agents send, choose the Queue to watch and how each suggestion arrives, then press Save. You must go live first.
  • Every email is mirrored: each email in the queue becomes an OpenCX session with the customer’s messages and your agents’ replies, in order.
  • Suggestions stop when the email leaves the queue: once an agent takes the email or it moves to another queue, the session gets an internal note and the AI writes no more suggestions for it.

The AI answers

The AI follows your email Autopilot setting. With autopilot off, email goes to your agents with no AI reply. You must go live first. Email waits in your own queue while the AI answers, held by a skill no agent has:
  1. In Genesys, create a skill such as OpenCX AI and give it to no one. On your email route, add it under Skills. Your agents aren’t offered the email while it carries the skill.
  2. In OpenCX, open the Channels tab, then Native email. Turn on AI answers Genesys email, choose that Hold skill and the Queue your route sends to, choose where AI replies come from, and press Save.
  • The AI answers: the reply goes out and the email stays held, so the AI also answers the customer’s next email in the thread.
  • Handoff: OpenCX takes the hold skill off and Genesys offers the email to your agents, with opencx_summary and opencx_transcript. Your routing and other skills stay as they are.
  • No answer: an email the AI hasn’t answered three minutes after the customer wrote goes to your agents the same way.
  • If OpenCX can’t reach Genesys: held email waits. To have Genesys release it on its own, use bullseye routing on the queue and remove the hold skill on a later ring.
Without a hold skill, OpenCX creates a queue called OpenCX AI and your route points there instead. Genesys may refuse to move email out of that queue, so prefer the hold skill.
  • After a handoff the AI stops replying. So does an email Genesys moves on its own.
  • Agent replies: Genesys sends them. They appear on the session and OpenCX never sends them again.
  • Inbox replies: a teammate’s reply goes out like the AI’s, in the same thread, while no agent holds the email in Genesys. Once one does, the composer says Reply in Genesys.
  • Cc: a teammate’s reply with Cc goes from your support address, since Genesys sends agentless email to one recipient only. If that address can’t send it, the reply goes to the customer alone through Genesys.
  • Formatting: replies go out with their formatting, and with a plain-text version that keeps paragraphs, lists and link addresses. Links in your agents’ emails stay on the session.
  • Auto-replies: an email your flow sends before any agent is on the email, such as an auto-reply, appears as a workflow message. The AI keeps the session.
  • Automated senders: email from addresses such as noreply@ or mailer-daemon@ appears on the session, but the AI doesn’t answer it and Session created workflows don’t run.
  • Signature logos: small inline images, such as a logo in an email signature, aren’t added to the session.
  • Assist mode: the email goes straight to the human queue with the draft in opencx_suggested_reply.
  • A reply that can’t be sent: the email goes to the human queue with the text in opencx_undelivered_reply.
  • Queue reports: time the email waits for the AI counts in that queue’s Genesys reports.
If you connected before this feature, reconnect so the role gets conversation:agentlessEmail:send and routing:queue:add.