Salesforce Software / SaaS global

Datasite

Customer Service Automation · Enterprise Knowledge Search

Datasite needed faster, more accurate support for dealmakers running high-stakes M&A transactions, but its first-generation Einstein chatbot could not transfer chats to humans or keep answers current without manual updates.

1.8 million dealmakers
180 countries
20% more than their Einstein chatbot
Knowledge base of over 2,000 articles

Reported impact

Business outcome

Datasite improved self-service quality for time-sensitive deal support, expects a higher automated resolution rate than its earlier chatbot, and frees the Assist team to spend more time on consultative, high-touch work.

  • Customer Experience
  • Productivity Improvement
  • Revenue Growth

Solution

Datasite evolved its support architecture from a basic Einstein chatbot into a more dynamic Agentforce workflow that lives in Experience Cloud and draws on both operational and knowledge data. The earlier Einstein implementation already used a knowledge base with more than 2,000 articles to resolve common questions, but the handoff to live support and freshness of answers remained a bottleneck for urgent deal workflows. Agentforce now verifies the user's identity and permissions, retrieves the most relevant knowledge for a natural-language question, automatically stays current with new product content, and passes the entire conversation plus account context to a human Assist team member when escalation is needed. Datasite also plans to extend the design by unifying structured knowledge in Snowflake with unstructured chats and emails in Salesforce through Data Cloud so the same agent layer can answer more nuanced product and case-history questions over time.

Data flow

Customers start a chat in Experience Cloud, where Agentforce verifies identity, retrieves the best answer from Datasite knowledge content, and either resolves the issue or hands the interaction to the Assist team with a generated summary; over time, structured Snowflake content and Salesforce interactions are meant to converge in Data Cloud for richer answers.

Solution architecture

5 components · 4 layers
  1. Compute
    • Einstein Handled the first generation of self-service chat based on Datasite's knowledge base.
  2. Storage
    • Data Cloud Will harmonize structured and unstructured support data across the Datasite stack.
    • Snowflake Stores structured knowledge that Datasite plans to expose to Agentforce through Data Cloud.
  3. Serving
    • Experience Cloud Hosts the customer chat experience on Datasite's website.
  4. Orchestration
    • Agentforce Provides the new conversational agent that answers questions and transfers context-rich escalations.

Architecture clues

  • Agentforce is embedded in Experience Cloud and performs identity and permission checks before answering.
  • Datasite plans to unify Snowflake knowledge with Salesforce chats and emails in Data Cloud.
  • Escalations include a summary of the chat and key account details for the Assist team.

Evidence from the source

Data Cloud will unify and harmonize this data and make it usable across Datasite's entire tech stack.
Datasite expects to use Agentforce to resolve 70% of incoming chat queries - 20% more than their Einstein chatbot.
Einstein ... tapped into Datasite's knowledge base of over 2,000 articles.
If a customer needs an Assist team member, Agentforce seamlessly transfers the case with a summary of the chat and key account details.
Transparency Evidence & methodology 100/100 reference value · 89% confidence · 1 source

Review how this reference was scored and trace each normalized claim back to its documented source.

01

Scoring methodology

How scores are calculated

Customer Reference Value measures usefulness as a customer reference. Evidence Confidence measures the quality and traceability of available evidence, not independent verification.

Customer reference value100/100
  • Problem clarity20/20
    Measures whether the customer's operational problem is specific enough to compare.
  • Implementation depth25/25
    Rewards named components, data flow, integrations, and architecture detail.
  • Outcome specificity20/20
    Measures whether the reported benefit is concrete rather than a generic claim.
  • Quantified impact25/25
    3 metrics describe measurable impact.
  • Deployment scale10/10
    Rewards evidence of a live or scaled deployment and meaningful integration scope.
Evidence confidence89%
  • Source authority20/25
    The main evidence is an official vendor-published customer story.
  • Claim traceability21/25
    10 of 12 key fields link to a named source.
  • Direct evidence20/20
    4 direct source quotes retained.
  • Date provenance10/10
    The publication date comes from the source page or publisher.
  • Source transparency8/10
    1 source reference document publisher, URL, authority, retrieval, and supported fields.
  • Implementation specificity10/10
    Rewards source-backed components, data flow, quantified impact, and a specific outcome.
02

Traceability

Sources & provenance

Field coverage shows which facts each source supports. Dates are shown only when documented by the source.

  1. Salesforce

    Datasite customer story

    First-party
    https://www.salesforce.com/customer-stories/datasite/
    Source type
    Vendor-published customer story
    Published
    May 14, 2025
    Supports
    • Customer
    • Business problem
    • Solution
    • Products
    • Solution components
    • Data flow
    • Integrations
    • technical area
    • use case category
    • Business outcome
    • outcome category
    • Metrics
    • Architecture
    • evidence quotes
    • Publication date

Date evidence

  • Published on source page May 14, 2025 · Salesforce · First-party
    Open date source
Not separately sourced Industry, Region, Company size. Treat these normalized attributes as lower-confidence until a dedicated source is added.