Email routing

Email remains one of the channels customers use most for anything that needs a paper trail: complaints, claims, documents, account changes and formal requests. Yet in many organisations it still lives in shared mailboxes, where messages are cherry-picked, duplicated or forgotten and nobody can say how long a customer has been waiting. Genesys Cloud email routing brings that work into the contact centre proper. Each message becomes an interaction with an owner, a queue, a priority and a service level, and it is reported alongside voice and digital contacts so leaders see the whole workload in one place.

The benefit reaches both customers and employees. Customers get an acknowledgement straight away and a reply within a promised time. Agents get a steady, fair flow of work instead of an overflowing folder, with the history and tools they need on screen. Workforce planners can forecast email demand and schedule for it. QVCCS starts every email engagement by understanding what your customers write to you about, how quickly each type of request really needs an answer, and which teams are best placed to respond – then designs the routing to match.

Inbound email on Genesys Cloud CX is designed in Architect. An organisation can hold up to two email domains with up to 1,000 addresses on each, and every address is routed either directly to a queue or through an inbound email flow. The flow can examine the sender, address, subject and body, read header fields with the Get Email Headers action, detect intents through its natural language understanding settings, look up customer data through data actions, set priority and skills, and transfer the email to the right ACD queue. The Send Auto Reply action confirms receipt and sets expectations. Unlike call flows, inbound email flows have no automatic failure path, so error handling has to be designed explicitly for every action.

Once queued, emails are offered by the ACD using the same routing and evaluation methods as calls and messages, considering skills, language, priority and utilisation. Agents reply from the Genesys Cloud workspace with canned responses, attachments and the previous thread. Replies go through the Genesys Cloud mail service by default or through your own server with the custom SMTP integration, and custom IMAP and Microsoft Graph integrations let Genesys Cloud receive mail from your existing estate. Encoded outgoing messages, attachments included, are limited to 40 MB, so large documents are shared as links. QVCCS configures each component, documents how they fit together in the LLD, and aligns your domains, DNS records and mail routing with the design.

The hardest email problems are rarely technical. They are about classification and ownership. Should a reply to an existing case go back to the agent who handled it, or to the next available person? How do you stop an out-of-office reply from creating a new interaction, or a long thread from bouncing between teams? Which messages deserve priority, and how are attachments, large files and suspicious content handled? QVCCS works through these questions with your operations and IT teams and turns the answers into clear, testable routing rules inside the inbound email flow.

Service levels need equal care. A two-hour target for complaints and a two-day target for general enquiries require different queues, priorities and reporting, and supervisors need to see ageing work before it breaches. We define email SLAs per queue, set priority so the most time-sensitive messages surface first, and build performance views that show backlog and age at a glance. We also plan utilisation carefully, so an agent working email can still be interrupted for a call where your operating model calls for it.

Security and compliance shape the design too. Email often carries personal data and documents, so we agree with your information-security team which content may be stored, how long it is retained, who can see it and how sensitive attachments are treated. For custom domains, SPF and DKIM are configured and DMARC aligned so replies are trusted by recipients' mail systems, and a domain allowlist can restrict which recipient domains agents may email where policy requires it. Every decision is written into the low-level design and the design decision log, giving your administrators a reference that explains not just how the email routing is configured but why.

Email routing touches your mail infrastructure, DNS, security policy, CRM and contact centre operations, so the team we bring from our own bench spans all of them. A Senior Business Consultant / Business Analyst analyses current mailboxes, volumes and request types and agrees the target operating model. A Solution Architect produces the HLD and LLD for addresses, flows, queues, skills, SLAs and integrations. An IT Systems, Telecoms & SIP Engineer handles domains, MX, SPF, DKIM and DMARC records and SMTP, IMAP or Graph connectivity with your mail team, while a Senior Developer builds the inbound email flows, data actions and canned response libraries. Our Systems Integration Tester sends messages from different mail clients, with and without attachments, as new contacts and as replies, and deliberately triggers out-of-office loops, oversized attachments, malformed headers and failed lookups.

Moving off shared mailboxes needs its own plan. Emails already in flight at cut-over must have a clear owner, so we agree whether open items are worked down in the old mailbox or imported as interactions. Forwarding rules and DNS changes are timed so that no message falls between the two, with record lifetimes reduced in advance. Auto-replies need loop protection, because two systems acknowledging each other can generate thousands of messages in minutes. Signatures, disclaimers and the reply-to address should be consistent across every queue, so customers reply to an address that is routed. And mailboxes are moved in phases, smallest first, with a rollback plan, so lessons from the first move improve the next ones.

Email demand changes with every product launch, billing run and policy update, so the routing needs regular attention. We review queue performance and ageing with you, refine classification rules and intents as new request types appear, and keep canned responses current with your content owners, because a response library that is out of date quietly spreads wrong answers. Release readiness reviews track how Genesys Cloud CX evolves its email capabilities, and support and maintenance follow your Genesys Cloud CX support model, inside your provider's service or under a direct SLA with monitoring of flows, integrations and mail delivery. When you are ready, we extend the channel with AI, from intent detection that improves routing to suggested replies that shorten handling time.