Five nationwide guides, jurisdiction by jurisdiction.

State-level generalizations hide meaningful neighborhood variance. California's Bay Area doesn't share LA's phone-order shape. Texas's Austin doesn't share Houston's. Florida's Jacksonville doesn't share Miami's. The guides here surface the regional patterns worth knowing about before you scope a pilot, but the actual configuration decisions — alias vocabulary, concurrency ceiling, hours policy — happen at the shop level. Read the state guide to know what questions to ask; answer the questions with your specific shop's data.

None of these pages claim Fire It has a local sales team, a local office, or a local partner network in the state. None of them claim compliance with the state's specific privacy statutes — that's a determination your counsel makes for your specific configuration. None of them are legal advice. Every recording, disclosure, or SMS-consent question is written as a counsel prompt, and every prompt links to the underlying primary source (statute, regulator page) so your counsel can start from the same reference material.

We publish state guides only when we have enough regional context and enough counsel-relevant sourcing to make the page useful rather than generic. If your state isn't listed here, that isn't a signal Fire It doesn't serve you — the platform is available nationwide. It's a signal we haven't authored a guide with the depth these carry. The demo, the calculators, and the implementation checklist are all available regardless of state, and a rollout in an unpublished state follows the same phased pattern as the ones on this hub.

A state guide is background reading; your carrier report and POS export are the numbers that determine whether a rollout makes sense. The recommended order: skim the state guide for the metros and languages that match your footprint, then pull the last thirty days of missed-call counts from your carrier and the last thirty days of average tickets from your POS. Plug those numbers into the missed-call and ROI calculators. The state guide tells you what to watch for during a pilot — sports Sundays, tourism weeks, morning espresso peaks; the calculators tell you whether the pilot pencils out at your specific shop. Skipping the numeric step and buying on the state guide alone is the mistake we most often see.

The five guides use the phrases one-party consent and two-party consent (also called all-party consent) because those are the categories your counsel will use during a call-recording review. One-party jurisdictions require the consent of one party to the call — typically the party doing the recording; two-party or all-party jurisdictions require every party's consent. Interstate calls introduce further complexity when the caller and the shop sit in different regimes. None of the guides tell you which rule to apply to your specific configuration; every guide points at the primary statute so your counsel can. If the compliance question is the reason you're stalled, the counsel prompts on each guide are the fastest way to structure a fifteen-minute call with your attorney.