Known caveats

These are real behaviors of the Setmore integration that we want you to know about before you flip it on, rather than discover after a customer complaint. Most have a “why it works this way” reason and an easy workaround.

Plan and access

A Setmore Pro account is required

Setmore’s free plan doesn’t include the connection we use. If you’re on the free plan, the connection will fail at the “Test connection” step.

Setmore API access is approval-only

Even with a Pro account, you have to email api@setmore.com and get manually approved before you receive an access key. This usually takes a few business days. There’s no self-service signup.

Note

Setmore doesn’t offer a sandbox or test mode. Setup happens against your real Setmore account, so we recommend doing your first sync over a short date range (next two weeks) so you can review the results without thousands of appointments coming through at once.

How the sync works (and how often)

New appointments only — no backfill

The first time you connect, TracsConnect starts watching Setmore for new bookings going forward. We don’t import appointments that were booked in Setmore before you connected. If you need historical appointments in TRACS, add them by hand.

Sync happens by polling, not instantly

We check Setmore on a schedule (typically every few minutes), not the moment a customer books. So there’s a short delay between a booking happening in Setmore and it showing up in TRACS. Plan for “minutes, not seconds.”

Cancellations and reschedules don’t flow to TRACS yet

If a customer cancels or reschedules in Setmore after the appointment has already synced into TRACS, TracsConnect does not automatically cancel or move the TRACS appointment. You’ll need to update TRACS by hand for now. We’ll wire this up in a future release.

Caution

Until this is wired, treat your TRACS schedule as the source of truth for what’s actually on the calendar. If you see a Setmore cancellation come in, update TRACS to match.

How customers and vehicles get matched

Phone number is the primary match

TracsConnect matches a Setmore booking to an existing TRACS customer by normalized phone number — we strip formatting so (555) 010-1234, 555-010-1234, and 5550101234 all match the same person. If the phone matches one TRACS customer, that customer wins.

Multiple matches → flagged for review

If two or more TRACS customers share the same phone number (it happens — family members, old records), TracsConnect won’t guess. The appointment lands flagged in TRACS for you to pick the right customer.

Customers with no phone (or a bad phone) are matched by name

If the phone field is blank, garbage, or fewer than 10 digits, we fall back to a name match. Name-only matches never auto-link — they always flag for review. Better to pause and pick the right John Smith than to land an appointment on the wrong account.

Vehicle requires Year, Make, and Model

If any of the three required vehicle fields (Vehicle Year, Vehicle Make, Vehicle Model) is missing on the booking, TracsConnect creates the appointment without a vehicle attached (you’ll see it as “no vehicle” in TRACS). Add the vehicle by hand or ask the customer to rebook with complete info.

Vehicle typos won’t auto-correct

We do a small amount of brand cleanup — chevy becomes chevrolet, that kind of thing. We do not do broader fuzzy matching. So if a customer types Tooyta Camery, we won’t recognize it as Toyota Camry — the appointment will sync with the typoed values stored verbatim, or it’ll flag for review if the typo means we can’t find a vehicle match.

Things that don’t sync

What	Does it sync?	Why
New appointments	Yes	The main feature
Customer name, phone, email	Yes	For matching + creating new customers
Vehicle year/make/model	Yes (when configured)	Per the custom contact fields setup
VIN, license plate	Yes (when configured)	Optional but recommended
Cancellations in Setmore	Not yet	Coming in a future release
Reschedules in Setmore	Not yet	Same
Setmore payments	No	Use your normal TRACS workflow for invoicing
Setmore’s customer reminder messages	No	Setmore sends those; TracsConnect doesn’t see them
Booking comments / notes	Partial	The note from Setmore comes across but may not land on the TRACS appointment in a visible spot
Staff assignments / resources	No	TracsConnect assigns the appointment to the shop, not to a specific tech

Double-messaging risk

If you have both Setmore reminders and TracsConnect appointment text reminders turned on, your customers may get two reminders for the same appointment — one from each system. Pick one source of reminder messages and turn the other off.

We recommend keeping reminders in TracsConnect so they go through your shop’s existing texting setup. Turn off Setmore’s reminders under Setmore → Settings → Notifications.

Operational gotchas

If you lose your access key, you need a new one

Setmore doesn’t let you view your access key again after you’ve issued it. If you lose it (deleted the email, switched computers without saving it), you have to email Setmore and ask for a new one. Save the email in a safe place when you first get it.

Disconnecting stops new syncs but doesn’t remove past appointments

If you disconnect Setmore in the TracsConnect dashboard, future Setmore bookings stop syncing. Appointments already in TRACS stay where they are. Reconnecting later picks up new bookings from that moment forward — it does not backfill the appointments that happened during the disconnect window.

Renaming a Setmore field after setup will break vehicle sync

If you rename Vehicle Year to Year of Vehicle in Setmore after the integration is already connected, new appointments will come in with no vehicle attached because TracsConnect is still looking for the old name. Either keep the field names you started with, or update the field mapping in the TracsConnect dashboard after you rename. See Troubleshoot.

When in doubt

If something looks unexpected, the troubleshooting page covers the common cases. If it’s not there, contact support with the appointment date and what you were expecting to see.