Feature Requests

it would be REALLY useful to have an address book function, or a link to google/apple contacts, for the email within in a task. It is a bit of a pain having to find the email addresses elsewhere and then copy & paste

An Inbox for your Email in ClickUp! You'll be able to see all of your emails and replace your email inbox with ClickUp. You'll also be able to quickly link and create tasks, docs, and more to emails.

At the moment, no attachments are displayed for sent emails, even if they have been sent. That's really stupid and I think it's simply a bug, but support said it was “not a bug, it was a design.” Whatever: You must be able to see what you've sent, including attachments! Otherwise, you have to go out into the external mail program to check whether the attachment has been sent along with it, and it is precisely this tool change and the manual check that is completely against the ClickUp approach.

I really hate that I always have plenty of Company Logos within my task attachements. Please stop that.

Duplicate emails appear in tasks when I attach a link to a task in an email correspondence. Each reply in the same thread is copied as a separate comment/attachment, which causes a mess. Is it possible to somehow limit or deduplicate it?”

When sending an email to a mailing list to create a task, you should copy the images contained in the task description instead of just referencing the image, as this doesn't allow for task review. I've attached a screenshot as an example.

From support ticket: Ability to 'Schedule Send' emails

Overview ClickUp should offer a native helpdesk/ticketing system that integrates directly with email and allows teams to manage client communications as tasks — eliminating the need for third-party helpdesk tools like Help Scout, Zendesk, or Freshdesk. Key Features Email Integration & Ticket Intake Authenticate ClickUp with your support inbox (e.g., support@domain.com ). When a client sends an email, it automatically: Converts into a task. Drops into a predefined folder/list based on custom routing rules (workspaces, tags, email address, etc.). Assigns the task to the correct assignee/team based on smart routing or manual rules. Two-Way Email Communication Users can reply to the client's email directly within the ClickUp task. Responses are sent as replies to the original thread. Optional: Add internal comments not visible to the client. Client responses get appended to the same ClickUp task/thread. Automation & Templates Support for auto-reply triggers, e.g.: "We’ve received your request. A ticket has been created." Use automation to: Set SLAs or due dates. Add custom fields like “Priority,” “Client,” or “Ticket Type.” Trigger reminders/escalations. Client View Portal (Optional) Option to generate a client-facing view or portal (lightweight) showing: Open/closed requests. Status updates. Response history. Smart Workflows Enable mapping based on custom logic: “If email contains ‘urgent’ → assign to John.” “If email from xyz.com → tag as VIP.” Integrate with Goals, Docs, and Dashboards for full visibility. Why This Matters ClickUp is already powerful for internal project management — this closes the loop by turning it into a client-facing support hub. Agencies, SaaS companies, and service teams want fewer tools, not more — and this would keep client operations centralized within ClickUp.

Overview: The current implementation of email integration within ClickUp tasks, while innovative, results in significant clutter due to the inability to auto-collapse long email threads. This issue is exacerbated when email threads include images, leading to an overwhelming and disorganized comments section. The proposed feature aims to introduce a simple yet effective solution to enhance the management and readability of emails within task comments. Technical Proposal: Introduce a customizable email thread termination marker, designated as "//CUEND". This marker will serve as a parsing delimiter within the ClickUp system. When an email containing this marker is forwarded to a ClickUp task, the system should parse and display only the content above "//CUEND". Subsequent replies to such emails would include the marker, ensuring that only the new response and the content immediately preceding "//CUEND" in the original email are parsed and displayed in the task comment. Benefits: Reduced Clutter: By limiting the displayed content to only the most recent and relevant portions of an email thread, this feature significantly reduces clutter in the comments section. Enhanced Readability: Improves the readability and usability of task comments, enabling team members to quickly identify and focus on pertinent information. User-Controlled Flexibility: The placement of "//CUEND" is controlled by the user, providing flexibility in determining how much of the email thread is relevant for inclusion in the task comment. Easy Adoption: Users can seamlessly incorporate the marker into their email signatures or standard practices, facilitating widespread adoption and consistent usage across teams. Implementation Considerations: Ensure compatibility with various email formats and clients. Provide user guidance and best practices for implementing and using the "//CUEND" marker effectively. Consider the potential for future enhancements, such as automatic insertion of the marker for emails exceeding a certain length.