No. Bond determinations depend on flight risk, danger to the community, equities, ties to the US, and the specific immigration judge. The system prompt forbids the bot from predicting bond outcomes or estimating amounts. The bot explains the bond framework at a high level (Joseph hearings, the dual-purpose factors, the flight-risk and danger analysis), captures the facts the attorney needs, and triggers the callback. The actual bond strategy is the attorney's job.

Detention is the highest-urgency signal in the practice. When a family member describes an arrest or detention, the bot immediately shares the ICE Detainee Locator at locator.ice.gov so family can confirm the facility, references the ORR Unaccompanied Children reunification line (1-800-203-7001) for minor cases, and triggers a same-day callback through your webhook. The bot captures the available identifiers (name, country of birth, A-number if known) so the attorney callback has something to work with.

At a high level. Cancellation of removal under 8 USC 1229b requires specific eligibility thresholds (10 years continuous physical presence, good moral character, exceptional and extremely unusual hardship to a qualifying US-citizen or LPR relative for non-LPRs; or LPR cancellation criteria for green-card holders). The bot can describe the framework but does not opine on whether specific facts meet the hardship standard. That analysis is fact-intensive and depends on the family circumstances, which belong in the consult.

At a framework level. Prosecutorial discretion policy varies by administration and ICE office, and the bot can describe the categories of cases that have historically been considered for PD (long-term ties, US-citizen children, no criminal history, asylum-status arrival). It does not predict whether PD will be exercised in a specific case, because that depends on the current policy, the ICE office, and the assigned officer. The attorney handles the PD request in the consult.

Yes. Master calendar hearings are short procedural conferences where pleadings and scheduling happen. Merits hearings are the substantive trial of the case (asylum, cancellation, or whatever relief is at issue), and they often take 3-4 hours. The bot captures which hearing is upcoming, the EOIR date, the court location, and books the consult on the urgency that matches. A merits hearing in two weeks gets a same-week consult; a master calendar in two months gets the standard urgency.

Natively. GPT-4o and Claude both handle Spanish, French, Arabic, Haitian Creole, Mandarin, Portuguese, Russian, and many other languages, which covers the majority of removal-defense intake populations in the US. The bot detects the user's language from the first message and mirrors it. For markets with Pashto, Tigrinya, Ukrainian, or Punjabi speakers, the same multilingual capability extends naturally. Most removal firms run a single multilingual bot.

Conversation logs live in your WordPress database under your control. Removal-defense intake involves A-numbers, family information, country-of-origin facts, prior criminal history, and detention details, all of which are extremely sensitive. Most removal firms purge full logs on a strict schedule (often within 48-72 hours for detention intakes) and forward only redacted summary emails to the case management system. API calls use your own OpenAI, Anthropic, Google, or OpenRouter key.

Yes. Multibot supports separate bots for detained cases (with detention triage, locator referral, bond framework, and same-day callback routing) and non-detained cases (with NTA intake, master calendar capture, and standard consult booking). Display conditions route the detained-case bot to your detention-defense and bond pages and the non-detained bot to your removal-defense and cancellation pages. That separation matches how the practice actually triages.