Compliant by architecture. Written down for your IT lead.

TCPA controls

Outbound calling and texting rules

Outreach runs inside calling hours set by the customer's own area code, with consent records, do-not-call handling, and opt-out processing at every touchpoint. Every attempt is timestamped in the audit trail.

• Quiet hours enforced by the customer's area code
• Do-not-call and opt-out processing on every channel
• Consent records and a timestamped audit trail

Reg F-aligned, enforced in code

Collections guardrails

Contact-frequency caps, dispute and pending-reply holds, and do-not-collect rules for disputes, legal holds, payment plans, and manual holds run before any outreach step fires. Outreach goes out first-party, in your brand's name. None of it is left to the model.

• Contact-frequency caps on every outbound path
• Dispute, pending-reply, legal, and payment-plan holds applied before any dial
• First-party outreach in your own brand's name

STIR/SHAKEN and A2P 10DLC

Caller ID and messaging deliverability

Outbound calling uses registered numbers with STIR/SHAKEN attestation, and SMS runs on A2P 10DLC registered campaigns, set up per brand, so caller ID stays trusted and messages stay out of spam labeling.

• Registered numbers and attestation
• A2P 10DLC registration for SMS
• Brand-by-brand campaign setup

ServiceTitan stays the source of truth

Customer data and system of record

FrontDeskPro reads the customer, job, invoice, membership, and payment context it needs from ServiceTitan and writes every outcome back: bookings, payments, card updates, notes, call summaries, and dispositions. Working data is synced per tenant. Your operations team and your finance team look at the same record, in the system you already own.

• Every booking, payment, note, and disposition written back to ServiceTitan
• Transcripts and call summaries land on the ServiceTitan record
• Portfolios can run a scheduled warehouse sync into their own analytics stack

One tenant per customer

Tenant separation and environments

Each customer runs as its own tenant with its own ServiceTitan connection, playbooks, numbers, and rules. Portfolio build-and-own customers get a dedicated tenant environment they own outright. Production is separated from the demo environment, and FrontDeskCollect's production, staging, and demo environments are defined in Terraform.

• Per-tenant ServiceTitan connection, playbooks, numbers, and rules
• Dedicated tenant environments for portfolio build-and-own customers
• Production, staging, and demo separated, with infrastructure defined as code

Designed, not a failure mode

Human escalation

A caller can ask for a person at any point. The AI hands off to your team with the full context of the conversation, and the handoff is logged. On the collections side, sensitive accounts route to your people instead of the machine, and escalations land as tracked cases.

• Warm handoff with the full conversation context
• Sensitive collections accounts route to your team
• Every handoff logged and tracked as a case

Measured changes, tested code

Engineering discipline

Call playbooks are versioned. Changes are A/B compared on booking rate and roll back automatically when a change hurts bookings. The inbound agent codebase carries more than 1,800 automated tests, the collections platform more than 470 backend test files, and every call and outreach attempt is logged for audit.

• Versioned playbooks with A/B comparison and automatic rollback
• 1,800+ automated tests in the inbound agent, 470+ backend test files in the collections platform
• Call-level and attempt-level audit trail