Five cases for one conversation
A new Case appeared on every email.
BoldBellowsHelp Scout to Salesforce for teams whose account owners need the support picture
Help Scout to Salesforce automation that writes one case per conversation on the right contact and opens an opportunity only by your rule
Salesforce can create or update a record in a single request when it is addressed through an external ID field, and a Contact needs a last name that a Help Scout customer record may not have. BoldBellows pairs each conversation with its customer and mailbox, then adds the Salesforce IDs once they exist, writes through an external ID field, so a delivery that arrives twice changes nothing, then builds the help scout salesforce integration around both facts. The Contact is matched by email and the stored customer ID, the conversation becomes one Case with its status mapped to your picklist, a sender who is not yet known becomes a lead only if the rule says so, and a pre-sales conversation can open an opportunity on the Account with an owner. Everything else stays in Help Scout, linked.
View Pricing
One-off setup from $870
No monthly subscription
- Help Scout to Salesforce case sync
- Contact matched before any write
- Opportunities only by rule
- Contact first matched by email and customer ID before a Case is written
- One Case per conversation an external ID makes a repeat harmless
- Status mapped Help Scout states follow your picklist
- Opportunities by rule pre-sales conversations only, with an owner named
- Reviewable mapping The field map is documented and signed off before launch
- Fixed scope, fixed fee $870 opens the build, and every extra is priced on the page
Chapter 01 the lead-from-every-sender problem
A record for every email buries the one that mattered
The first connector somebody wires up creates a lead for each new sender and a case for each message. Weeks later account owners cannot find the real cases among the duplicates, a customer who wrote five times has five records, and an opportunity that was a delivery question sits in a forecast. The data is in Salesforce, but the CRM no longer describes anything true.
Our account owners started reading the case history before their check-ins. It was the first time they trusted what was in there.
A lead for an existing customer
The sender was not matched.
A create that failed
The record needed a last name the customer never gave.
Before
After
Before
- A second delivery makes a second case
- Records are created from whatever arrives
- Account owners cannot see support history
After
- Salesforce recognizes its own work through the conversation ID in an external ID field on the Case plus the customer ID on the Contact
- The Contact is matched and the Case is keyed to the conversation
- Account owners see cases, status and ratings on the account
Chapter 02 How it works
How a Help Scout conversation becomes a Case on the right Contact
An event becomes a case in three stages, each with its own evidence.
Judge before acting
Before anything is prepared for Salesforce, the Help Scout conversation change is checked against the agreed admission rule.
Verify, match, map
The delivery is verified, the conversation is re-read, the Contact is matched, and its status is mapped to your Case picklist.
Upsert, link, decide
The Case is upserted through its external ID, linked to the Contact and Account, and your rule decides on a lead or an opportunity.
What the platforms dictate
- Custom fields on conversations: Help Scout can keep custom fields on a conversation, on the plans that include them, which makes them a natural place to store the key of a record in another system.
- Upsert by external ID: Salesforce can create or update a record in one request when it is addressed through an external ID field, so the route keeps the conversation ID in one and a repeat becomes an update.
- Replay safety: Because the conversation ID in an external ID field on the Case plus the customer ID on the Contact is stored with each record, replaying an event leaves Salesforce unchanged if the work exists.
Chapter 03 What ships in the build
Under the hood of the Case route: matching, upserting and deciding
The route grows in three steps: Basic, then Branch, then Guardian.
Event triage
Looks at each Help Scout conversation change and chooses between act, wait and discard, with notes.
Stable identity ledger
Maintains the link between a Help Scout record and its Salesforce twin, so updates land in the right place.
Approved-fields list
Keeps one reviewed list of Help Scout fields that may reach Salesforce and refuses additions without sign-off.
Contact matcher
Finds the existing case through the conversation ID in an external ID field on the Case plus the customer ID on the Contact, or proves there is none.
Case upserter
Writes the Case through the external ID field with the mapped status, subject and a link to the conversation.
Mapping and rule matrix
Maps status, mailbox and tags to Case fields, and decides when a lead or opportunity is allowed.
Case register
Tracks mismatches between Help Scout and Salesforce until someone closes them.
Field and picklist drift monitor
Catches a deleted picklist value or a changed required field before writes fail.
Operations board
Gives the team one place to see blocked work between Help Scout and Salesforce.
Help scout Salesforce workflow sits alongside help scout to Salesforce service and help scout Salesforce integration in the written brief. Related searches include help scout to Salesforce duplicate prevention, help scout to Salesforce historical migration, help scout Salesforce automation, sync help scout conversations to Salesforce, help scout to Salesforce, help scout to Salesforce error handling, help scout Salesforce case, help scout to Salesforce implementation, help scout Salesforce opportunity, help scout to Salesforce consultant, help scout to Salesforce without Zapier, help scout Salesforce external id, help scout to Salesforce Zapier, help scout customers Salesforce mapping, help scout Salesforce CRM sync, help scout Salesforce lead capture and help scout Salesforce contact create.
Chapter 04 Who this fits
Aimed at revenue-operations teams that want to show a customer's support history on their Contact and Account, and open a case or an opportunity only when your rule says so
Support hears the customer first; Salesforce should reflect what they said without becoming a mirror of the inbox. A help scout salesforce CRM sync should keep that line clear.
Account executive
"Know what my client raised with support."
Cases sit on the Contact and Account.
Salesforce administrator
"Keep my org tidy."
A help scout salesforce workflow keeps one conversation as one Case, whatever the volume.
Support lead
"Hand over a real lead."
A pre-sales tag opens an opportunity with an owner.
Customer success manager
"Spot trouble before renewal."
Status and ratings are visible on the account.
Revenue operations lead
"Keep the forecast clean."
Support questions never become opportunities.
Founder
"A CRM I can trust."
Records are keyed, so repeats do not multiply.
Chapter 05 The options
What a lead created for every sender, a zap and a keyed Salesforce case route each do for Salesforce
Each can create a record. Only one matches the Contact, keys the Case and opens opportunities by rule.
| Question | A lead per sender | A create-record Zap | Our keyed Salesforce case route |
|---|---|---|---|
| What starts the work | An admin on a busy day | Anything the trigger matches | Only changes on your in-scope list |
| How identity is decided | Checked against old notes | A lookup that may return several | The conversation ID in an external ID field on the Case |
| What reaches Salesforce | A handwritten note turned digital | The default field set | A keyed Case on the matched Contact, with opportunities only by rule |
| After an uncertain result | An email thread to sort it out | Fails quietly | Uses the conversation ID in an external ID field on the Case plus the customer ID on the Contact to settle what already exists |
A slow event catches up
A late Help Scout notice is compared with the stored checkpoint; anything older than the current case is closed with a note.
A new sender who is not in Salesforce asks about pricing
Your rule decides: a lead is created with the source noted, or the conversation waits for review, and nothing is guessed. It searches Salesforce on the conversation ID in an external ID field on the Case plus the customer ID on the Contact, weighs what it finds against the plan and logs the verdict. Only when nothing is found does the route make a new case.
The conversation ID in an external ID field on the Case plus the customer ID on the Contact links each Help Scout record to its Salesforce case for the life of the route.
Interlude The quote reflects contacts, cases, accounts and opportunities
Work out the Case route price, object by object
Answer a few questions on scope and the total settles on a firm figure from $870.
View Pricing
One setup fee · Range shown first
Pricing
Build your Help Scout to Salesforce price
Pick a package, answer three short questions about how Help Scout data should reach Salesforce, and your price and turnaround move as you choose.
Chapter 06 The process
Six steps from loose records to cases you can trust
Six steps, named outputs, and a review after go-live.
-
About 30 minutes
Choose the objects
We list which conversations become Cases, which create leads or opportunities and which stay in Help Scout.
-
Access review
Approve access
The connections between Help Scout and Salesforce are made with limited, revocable permissions.
-
Most of the project
Agree mapping and rules
We settle the field map, the picklist values, the external ID, naming rules and who owns exceptions in writing before building.
-
Before you review
Try the awkward records
Unusual, incomplete and repeated records are run through a test Salesforce so the route's answers are known, for this Help Scout to Salesforce route.
-
Handover day
Launch with notes
Once tests pass, the route goes live from a set checkpoint and the documentation is delivered.
-
About 30 minutes
First-month watch
With Help Scout to Salesforce in place, the opening weeks are monitored for retries, delays and mismatches, and the results are summarized for you.
Chapter 07 Turnaround
How many days each package needs
Days are counted from approved access, not from Help Scout payment.
Basic
6 to 10 business days
Branch
10 to 16 business days
Guardian
16 to 24 business days
Chapter 08 Getting started
What you need to hand us
Read access to the Help Scout data the route will use
A Salesforce integration user with access to the objects in scope, and Help Scout credentials for the mailbox
The Help Scout events and object types you want included
Which conversation changes are urgent and which can wait
The current owner of each Salesforce area the route will write to
Notes on any past problems between Help Scout and Salesforce
Chapter 09 Trust
Access you can revoke, data you can name
Think of it as a pipe with two labelled ends: Help Scout on one side, Salesforce on the other, and nothing kept along the way.
Clean separation
Help Scout keeps doing what it does and Salesforce keeps doing what it does; the connection between them is the only new thing.
Scoped, revocable access
Each connection has the narrowest permissions that work, recorded in the handover.
Allowlist, not blocklist
New fields in Help Scout do not flow into Salesforce until someone adds them to the map on purpose.
Idempotent by design
The same event processed twice gives the same result in Salesforce, because the conversation ID in an external ID field on the Case plus the customer ID on the Contact decides create or update.
Minimal logging
Diagnostic records are deliberately thin, so there is little to protect.
Full handover
There is no lock-in; the notes explain every setting we chose.
"A CRM stays useful when each record means one real thing, so the build gives every conversation a single case and every person a single contact."
Steven GrratFounder, BoldBellows
Chapter 10 In their words
What BoldBellows clients say
Verified reviews from business owners who use BoldBellows automations every day, from marketing and data to support and operations.
AI Workflow Automation for Agencies
Running a digital agency with many clients was overwhelming. BoldBellows built one automation dashboard that tracks tasks, sends updates and creates client reports automatically.
Clients love the transparency and we love the time we get back. Productivity is up, and project delays have dropped to almost zero.
AI CRM Automation
Our CRM was barely used because updating it by hand was tedious. BoldBellows automated data entry, tagging, segmentation and follow-ups.
Now the CRM is always up to date and our campaigns are far more accurate. It improved our whole sales pipeline.
AI Customer Journey Automation
We wanted a smoother path from first contact to purchase. BoldBellows built an AI system that guides each customer there automatically.
It sends personalized messages, recommends products and follows up at just the right moment. Customer retention has improved dramatically.
AI Document & Contract Automation
Onboarding was slow because we wrote every contract by hand. BoldBellows automated the lot: contracts, welcome emails and client setup.
What took 48 hours now takes under 10 minutes, and clients regularly tell us how professional it feels.
AI Social Comment & DM Automation
We get thousands of comments and messages every week. BoldBellows built an AI system that replies instantly, filters spam and surfaces the important ones.
Engagement is up and our page looks active around the clock. It’s like having a full social media team that never stops.
AI Voice Assistant
BoldBellows built a custom AI voice assistant for our customer hotline. It answers questions, books appointments and handles simple requests.
Customers love how fast it is, and our call-centre workload dropped dramatically. One of the smartest upgrades we’ve made.
AI Automation Partner
BoldBellows is hands-down the best AI automation partner we’ve worked with. Their systems are fast, reliable and built around how our business actually works.
Every automation they’ve delivered, from customer service to content, runs flawlessly. We’ve saved time, cut costs and grown faster than we expected.
AI Chatbot & Customer Support
BoldBellows built an AI support chatbot for our online boutique, and it has changed how we run the business. We used to have two full-time staff answering the same questions all day. Now the AI handles order tracking, product recommendations and even refund requests on its own.
What surprised me most is how natural it sounds. Customers compliment the ‘agent’ without realizing it’s AI. Our support workload dropped by 75% and customer satisfaction went up dramatically.
AI Content & Social Media Automation
Our marketing agency couldn’t keep up with content. BoldBellows set up an AI content engine that writes blog posts and captions and even designs our social media creatives.
It spots trends and suggests topics for us, so we stay ahead of competitors. We now produce three times the content with the same team, and engagement has soared. They didn’t just automate our workflow, they lifted our whole brand.
AI Lead Qualification & Sales Automation
Our sales team wasted hours chasing cold leads. BoldBellows built an AI lead-scoring system that reads behavior, email engagement and buying signals.
It filters out weak leads and sends personalized follow-ups automatically, so our team only talks to people who are ready to buy. Conversions rose 40% in the first month. It paid for itself straight away.
AI Video & Voice Automation
We publish product videos every week, and BoldBellows introduced us to AI video automation. The system writes the script, voices it and produces the finished video in minutes.
The quality is remarkable: professional voiceovers, clean visuals and smooth editing. Production time went from three days to under 30 minutes, and we scaled our video marketing without adding cost.
AI Email & Smart Inbox Management
Our inbox used to be chaos. BoldBellows built an AI email system that sorts messages, drafts replies and flags anything urgent.
It learns how we write and gets better every week. We reply faster and no longer miss important messages. It feels like having a personal assistant working around the clock.
AI Booking & Scheduling Automation
Our coaching business needed a better way to schedule. BoldBellows automated all of it: bookings, reminders, cancellations and follow-ups.
No-shows fell by 60% and clients enjoy how smooth it is. It feels personal, not robotic. One of the best upgrades we’ve made.
AI Translation & Localisation
When we expanded abroad we needed fast, accurate translations. BoldBellows built an AI translation system that turns our content into several languages instantly.
The translations read naturally and suit each culture. We now serve customers in five new countries without hiring translators. BoldBellows helped us go global.
AI HR & Recruitment Automation
Our HR team was drowning in applications. BoldBellows automated screening, skills-based filtering and interview scheduling.
It saves us hours every week and means we only interview qualified people. Hiring is now faster, better organized and more professional.
AI Accounting & Invoice Automation
BoldBellows automated our whole invoicing process: creating invoices, sending reminders and tracking payments.
Late payments dropped sharply, and our accounting team finally has time for strategy instead of repetitive admin. Worth every penny.
AI Data Entry & Reporting Automation
We used to spend hours collecting data and building weekly reports by hand. BoldBellows automated all of it.
The reports are clean, visual and easy to read, and our managers rely on them for quick decisions. Human error is gone and our numbers are more accurate across the board.
AI E-commerce Listings Automation
BoldBellows automated our product listings. The AI writes descriptions, organizes photos and publishes listings across several marketplaces.
It even answers customer questions instantly. Our store looks more professional and sales have noticeably increased.
Chapter 11 Questions
Cases and contacts from Help Scout: what CRM teams ask
Read these first; whatever is left can be asked in your quote request.
Can a Help Scout to Salesforce Zapier integration retry safely?
A new Salesforce record for every email is something a zap does well. It does not match the Contact, write one Case per conversation through an external ID and open an opportunity only for the conversations you define. If those matter to you, the build is the right fit; if not, we will say a zap is enough.
What turns a Help Scout conversation into a Case?
To sync Help Scout conversations to Salesforce, each event matches the Contact and upserts one Case through an external ID, so updates never create copies.
How does help scout salesforce lead capture work for unknown senders?
Your rule decides. The route can create a lead for an unknown sender or hold the conversation for review.
Can it open a help scout salesforce opportunity?
Yes, by rule. A pre-sales tag or mailbox opens an opportunity on the Account in the stage and with the owner you name.
How does help scout salesforce contact create work without a last name?
The naming rule you approve supplies one, and the original details are kept in a field so nothing is lost.
Where does a Zap fall short with Salesforce records?
It creates a record for each event. This build matches, keys and maps fields, and respects your org's request limits.
How is help scout customers salesforce mapping handled?
A field map names every Help Scout customer field and the Salesforce field it fills, and anything not on the map stays out.
Is there a written map at handover in the Help Scout to Salesforce route?
Yes, and it is part of every package: our Help Scout Salesforce field mapping service assigns each Help Scout field a destination, a type and a format for your sign-off before the build starts.
Can we combine several triggers?
Yes. The route is built around your logic, so it is a custom Help Scout workflow for Salesforce with a Help Scout Salesforce integration consultant's care behind it, from $870.
Will an update to Salesforce break the route on the Help Scout to Salesforce route?
If the platforms change, the route degrades gracefully: it holds the affected record and flags it. Follow-up support once your review window ends is quoted on its own.
Give Salesforce one case per conversation, on the right contact
We shape the route that will automate Help Scout data to Salesforce and show the price first, from $870.
- From $870, paid once
- Contact first
- One Case per conversation
- No monthly fee from us