⚠️ This feature is currently in Beta. The ServiceFusion integration is available to a limited number of contractors while we continue building it out. If you'd like access, reach out to your SetSale rep or [email protected].
The ServiceFusion integration pushes your quote outcomes from SetSale into ServiceFusion, so your office team isn't re-entering the same job details twice. When you close out a quote, the matching records get created in ServiceFusion for you.
This article covers what syncs, what you'll need to set up first, and what isn't supported yet.
What Happens When You Close a Quote
The integration works based on the outcome you set on the quote in SetSale.
When a quote is marked Won
SetSale creates the following in ServiceFusion:
A customer record, if one doesn't already exist
An estimate
A job
This is the main workflow the integration supports today.
When a quote is marked Lost
SetSale creates a lost estimate in ServiceFusion so your pipeline stays accurate on both sides.
Setting Up Your Field Mapping
Before your first sync, you will need to map values in SetSale to the matching values in ServiceFusion. ServiceFusion requires some fields to match exactly, so a mismatch will cause the sync to fail.
Plan to review:
Custom fields
Status names
Any other ServiceFusion values that need an exact match
💡 Tip: Get your mapping sorted before you start closing quotes. It's much faster than troubleshooting failed syncs one at a time after the fact.
Checking Whether a Sync Worked
Sync results show up in the Activity feed on the right side of the quote — the same place you track quote opens and sends.
You'll see:
Confirmation when a sync completes successfully
An error message when ServiceFusion rejects part of the sync, including which field or value needs attention
If a sync fails, correct the mapping and try again. ServiceFusion surfaces errors one at a time, so you may need to fix one issue before the next becomes visible.
What Isn't Supported Yet
The integration pushes quote outcomes from SetSale into ServiceFusion. It's not a two-way sync, and it doesn't update records after they're created.
That means these scenarios aren't automated today:
A quote that's marked Won and later changed to Lost
A quote that's reopened and then won again
Any change where you'd expect ServiceFusion records created earlier to update on their own
If you need to change something after the initial sync, update the record directly in ServiceFusion.
Some of these limits come from ServiceFusion's API rather than SetSale — certain records can be created but not updated. We're continuing to expand what's supported.
Is This a Good Fit for Your Team?
The integration works best when you:
Want to cut down on manual re-entry after quotes close
Are comfortable working within a defined beta workflow
Can validate your ServiceFusion field mapping during setup
If your team relies on frequently reopening or reversing quotes, you may want to wait for a later release.
💬 Need Help?
Chat with us: Use the chat icon in the lower-right corner
Email us: [email protected]