Sybill can be connected to Claude through MCP, so you can use the context Sybill has built about your customers and deals without copying transcripts, CRM notes, or meeting summaries into Claude manually.
Once connected, you can ask Claude to use Sybill while doing things like:
Analyzing pipeline or closed-lost deals
Identifying accounts worth re-engaging
Creating business cases
Drafting personalized outreach
Building forecasts or deal reviews
Creating assets using your team's Claude Skills
Combining Sybill's sales context with information or workflows you already have in Claude
The important part is understanding how Claude accesses Sybill and which Sybill tools you should ask it to use.
Connect Sybill to Claude
Open Claude and go to Settings > Connectors.
Choose the option to add a connector and select Sybill.
Sign in to your Sybill account when prompted.
Authorize Claude to access Sybill.
Return to Claude. You should now see Sybill listed under your connected tools.
Open Sybill > Configure to review the tools Claude can use.
Once connected, Claude can access tools including Ask Sybill, as well as read-only tools for Sybill data such as accounts, conversations, and deals.
We recommend configuring:
Ask Sybill → Always allow
Underlying Sybill data tools → Needs approval
How Sybill works inside Claude
Connecting Sybill to Claude gives Claude access to two kinds of information:
Type | What it gives Claude | Best used for |
Ask Sybill | Sybill's understanding and reasoning across your sales data | Deal analysis, pipeline questions, risks, account strategy, win/loss analysis, forecasting, and other questions that require sales judgment |
Sybill data tools | Read-only access to underlying records such as accounts, conversations, and deals | Looking up particular records or retrieving specific underlying information |
This distinction matters.
Sybill doesn't just store sales data. It continuously interprets information from your conversations, emails, CRM, and other connected sources to build an understanding of your deals.
When Claude uses Ask Sybill, it can use that understanding.
When Claude queries the underlying Sybill data tools directly, Claude receives the records and decides for itself how to interpret them.
For most sales analysis, we recommend starting with Ask Sybill.
We recommend letting Claude use Ask Sybill by default
Claude is designed to complete tasks efficiently. When several tools can answer a question, it may sometimes choose the quickest way to retrieve enough information to produce an answer.
For simple lookups, that's useful.
For sales analysis, taking a shortcut can lead to a very different answer.
For example, imagine asking Claude to forecast your pipeline.
Claude could retrieve a subset of deals, analyze those records itself, and produce a forecast. But if it happens to retrieve 30 opportunities that are all in Stage 1, that isn't enough information to produce a reliable sales forecast.
Ask Sybill approaches the problem differently because Sybill already has sales-specific reasoning about your deals, their histories, buyer interactions, risks, and other context.
That's why we recommend configuring Claude so that:
Ask Sybill can be used freely for sales questions
Claude asks for approval before querying Sybill's underlying data tools directly
This encourages Claude to start with Sybill's understanding of the deal rather than rebuilding that understanding from a small set of raw records.
Recommended Claude connector settings
You can review the tools Claude can access through your Sybill connector.
In Claude:
Go to Settings > Connectors.
Select Sybill.
Open the connector configuration.
Review the available Sybill tools.
Configure Ask Sybill so Claude can use it without requiring approval each time.
Configure the underlying read-only data tools to require approval.
Your exact options may depend on your Claude workspace and administrator settings.
The goal is simple: default to Sybill's reasoning, and use raw Sybill data deliberately when the task calls for it.
Example: Find closed-lost accounts worth re-engaging
Here's an example of a task that combines Sybill's sales context with Claude's ability to create an output:
Use Sybill to analyze our closed-lost deals from the last 12 months. Find the five prospects most worth re-engaging based on product features we've shipped since losing the deal, and draft a re-engagement email for each account.
Claude can use Sybill to analyze your historical deals, identify relevant accounts, and then turn the findings into personalized outreach.
Instead of manually searching through closed-lost opportunities and reading old transcripts, you can work from Sybill's accumulated deal context.
Example: Create a business case
You can also use Sybill as the context layer for assets you create in Claude.
For example:
Use Ask Sybill to create a business case for Acme. Anonymize any sensitive contact details.
Sybill provides the customer and deal understanding. Claude can then turn that information into the final artifact.
You could also do this directly in Sybill.
Claude becomes particularly useful when your team has built a specific workflow or Claude Skill for the output you want.
For example, your company may have:
A required business case format
Specific brand guidelines
A standard executive summary structure
Preferred terminology
A particular ROI framework
Rules for how customer-facing documents should be written
In that case, you can use Sybill for the deal intelligence and Claude for the specialized format or workflow.
When should I use Sybill directly instead?
Connecting Sybill to Claude doesn't mean every Sybill task should move into Claude.
For everyday sales workflows where Sybill already knows what needs to be done, doing the work directly in Sybill is often simpler.
Use Sybill directly when you want to:
Ask questions about your deals
Analyze your pipeline
Inspect deal risks
Work through everyday deal actions
Create standard sales assets
Execute workflows Sybill already supports
Use Sybill with Claude when you want to:
Combine Sybill context with other information available in Claude
Use a custom Claude Skill
Apply your own specialized workflow or formatting rules
Turn Sybill's analysis into a highly customized artifact
Use Sybill's sales intelligence as one part of a broader Claude workflow
A simple way to think about it is:
Sybill understands the deal. Claude can use that understanding inside a broader AI workflow.
Example prompts to try
Once Sybill is connected, here are a few prompts you can try in Claude.
Re-engage closed-lost opportunities
Use Ask Sybill to analyze our closed-lost opportunities from the last 12 months. Identify five accounts that are worth re-engaging based on their original objections, reasons for losing, and changes in our product since then. Explain why each account made the list, then draft a personalized re-engagement email for each.
Build a business case
Use Ask Sybill to understand the Acme deal and create a business case for the buyer. Include their current challenges, desired outcomes, relevant stakeholders, expected business impact, and agreed next steps. Then format it using our Business Case Skill.
Review an opportunity
Use Ask Sybill to analyze the Acme opportunity. Tell me what is going well, the three biggest risks, what we still don't know, and the next actions you recommend.
Prepare for a forecast call
Use Ask Sybill to analyze my open pipeline. Identify the deals most likely to slip, explain the evidence behind each risk, and give me the three deals my manager is most likely to challenge me on during forecast.
Find patterns across lost deals
Use Ask Sybill to analyze our closed-lost deals from the last six months. Find the most common reasons we lose, separate product gaps from sales execution issues, and show me the evidence behind each theme.
Why does Claude have access to separate Sybill tools?
Sybill's connector doesn't expose Sybill as one generic source.
Claude can access different read-only tools depending on the information it needs, including tools for areas such as:
Conversations
Deals
Accounts
Ask Sybill
This gives Claude flexibility.
For example, if you simply need the details of a particular account, retrieving the account directly can make sense.
But if you're asking why an opportunity is at risk, the answer requires more than retrieving a deal record. That's when you should lead with Ask Sybill.
Does Claude change my Sybill data?
The Sybill data tools described here are read-only. They allow Claude to retrieve information that you already have access to in Sybill.
Can Claude access all of my company's Sybill data?
Claude's access to Sybill follows the Sybill account you connect.
You should only be able to work with Sybill information that your connected Sybill user is permitted to access.
Why did Claude answer my sales question without using Ask Sybill?
Claude chooses tools based on the task you give it and the tools it has available.
For some requests, it may decide that retrieving underlying records is sufficient.
If the question requires sales reasoning, you can be explicit in your prompt:
Use Ask Sybill to analyze...
You can also configure your Sybill connector so that Ask Sybill is the easiest Sybill tool for Claude to use, while requiring approval for direct access to underlying Sybill data.
Do I have to say "Use Ask Sybill" in every prompt?
Not necessarily.
If your connector permissions are configured as recommended, Claude can choose Ask Sybill when it needs Sybill's reasoning.
For important deal analysis, forecasting, pipeline analysis, or other questions where the quality of the sales reasoning matters, explicitly saying "Use Ask Sybill" is a useful way to make your intent clear.
Is Claude replacing Sybill's reasoning?
No.
The most powerful way to use the two together is not to have Claude independently reconstruct your deal from fragments of sales data.
Instead:
Sybill provides the sales memory and reasoning. Claude uses that intelligence to complete the broader task.
That lets you bring what Sybill knows about your deals into the custom skills, formats, and workflows you've already built in Claude.