Call Experts: website access vs ServiceTitan API

01 / Provider buying guide

Two access paths are described, not one universal integration

The ServiceTitan page says website access is sufficient for many businesses, while high call volume or more sophisticated protocols may use an advanced API connection. It describes real-time appointment booking and job input, and names an unassigned queue for overflow booking. These are the supplier’s published descriptions, not independently tested account behavior.

02 / Provider buying guide

Decide where an overflow job enters the office workflow

An HVAC office can use the distinction to ask whether an overflow request becomes an unassigned record or an appointment already assigned to a crew. A created record still needs the office’s service-area, job-type and availability rules. The operator’s access path should match those rules rather than silently bypass them.

Separate the permissions needed to look up a customer, enter a job and change an existing visit. Website access can require different onboarding and failure handling from an API connection. Confirm what is included in the proposed implementation.

03 / Provider buying guide

On-call calendars are a second responsibility

The home-services page explicitly offers self-service and managed on-call calendars. For self-service, establish which office user updates coverage and when the change becomes active. For managed service, establish how changes are submitted and acknowledged. These are buyer acceptance criteria, not a claim that either configuration was tested. Transfers and notification attempts remain distinct from a technician accepting work.

The pricing entry point asks for business details before sending prices; no form was submitted. Compare a written proposal that identifies both the integration method and on-call responsibility. A logo on the integrations menu is not a complete scope or quote.