Skip to main content
Velor

Channel · Email

Forward your support inbox. The agent replies in-thread.

Email is the channel we set up WITH you rather than one you switch on yourself, and it is not generally available yet — talk to us before you plan around it. Once we provision your intake address and confirm DNS, you forward support@yourcompany.com to it; we parse each inbound message, retrieve from your knowledge base, and reply in the same thread, with the same grounding, escalation and resolution tracking as every other channel. Deeper IMAP and provider-level integrations are on the roadmap.

What it does.

Forwarding-based setup

Once your intake address is provisioned, you add one forwarding rule from your support inbox. No OAuth, no provider lock-in, no migration. We confirm DNS with you before you point anything at it.

Grounded replies in-thread

The agent parses the inbound message, runs grounded retrieval, and replies. Message-ID and In-Reply-To headers are preserved so Gmail, Outlook, and clients thread correctly on the customer side.

Branded sender

Replies are sent from a Velor-hosted address for your workspace (support+your-workspace@…) and keep your subject and thread, so the customer's mail client shows one conversation. Sending from your own domain is not available yet.

Attachment awareness (MVP)

Inbound attachments (up to 10 per email, 10 MB each, common image, PDF and document types) are stored on the conversation for your team, and the agent is told they arrived. The agent does not read their contents yet; parsing invoices, screenshots and PDFs into its context is on the roadmap.

How it works on email.

  1. 01

    Inbound email

    Your support inbox forwards to the Velor alias. The message lands on our inbound endpoint over an HMAC-signed webhook.

  2. 02

    Parse + resolve

    Sender is matched against your customer record if identifiable. The message body, thread history, and subject are parsed into turn context.

  3. 03

    Retrieve + generate

    Grounded retrieval runs against your KB. The agent generates a reply, optionally invoking any configured actions scoped to the sender.

  4. 04

    Reply in thread

    The reply is sent via Resend from your workspace's Velor-hosted address, threaded correctly. On escalation, the thread routes to a teammate with context attached.

Built for email-specific needs.

Thread continuity

Every reply carries In-Reply-To and References headers so Gmail, Outlook, and Apple Mail thread correctly on the customer's side. Long threads stay coherent; the agent reads the whole history, not just the most recent message.

Forwarding-based MVP

Today the channel is provider-agnostic by design: any provider that supports forwarding rules works. We lose out on features like server-side draft creation or shared-inbox status that deeper integrations would offer. Gmail-native and shared-inbox integrations are on the roadmap.

Signed inbound

Inbound webhooks from your forwarding provider are HMAC-signed with a 5-minute replay window. Forged email events that don't match the signature are dropped; no injection path into your conversations.

Escalation with thread handoff

When a customer asks for a person, the conversation is escalated and your teammate receives it in Velor's inbox with the full email thread, retrieved knowledge, and any tool results attached. They can reply from Velor or pull the thread back into their own helpdesk.

One agent, every channel

Configure once. Deploy everywhere.

Email runs on the same brain as the rest of Velor — one knowledge base, one set of guardrails, one scoped action schema, one audit trail. Tune a behavior once and every channel respects it. No per-channel re-training, no drift between how the agent answers on the phone versus in chat.

Run it on your own tickets.

Every workspace starts with a 14-day free trial. No credit card. If you want a guided walkthrough against your data, we're happy to run one with you.