CC Gent
Copy Gent when an email should become work.
A Gent inbox does not always need to be the main sender or recipient. Copy it on a thread when you want the conversation, attachments, follow-up, labels, reminders, and workflow events to be tracked without changing how people already email.
The mode
Gent can observe the thread without owning the conversation.
Some work starts in a human inbox, a client mailbox, or another team system. CC mode lets Gent receive the same message as an address on the thread, then use that copy as workflow input.
Keep the human thread
People continue using their normal email addresses while Gent receives the messages needed for tracking and follow-up.
Preserve context
The sender, recipients, subject, attachments, labels, and thread history stay connected to the work that comes out.
Avoid forwarding sprawl
Instead of building hidden forwarding chains, add the Gent inbox where the work should be visible and reviewable.
Use explicit participation
The Gent address is copied on the thread, so the workflow surface is visible in the same email context.
How it works
A copied email becomes a tracked signal.
CC
Add a Gent inbox to the email thread when the conversation needs tracking, follow-up, intake, or workflow handling.
Receive
Gent receives its copy and treats the real sender and recipients as the relationship context, not the Gent mailbox itself.
Classify
Labels, rules, and optional enrichment can detect what the message is about, such as a client request, vendor document, approval, or missed follow-up.
Act
The inbox can create a task, schedule a reminder, save an attachment, send a webhook, update contact context, or prepare a draft.
Review
If a response or action needs judgment, Gent can hold it for approval instead of acting automatically.
Use cases
Use CC mode when the work starts in someone else's inbox.
Client follow-up
Copy Gent on client threads so open loops become tasks, reminders, drafts, or webhook handoffs.
Vendor intake
Copy Gent when invoices, files, or requests need to be stored, routed, or reviewed without moving the whole vendor mailbox.
Approvals
Copy Gent on a request thread so approval status, decisions, and follow-up stay attached to the conversation.
Project memory
Copy a project inbox when important decisions should become searchable context for tasks, labels, contacts, and workflows.
When not to use it
Use a dedicated Gent address when Gent should own the work.
CC mode is useful when humans or another system keep the main conversation. Use a dedicated Gent inbox when an agent, workflow, client mailbox, or vendor address should receive, prepare draft actions, and own the work from the start.
Use CC mode
When the thread already exists elsewhere and Gent only needs enough context to track, route, remind, or prepare work.
Use a Gent inbox
When the agent or workflow should be the address people contact directly.
Use forwarding
When another mailbox should automatically send a class of messages to Gent without asking people to remember the CC.
Use a help desk
When the main job is human support queues, SLA management, and many-agent ticket operations.
Why it matters
The copy should create an operating record, not another inbox to watch.
Most copied email just adds noise. Gent uses the copy to update the work graph around the thread: contacts, labels, tasks, reminders, files, events, approvals, and audit history.
Relationship-aware
Gent can treat the relationship as the people in the conversation, not the mailbox copied for workflow.
Workflow-ready
Copied messages can trigger the same workflow primitives as direct inbound email.
Reviewable
Actions, drafts, approvals, and webhooks stay attached to the inbox that received the copy.
Incremental
Start by copying Gent on one type of thread before moving that workflow to a dedicated address.
Next step
Give the delegated work its own address.
Start with one workflow that should no longer borrow a human inbox: vendor intake, client follow-up, support escalation, or agent-managed approvals.