Help from people who
know title operations.
No ticket-deflection maze and no first-line script. You reach someone who has looked at a stalled sync before and can tell you what it means.
Email support
The best channel for anything with a sync event ID attached. Include it and we can see the exact payload without asking you for a screenshot.
Shared channel
Customers on an annual plan get a shared Slack or Teams channel with the engineers who build and run the service. Ask in the room, not through a form.
Urgent: sync down
If orders have stopped flowing for a live tenant, mark the subject URGENT. Those page an on-call engineer directly, around the clock.
What you can
actually expect.
These are targets we hold ourselves to during business hours, US Central, Monday through Friday — with the exception of a downed sync, which is answered whenever it happens.
| Severity | First response |
|---|---|
| Sync down | Under 1 hour, 24/7 |
| Records failing | Same business day |
| Mapping / config | 1 business day |
| Question or request | 2 business days |
Three things that shorten every ticket.
- The sync event ID. Copy it from Sync history. It's the single most useful thing you can send us — it carries the tenant, the order, the payload, the rule, and the response.
- The tenant name. Multi-tenant deployments mean "the sync is broken" is ambiguous. Naming the branch narrows it instantly.
- What you expected to see. "Stage should read Clear to close, it still says Title search" tells us more than any log excerpt.
Asked often enough to write down.
How long does setup actually take?
About thirty minutes for the first tenant if your Salesforce fields already exist, and closer to an hour if you're creating a Title_Order__c object as you go. Every tenant after the first is faster because mappings are reusable templates.
Nobody outside your Salesforce admin has anything to learn — status simply starts appearing on records people already use. What changes when it's on covers it role by role.
Does TitleBridge ever write back into Qualia?
No. The Qualia connection requests read scopes only. Qualia stays the system of record for title data; TitleBridge just makes a copy of the status visible in Salesforce.
What happens if Qualia or Salesforce goes down?
Changes queue and drain in order once the connection recovers. Failed writes back off and retry on a schedule that runs for 24 hours, and writes are idempotent so a retry that lands twice changes nothing the second time.
Anything that exhausts its retries raises an alert rather than disappearing. See Retries & failures.
Can it map to our custom Salesforce fields?
Yes — that's the normal case, not an exception. TitleBridge reads your object's schema and offers every writable standard and custom field. Picklist values get their own translation table so Qualia's milestone names can land as whatever your org calls them.
Will syncing overwrite edits my team made in Salesforce?
That's your org's decision, not ours. We deliver a signed JSON payload to a receiving app inside your own Salesforce org — we never log in and never write a record ourselves. Your app decides which fields it accepts and what it does with them, so whether a local edit survives is controlled by the code and automation you own.
Most teams let title-owned fields (status, key dates, open requirements) be overwritten and leave everything else alone. New connections start in dry-run mode so you can see exactly what would be written before anything is.
Where is our data stored?
On our infrastructure in the United States — TitleBridge is a hosted service, so the order timeline rests on our servers. What matters is which data: borrower identity, property addresses, loan and policy amounts, and the title commitment's curative report are filtered out before anything is written, and fetched live from Qualia only when someone authorised asks to see them.
What we hold day to day is the status layer — order numbers, milestones, dates, business names — plus the lender loan number, which we must store to match records and therefore keep encrypted. The full breakdown is in the Privacy Policy.
How do brokers and clients see status without a Salesforce license?
Most teams surface the synced fields through an Experience Cloud page. Sharing and visibility stay Salesforce's job — TitleBridge only keeps the underlying fields current. There's more in Redirecting the askers.
Can we run a pilot on one branch first?
We recommend it. Go live on a single tenant, leave it a week, then roll out. It surfaces field-naming surprises while the blast radius is one office, and it gives you a real before-and-after count of deflected status requests.
What does it cost to add another branch?
Tenants are part of the same deployment, so adding one is a configuration change rather than a new install. Pricing depends on order volume and tenant count — tell us your shape and we'll give you a real number.
Send it over.
Give us the tenant, the order, and what you expected to see. We'll take it from there.