Salesforce Travel and Hospitality South Africa

Safari365

Sales Automation

Safari365 was running a bespoke-travel business on spreadsheets, Word documents, and fragmented tools, which made pricing multi-vendor itineraries, tracking customer context, and removing repetitive advisor work increasingly difficult as the company grew.

3,000 suppliers
35-person staff
First estimate in 30 minutes
Internal efficiency is up 30%

Reported impact

Business outcome

Safari365 raised internal efficiency, sped up quoting, reduced repetitive advisor work, and shortened time-to-value for AI deployment by pairing well-structured Salesforce data with directly configurable agents.

  • Customer Experience
  • Productivity Improvement
  • Revenue Growth

Solution

Safari365 turned Salesforce into its system of record for sales, vendor preferences, and pricing logic before adding Agentforce to automate repetitive itinerary and communication work. The company rebuilt highly complex pricing rules for multiday safaris with thousands of suppliers directly inside Salesforce, so consultants can price long itineraries in minutes instead of stitching together information from disconnected tools. On top of that clean data layer, Agentforce now drafts 'day notes' from detailed trip information, uses historical customer context to personalize follow-up recommendations, and is tested iteratively in Agentforce Testing Center with a human in the loop to prevent internal notes or unsafe suggestions from reaching travelers. External data from a SQL database, Synatic, and Roam feeds the same environment, which gives the CEO and team enough control to refine agents in natural language and deploy new travel-operations automations in weeks rather than months.

Data flow

Customer, supplier, and pricing information is consolidated in Salesforce and connected SQL sources, Agentforce uses that history to generate itinerary notes and personalized recommendations, and Testing Center plus human review keep messages safe before they reach travelers.

Solution architecture

3 components · 3 layers
  1. Serving
    • Salesforce Serves as Safari365's system of record for itinerary data, customer history, and pricing logic.
  2. Orchestration
    • Agentforce Generates customer-facing itinerary content and automates low-value travel workflow tasks.
  3. Governance
    • Agentforce Testing Center Lets Safari365 test and refine agent behavior before customer-facing use.

Architecture clues

  • Agentforce Testing Center and human-in-the-loop review were used to prevent internal notes from leaking into traveler communications.
  • Pricing logic for multiday itineraries was rebuilt directly on Salesforce.
  • Safari365 syncs a SQL database to Salesforce through Synatic and brings in foreign-exchange considerations via Roam.

Evidence from the source

Being able to build agents and refine them on my own made Agentforce the fastest time-to-value of any Salesforce product we've deployed: just six weeks from signing to live.
Huge. Our internal efficiency is up 30%.
Our biggest lift was rebuilding our pricing logic directly on Salesforce.
This kind of repetitive task is a perfect fit for Agentforce. It saves my team hours.
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
    2 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

    Safari365 customer story

    First-party
    https://www.salesforce.com/customer-stories/safari365-marcus-brain-interview/
    Source type
    Vendor-published customer story
    Published
    Jul 30, 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 Jul 30, 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.