I Forwarded a Screenshot. The Task Marked Itself Done.

Our email provider approved our account and sent setup instructions. I forwarded that email to Project Campfire. A task appeared: "Verify domain with DKIM if needed for sending emails."

I configured the DNS records. Then I replied with nothing but a screenshot showing the verification was complete.

The task moved to Done. Campfire looked at the image, understood what it showed, and matched it to the pending task.

"No clicking. No dragging. Campfire understood the screenshot."

The Setup: Account Approval

After applying for account approval, our email provider sent this:

Good news - your account has been approved!

Your application to send has been approved and your account is now in live mode. Here are your next steps to start sending:

1. Sign up for an API or SMTP message stream (if you haven't already). Broadcast (bulk) or Transactional? Use the stream type that fits your use case.

2. Verify your domain with DKIM. Domain authentication protects your sender reputation and improves deliverability.

Standard vendor onboarding. A simple task, really—but one that usually requires a small context switch: read the email, add it to your task list, do the work, remember to check it off.

Step 1: Forward the Email to Project Campfire

I forwarded the email to our project's unique inbox. Within seconds, a task card appeared on our board:

"Verify domain with DKIM if needed for sending emails"

Campfire read the email, identified the action item about domain verification, and created a trackable task. It even added context about why this mattered (account approval, sending emails).

Step 2: Configure the DNS Records

I logged into our DNS provider and added both records required for email authentication:

• DKIM TXT record — For email authentication
• Return-Path CNAME — For bounce handling

Then I waited for DNS propagation and watched both records verify in the dashboard.

Step 3: Reply With Just a Screenshot

Here's where it gets interesting. When I replied, I didn't write a detailed status update. I didn't list what I'd done. I just forwarded a screenshot of the DNS Settings page showing:

• DKIM: Verified (green checkmark)
• Return-Path: Verified (green checkmark)
• A banner confirming: "Your domain is verified! You're now able to send from any email address on your domain."

That's it. One image. No accompanying text explaining what the image meant.

The Magic: Visual Understanding

Campfire didn't just process text—it understood the screenshot:

1. Recognized the context — This was a DNS Settings page
2. Read the verification status — Both DKIM and Return-Path showed "Verified"
3. Connected it to the pending task — The task was about DKIM verification
4. Marked the task complete — Because the screenshot proved the work was done

The task card moved to Done with context explaining that domain verification was confirmed.

Why This Matters

This demonstrates something different from automation that looks for keywords or requires explicit status updates:

Understanding, Not Pattern Matching

Campfire didn't find the word "done" and mark the task complete. It analyzed a screenshot, understood what the visual elements meant, and matched that evidence to the pending task.

Your Communication IS Your Status Update

I was already going to reply—that's just normal communication. I was already going to include evidence that the setup was complete. Now that same reply automatically updates my project board. No extra work.

Evidence-Based Completion

The task didn't close because I said "done." It closed because I provided visual evidence that the work was actually complete. The green checkmarks in the screenshot proved the DNS records were verified.

Zero Manual Task Management

From email to task to completion—I never touched the project board directly. Campfire handled extraction, tracking, and completion automatically. I just did my normal work and communicated normally.

The Broader Pattern

This isn't just about email providers or DNS configuration. It's about how real work happens:

• A vendor sends instructions → Forward to Project Campfire → Tasks appear
• You do the work → Reply with evidence (screenshot, confirmation, etc.)
• Campfire understands the evidence → Tasks update automatically

Your email thread becomes your project history. Your replies become your status updates. Your attachments become your proof of completion.

Try It Yourself

1. Create a project in Project Campfire
2. Forward an email containing action items or setup instructions
3. Watch tasks appear automatically
4. Complete the work
5. Reply with evidence (screenshot, confirmation email, etc.)
6. Watch the relevant tasks update

No clicking around in a project manager. No manual status updates. Just do your work and communicate like you normally would.

---

Frequently Asked Questions

Does it really understand screenshots?

Yes. Campfire processes images and extracts meaning from them. A screenshot showing "Verified" status, a confirmation page, or a completed form can all serve as evidence of task completion.

What if I prefer to write status updates?

That works too. You can reply with text describing what you did, and Campfire will match that description to the relevant tasks. Screenshots are just one type of evidence it understands.

What types of emails work best?

Any email containing action items, requests, deadlines, or commitments. Vendor onboarding, client requests, internal project updates, meeting follow-ups—if someone needs to do something, forward it.

What if Campfire makes a mistake?

You can always manually adjust card status. You maintain full control over your project board. Campfire is a helpful assistant, not a replacement for human judgment.

Is my email content secure?

All email content is encrypted in transit and at rest. Only project members can see extracted tasks and the original message content. We never share your data with third parties.