Email Workflows for Every Scenario

Real-world examples to help you choose the right workflow for your situation.

Add Emails to Existing Tasks

Most tasks already exist when the emails start flying.

You've got a task. Now you've got an email about it. Every other tool either creates a duplicate or makes you copy-paste.

Paste the task URL in your subject line. Casso adds your email as a comment. Done.

1Copy the task URL from ClickUp, Asana, Monday, or Jira
2Paste in the subject line when you forward the email
3Email becomes a comment on the existing task

After the first email:

Casso gives you a ticket:xxxx ID. Use that for future emails to the same task. No URL needed.

"Most often, project tasks are already created by the time email communication is happening. The inability to add an email or multiple emails to the relevant task without creating a new task really defeats the efficiency of this automation."

— mikedfarrell, Asana Forum

See how it works
Just Forward It
Easy Mode
Got an email? Forward it. That's it. I do this one a lot.
The Sneaky One
Nobody Knows
BCC means they can't see it. I learned that the hard way.
The Fancy One
Full Auto
This one does everything automatically. I barely have to think. Which is good.
1. Client Support ThreadThe Fancy One
Why this workflow

Full automation, client doesn't care about seeing Casso in CC

Example
  1. 1Send email to client@company.com, CC org@mail.casso.app
  2. 2Subject: ticket:4821 Website revision feedback
  3. 3Client replies all → auto-routes to ticket
  4. 4Thread continues, ticket stays updated
2. Lawyer / Legal CorrespondenceThe Sneaky One
Why this workflow

Privacy, attorney-client privilege, you control what's logged

Example
  1. 1Send email to attorney@lawfirm.com, BCC org@mail.casso.app
  2. 2Ticket created with AI summary
  3. 3Attorney replies (doesn't see Casso)
  4. 4You forward reply with ticket:xxxx in subject
  5. 5Ticket updated, full thread preserved
3. Vendor NegotiationsBCC → CC after deal signed
Why this workflow

Keep leverage during negotiation, automate during execution

Example
  1. 1Negotiations: BCC all emails, forward replies manually
  2. 2Contract signed: Switch to CC + ticket:xxxx for project execution
  3. 3Full history preserved, no gaps
4. Internal Team ThreadThe Fancy One
Why this workflow

Everyone's on the same system, full transparency

Example
  1. 1Email team with Casso in CC
  2. 2Discussion threads auto-update the ticket
  3. 3Anyone can check ticket for full context
5. Bug Report from UserJust Forward It
Why this workflow

One-off, no ongoing thread expected

Example
  1. 1User emails bug report
  2. 2Forward to Casso
  3. 3Ticket created, assigned, tracked
6. Contractor / Freelancer ProjectsThe Fancy One
Why this workflow

Create audit trail, contractor sees the system

Example
  1. 1Email contractor with project brief, CC Casso
  2. 2All back-and-forth logged automatically
  3. 3Deliverables tracked, timeline visible

Ready to get started?

Start with our free tier. No credit card required.

Get Started FreeView Pricing