Sybill

Sybill is a sales assistant built around recorded customer calls. After each external meeting it produces a structured summary, drafts a follow-up email, and pushes the summary plus a link to the meeting dashboard into the CRM as a Meeting, Call, Note or Task, attaching it to the matching account, opportunity and contacts where it can find them.

The part that separates it from a note taker is CRM Autofill, which updates the deal and company fields you configure after every meeting and every email on that deal. Matching depends on housekeeping: the vendor asks that the opportunity exists before the first call, that participant emails sit on the CRM contact records, and that CRM stages are mapped to Sybill's own deal stages during setup.

Four plans are published: Free, Pro, Business and Enterprise. Pro is $36 per user monthly or $30 billed annually and Business is $108 or $90, with Enterprise quoted by sales.

The seat price is not the whole meter. Each plan carries a weekly allowance of AI credits per user: 500 on Free, 2,500 on Pro, 5,000 on Business, unlimited on Enterprise. Automatic work (summaries, pre-meeting briefs, follow-up drafts, CRM Autofill) is described as not consuming credits, while user-requested work does: asking questions across the pipeline, running analyses, and calls made through the API or the MCP server. Admins buy one-time 5,000-credit bundles or turn on automatic top-offs when a team runs low, and no bundle price is published.

Two gates matter when comparing tiers. Pushing a summary into the CRM starts at Pro; field-level Autofill, API and MCP access, two-way Slack and the deal workspace start at Business, where Autofill is capped at 10 fields.

The API documentation describes bearer-token REST endpoints at api.sybill.ai for reading organization-visible conversations, deals, accounts, messages, rows and documents, and for importing your own records. Keys are created in the dashboard under Settings, Integrations, API Keys.

Alongside it sits an MCP server at mcp.sybill.ai/mcp for assistants such as Claude and Cursor. The two have different identities: REST keys operate with organization-level context and never return private records owned by individual users, while the MCP server acts with the signed-in user's own access. Imported records are private by default and need at least one owner email, and an import response only confirms the record was accepted for asynchronous processing, so transcription and derived fields are not immediately readable.

A SafeBase trust center lists SOC 2, ISO/IEC 27001:2022, GDPR, CSA STAR Level 1 and the EU-US Data Privacy Framework, names Slack, Intercom, Google Cloud, MongoDB and AWS as subprocessors, and holds a data processing agreement, a CAIQ self-assessment and a pentest report behind an access request. The risk profile states a recovery time objective of 24 to 48 hours. No uptime percentage is published.

Against that, the public master subscription agreement permits using customer data to train Sybill's own expression recognition and speech-to-text engines and to improve its machine learning models, with no opt-out published beside it. The privacy policy ties retention to customer instruction rather than to a schedule. Those are the two documents a security reviewer will want rewritten in an order form.

Single sign-on is documented in detail for Okta, Microsoft Entra ID and other SAML providers, with optional enforcement and SCIM directory sync that follows IdP group changes. It is limited to eligible plans, and the pricing page places SSO at Enterprise. Each user still connects a Google or Outlook calendar on first SSO login, because the calendar is the Sybill identity.

Deleting a single meeting is self-serve from the meetings dashboard, but removing a recording from Sybill's servers goes through support or privacy@sybill.ai.

Bulk export is the same shape. The help centre states that bulk exports are not available within the app and routes offboarding teams through one of two assisted transfers: an S3 bucket named for your domain with Sybill's canonical ID granted list and write access, or a Google Drive service account. What arrives is MP4 recordings with audio and video. Transcripts, next steps, outcomes and other metadata are explicitly excluded, and anything beyond the recordings is a conversation with your account representative.

The fit is a B2B revenue team on Salesforce, HubSpot, Zoho CRM or Dynamics 365 that wants call notes to become CRM data without a rep retyping them, and that can live inside the Business tier's 10 Autofill fields.

It fits less well in three cases. Teams working in languages other than English get transcription in 100+ languages but the Magic Summary itself in English only. Teams whose legal review requires a contractual no-training commitment start from an agreement that grants the opposite. Teams that need programmatic access or single sign-on pay for it twice over, since the API and MCP sit on Business and SSO on Enterprise.