The Email Integration within Dobbin:
🔸 Overview
• Captures the exact email threads you choose to teach it via CC or BCC, securely receiving the email body and any supported attachments as a learned resource in your knowledge base.
🔸 Value
• Synthesizes temporal, conversational context—like "commitments-in-passing" and client feedback—directly from your inbox by ingesting both the dialogue and its attachments simultaneously so Dobbin can reason across the entire unified thread.
🔸 Setup
1. Generate a unique email address for your bot instance.
2. Sync the address to a specific channel, multiple channels, or global knowledge.
3. CC or BCC that address on any email to automatically ingest its content and supported attachments into those channels.
🔸 Security
• Accepts emails only from registered, authenticated Dobbin users to maintain security and keep your knowledge base clean.
• Routes inbound emails exclusively to your dedicated, isolated bot instance.
• Extracts text and generates visual previews securely by passing attachments through Dobbin's shared file-processing pipeline.
🔸 Technical Safeguards & Edge Cases
• Sends a polite bounce-back notification automatically to the original sender if a bot instance cannot be found or delivery fails, ensuring no critical communications fall into a black hole.
• Uses email thread headers (like Message-ID and In-Reply-To) to ensure thread stability and consolidation across replies, preventing messy duplicates in the knowledge base.
🔸 Good Prompts
• "Consolidate all the feedback on [campaign] scattered across our forwarded email replies into one themed list, so nothing gets lost between rounds."
• "For the {x} negotiations captured via email, show me how the terms evolved — what we opened at, what we landed on, and where we gave ground."
• "Before my call with [partner], brief me on everything they've said across our CC'd email threads — asks, complaints, and anything I promised."
• "Pull every deadline I've committed to by email, across all clients, into one view of what's due and to whom."
🔸 Bad Prompts
• "Did the client reply yet?"
Why it fails: Dobbin reasons over what has been explicitly ingested, not watching your live inbox. It is a snapshot, not a mail client—asking it to check for new mail mistakes what the integration is.
• "Summarize the thread."
Why it fails: Email is many-to-many, so "the thread" and "they" are ambiguous the moment you have more than a couple of threads going.
• "Why did we decide to kill the campaign?"
Why it fails: If the decision happened on a call or in Slack that was never CC'd, the reasoning simply isn't in the corpus. Dobbin will either stall or stitch together a plausible-but-invented rationale from adjacent emails.
🔸 FAQs
• Q: How are email threads and replies handled?
A: Dobbin uses email thread headers (like Message-ID and In-Reply-To) to keep your email threads organized and stable across replies, preventing messy duplicates in your knowledge base.
• Q: Can I send attachments via email?
A: Yes. When you email files like PDFs or presentations, Dobbin automatically extracts the text and generates visual previews so the AI can "see" and reason about the attachments alongside the email text.
• Q: Who can email the bot?
A: To maintain security and keep your knowledge base clean, the integration only accepts emails from registered, authenticated Dobbin users.
• Q: Can I control who has access to the emails I forward?
A: Yes. When generating your unique email address, you can map it directly to a specific Slack channel. Only members of that channel will be able to query and access the ingested emails.
• Q: What happens if I send an email to the wrong bot address or it fails to deliver?
A: Dobbin has built-in failure handling. If the system hits a delivery error or cannot locate your specific bot instance, it automatically sends a polite bounce-back notification to the sender so no critical communications fall into a black hole.