FAQs: Dobbin and Other AIs; Claude, ChatGPT
Dobbin vs. Other AIs: What's the Difference?
How is Dobbin fundamentally different from tools like ChatGPT or Claude?
When people use separate AI tools, valuable knowledge stays trapped in their individual chats where nobody else can benefit. Dobbin connects your whole team to a shared system that pulls from your live integrations and organizes information by channel. This ensures everyone gets access to the right company knowledge based on the channels and permissions your team has set up.
We already pay for enterprise seats on Claude. Why do we need Dobbin?
Claude is fantastic at fast drafting, brainstorming, and complex reasoning, but it does not know your internal business rules. Dobbin provides the verified company context and guardrails that Claude needs to produce accurate, on-strategy work. Pairing them together gives your team Claude's execution power with Dobbin's company knowledge.
Why not just let every employee use their preferred personal AI assistant?
Personal AI accounts are great for individual tasks, but they do not talk to each other. When an employee solves a problem or learns something new in a personal chat, that insight stays locked in their account. Dobbin turns individual work into collective intelligence, so the whole company improves together.
Does Dobbin replace our team's existing AI subscriptions or work alongside them?
Dobbin is designed to work alongside tools like Claude. Other AIs can share the work of drafting and editing, while Dobbin shares the company's memory and standards. You can keep using the AI tools your team loves while powering them with Dobbin's verified knowledge.
Security: Keeping Company Information Safe in Claude
Why not just Import all of our company information into Custom GPTs or Claude Projects, or attach into chats?
Adding company documents into a project or chat exposes all of that sensitive information at once to anyone who has access to the workspace. Dobbin protects your data through controlled disclosure, sharing only the specific snippet needed to answer an immediate question. It also respects your channel-based permissions, ensuring sensitive details are never visible to team members who should not see them.
What does Claude get access to, and does connecting Dobbin expose our entire company database?
No, it never exposes your entire database. Dobbin acts as a secure gatekeeper that hands Claude only the small, isolated piece of information relevant to your question. Everything else in your knowledge base remains locked and invisible to Claude.
Does Claude store, remember, or train its public models on company data pulled through Dobbin?
No, company data passed through the connector is never used to train public models. The connection is private and governed by strict enterprise safeguards. Independent audits like SOC 2 and ISO 27001 verify that your data is kept secure and confidential.
If I use Dobbin with Claude, can any of my teammates see those conversations?
No, your conversations in Claude stay completely private to you. Dobbin provides background facts to your chat, but nothing you ask or type is visible to your colleagues. You can freely explore questions without worrying about teammate visibility.
Where to Work: In Slack, in Claude, or Both?
When should I talk to Dobbin in Slack versus in Claude?
Use Slack when you are working with your team and handling day-to-day communication, because Dobbin actively learns from those discussions and stores that know-how in your knowledge base. Use Claude when you are working in Claude's interface and want to pull in verified company facts. Slack is where Dobbin captures and grows your company memory, while Claude is a great space to apply it.
Does Claude automatically route everything through Dobbin, or do I choose when to use it?
You can ask for Dobbin directly, but Claude will also use its own intelligence to decide when Dobbin's context is needed. If your question touches on company strategy, customers, or internal rules, Claude automatically consults Dobbin. For general writing or public knowledge, Claude answers on its own without calling Dobbin.
Can our team use Dobbin entirely through Claude without opening Slack?
Yes, you can look up company facts and draft work directly inside Claude without ever opening Slack. However, Slack is where your team collaborates and where Dobbin captures new decisions in real time. Using both gives you the benefit of live knowledge capture in Slack and flexible execution in Claude.
"My Other AI Already Knows Me": Bringing Your Habits Over
I spent months teaching ChatGPT or Claude how I write. Can I move my personal habits into Dobbin without starting over?
Yes, you can easily bring your habits over. You can ask your existing AI to summarize your writing style, tone preferences, and formatting habits into a short profile. Then, simply paste that summary into your private Bio in Dobbin HQ so Dobbin mirrors your voice.
What does my other AI actually learn about me versus what Dobbin captures?
Other AIs learn your individual writing preferences through your personal chat history. In Dobbin, you manually enter your personal preferences in your private Bio, which shapes your individual experience without changing team standards. At the same time, Dobbin connects you to your company's live integrations and verified team playbooks.
How do I bring my existing prompts, personas, and custom instructions into Dobbin?
Add your personal writing habits and instructions directly into the Bio editor in Dobbin HQ, which you can manually update whenever your needs change. For team-wide prompts, personas, or standard operating procedures, upload them as documents into your Dobbin Knowledge Base. Dobbin will combine your personal bio with those team documents whenever it drafts work for you.
Setting Up: Connecting Dobbin and Claude
How do I connect Dobbin to my Claude account?
You connect Dobbin to Claude using a Model Context Protocol (MCP) connector available in your Dobbin Knowledge Base integrations. Once the connector link is configured, you simply add it to Claude's connector settings and complete a quick authentication step. Dobbin's knowledge will then be available in your Claude workspace.
Can I set up the Claude connector myself, or do I need an admin?
A Claude admin must first add the Dobbin connector to your organization's Claude account. After the admin completes that initial step, team members can connect Dobbin to their individual Claude accounts in just a couple of clicks.
What do I need in place before I can turn the connector on?
You need a Claude Pro account and a Claude workspace admin to set up the integration. You also need an active user account in your organization's Dobbin workspace so the connector can authenticate you.
Using Dobbin and Claude Together
How does the Dobbin connector inside Claude actually work?
The connector works like a secure bridge between Claude and your company knowledge base using the Model Context Protocol (MCP). When you ask Claude a company-specific question, Claude securely asks Dobbin for the relevant information. Dobbin checks your verified sources, hands Claude the exact snippet needed, and Claude writes the final answer.
What company knowledge can I access through Claude?
You can access your organization's full Dobbin Knowledge Base, including strategy documents, guidelines, and information learned from the Slack channels you belong to. Claude can read this context to answer questions, but it cannot alter, delete, or overwrite your source files.
Does Dobbin learn from my Claude conversations or send what I type back into Slack?
No, the connector is strictly a one-way street. Dobbin provides knowledge to Claude, but nothing you say or generate inside Claude is saved by Dobbin or shared to Slack. Your Claude chats remain entirely private.
How do my prompts change when using Dobbin inside Claude, and what are examples of good prompts?
With Dobbin connected, you no longer need to write giant background paragraphs or paste confidential playbooks before asking a question. You can ask Claude high-level questions that rely on company memory and internal judgment, which Claude could not answer accurately on its own.Here are a few examples of questions where Dobbin provides the missing company context:
Handling customer objections:
Without Dobbin, Claude gives generic sales advice; with Dobbin, it applies your actual approved pricing tiers, exception rules, and value messaging.)
"Draft a reply to a prospect who says our pricing is too high compared to standard alternatives."Internal review and brand consistency:
Without Dobbin, Claude only checks grammar; with Dobbin, it checks against your specific voice rules and unwritten standards
"Review this product launch announcement and flag anything that conflicts with our brand guidelines or uses banned buzzwords."Strategic alignment:
Without Dobbin, Claude guesses from internet benchmarks; with Dobbin, it grounds the answer in your actual customer outcomes.
"Based on our case studies and customer history, which of these two proposed pilot offers best fits our ideal customer profile?"
Does connecting Dobbin to Claude help reduce token costs and repetitive prompting?
Yes, it saves significant time and token usage. Instead of repeatedly pasting long strategy documents into Claude chats, Dobbin automatically retrieves only the exact snippet needed for your prompt. This keeps your conversations fast, focused, and much more cost-effective.