A boolean is_24h column drives a badge on the agent page and a filter on county hubs. Agents who run a true 24-hour answering service flip the column to true; those who post staffed-hours-only set it to false. The badge is data-driven, so it stays honest as long as the column does.

Yes. A selector mapping targets a hero-position phone block on the agent page and pulls the emergency_phone column directly. The same mapping can populate a click-to-call link in the H1 area so mobile visitors connect with one tap from the search result.

Flip the status column to suspended or revoked. The agent disappears from county and bond-type hubs on the next cache cycle. The personal page can either return 404 or render a notice; either way, the sitemap regenerates so search engines update their index.

Each generated URL is a real WordPress page with full HTML, sitemap inclusion, and per-page meta tags. The base template is auto-noindexed so it never competes with the generated children. Local bail queries typically index within a few crawls of the sitemap update.

Yes. Columns for min_bond and max_bond render in the agent's credibility block. Hub pages can also filter by bond size range, so a /bail/large-bond/harris-county/ URL surfaces only agents who write bonds above a threshold.

Yes. Bond types stored as a JSON array column so an agent can write both. The bond-type hubs render only agents tagged with that type, so /bail/immigration/houston/ and /bail/felony/houston/ become distinct indexable URLs from the same roster.

Yes. Each office becomes its own row in the roster with a unique slug and its own coverage county. A central agency hub page can list all offices via a list mapping that filters on the parent_agency column.

Keep the row, set status to retired, and switch the agent page to render a redirect or a notice with referrals to active agents in the same county. The URL still resolves so backlinks do not 404, but the agent disappears from hub lists.