Docs: FAQ

We build and run practical AI operations for local and service businesses: phones, SMS, follow-up, booking, reviews, and admin workflows you actually use every week.

Book a 30-minute strategy session on Calendly or use Contact. Bring call volume, missed leads, or calendar pain in plain language. No RFP required.

No. We work with US businesses remotely when your stack is cloud-accessible. DMV shows up on local pages for discovery, not as a hard fence.

Rough weekly call volume, where leads land (phone, form, text), and one process that breaks most often. Screenshots of missed-call logs help.

Three packaged tiers on /services/packages. Capture focuses on phones and lead capture. Convert adds follow-up, quotes, and reputation plays. Operate adds booking, support depth, and heavier admin automation.

No. The bundle builder at /services/all-services helps you pick individual agents. Packages are templates; custom stacks are normal.

Often yes, depending on integrations and data cleanup. Final dollars sit in a written scope before build.

Yes. Most teams ship one high-impact workflow first, prove it, then add the next. We plan that sequence on the strategy session.

Use /services/all-services for the interactive catalog with filters. Docs: Services summarizes how lines fit together and links to deeper pages.

Phone coverage on the hours and rules you set: answer, qualify, book when allowed, SMS handoff so fewer rings hit voicemail. See /services/ai-receptionist.

Event-driven SMS or email after a form, missed call, or quote, with opt-out and quiet hours. See /services/lead-follow-up and the Lead Follow-Up agent in the bundle builder.

Usually no. We connect to the CRM or calendar you already pay for when the API or Zapier path is sane.

Intake screening, insurance verification, claims follow-up, and treatment follow-up are common when compliance allows. Scope always follows your policies.

Yes for builds we take on. You approve scripts, hours, and escalation rules. Staff stay in control of edge cases.

We operate like a vendor with ongoing tuning: copy updates, routing tweaks, and tool changes as your seasonality shifts.

Depends on integrations and how clean your data is. Simple phone plus SMS paths are faster than multi-system billing. We quote realistic timelines in scope.

We say so up front. Sometimes a cleanup sprint or single source of truth for contacts comes before fancy automation.

Owner-led teams where the phone, inbox, or calendar still drive revenue: restaurants with reservation pressure, home services with missed calls, professional offices with intake load, retail with pickup questions, and gyms with booking churn.

Yes when cart recovery, post-purchase support, or product questions create real ticket volume. Pure content sites with no operations may be a weaker fit.

No. They are examples for search and education. Fit is about operations, not a fixed niche list.

Only inside the boundaries your counsel and policies allow. We scope language, storage, and vendors explicitly. Nothing ships as implied compliance.

Consultation follow-up, treatment reminders, review timing, and light reactivation when you approve the copy. See the Treatment Upsell and Review agents in the bundle catalog.

Booking and reminder agents pair with your PMS rules. Insurance verification and document collection agents reduce desk time when your workflow supports it.

We avoid fake guarantees. Directional ranges on the bundle builder are labeled as estimates. Real outcomes depend on volume, discipline, and what you hand off first.

We align on a few metrics before launch: missed-call rate, speed-to-lead, booking fill, ticket volume, or review cadence, depending on what we ship.

Talk to us before flipping tools off. Pauses happen; we help wind down automations so customers are not left mid-sequence.