Integration
HumCrew and ServiceTitan
ServiceTitan can remain the system your office uses while HumCrew's engineering team designs a customer-specific connection around approved workflows. The exact API access, objects, directions, and failure handling are discovery and implementation work, not assumed features.
Connector status: This ServiceTitan connector is not part of the current HumCrew core. It must be separately scoped, built, and verified for your tenant before any external read or write is enabled or represented as available.
What a scoped build can connect to
- An approved ServiceTitan tenant through API access provisioned in your account and confirmed during discovery.
- Configured HumCrew phone and text channels, with the external handoff defined in the written integration scope.
- Approved website, lead-form, or quote-tool sources only after each ingress and destination path is implemented and verified.
What an approved connector can read
- Customer records, if the approved ServiceTitan API scope exposes the required fields.
- Job and appointment history, if the account tier and implemented connector permit those reads.
- Schedule availability only after the exact calendar rules and API responses pass tenant-specific tests.
What an approved connector can write
- New customers and leads only where the separately built connector has a verified write path.
- Booked jobs and appointments only after availability and idempotent write behavior are verified.
- Notes and call outcomes only for approved objects and fields in the customer-specific scope.
Honest limits
We would rather tell you what does not work on the first call than have you find out after the invoice.
- No ServiceTitan connector ships in the current HumCrew core. This page describes a custom engineering option, not an enabled integration, marketplace listing, certification, or partnership.
- Integration depth follows what the API exposes for your account tier and configuration. In discovery we map exactly which of your workflows the agent can touch, and we tell you before you commit.
- Complex dispatching rules that live in your dispatcher's head have to be written down before the agent can follow them. That is part of the build, and it takes real conversations with your team.
Common questions
Does the AI answering service actually connect to ServiceTitan, or just take messages?
Not by default. The current HumCrew core does not include a live ServiceTitan connector. For a separately approved project, we can scope the API access, build the authorized paths, and verify each read and write against your tenant before enabling it.
Is HumCrew a certified ServiceTitan partner?
No. We offer separately scoped custom engineering and do not claim a marketplace listing, certification, partnership, or currently enabled core connector.
Will an AI agent replace how my office uses ServiceTitan?
No. ServiceTitan can remain your system of record. Any HumCrew read or write into it is enabled only after the customer-specific connector is built and verified; until then, the supported HumCrew core operates inside HumCrew.
What if our ServiceTitan account tier does not include full API access?
Integration depth follows what your account tier and configuration expose through the API. We map this in discovery before any build starts and tell you plainly which of your workflows the agent can reach and which it cannot.