No. Specialty-occupation analysis depends on the degree requirement, the position duties, the level of judgement required, and current USCIS adjudication trends. The system prompt forbids the bot from opining on whether a specific role qualifies as a specialty occupation, whether an alternative-degree position will sustain, or whether an RFE response will succeed. The bot explains the four-prong framework at a high level and routes the analysis to the consult where the attorney can review the position.

Yes, when your fees page is current. H-1B fees include the base I-129 filing fee, fraud fee, asylum program fee (tiered by employer size and case type), the H-1B integrity fee, and premium processing. The bot reads your published fees page rather than baking numbers into a system prompt, so when USCIS adjusts fees - which has happened multiple times recently - you edit one page and every conversation is current.

Yes. Universities, university-affiliated nonprofit research organisations, and governmental research organisations are cap-exempt, and the bot recognises the signals from the employer description. Cap-exempt cases skip the lottery entirely and can be filed year-round, with a different fee structure and different USCIS Service Center routing. The bot explains the framework and captures the exemption basis for the consult to verify.

Yes. Concurrent H-1Bs (a beneficiary working for two employers simultaneously, each holding their own H-1B) and amended petitions (after worksite, role, or material employment-term changes) are common in established practices. The bot captures the trigger - new worksite, new role, secondary employer - and routes to the right attorney with the right intake form. It does not opine on whether a specific change requires an amendment versus a renewal; that analysis is the attorney's.

Yes. STEM OPT beneficiaries whose H-1B petition is timely filed and selected get cap-gap protection extending work authorisation through September 30, with H-1B status starting October 1. The bot explains the timing carefully because beneficiaries often plan international travel during cap-gap and the travel rules are restrictive. As with everything else, the actual travel-risk analysis is the attorney's, not the bot's.

Conversation logs live in your WordPress database under your control. H-1B intake involves beneficiary information, employer details, and work-site addresses that are sensitive. Most business-immigration firms purge full logs on a scheduled basis and forward summaries to the case management system. API calls use your own OpenAI, Anthropic, Google, or OpenRouter key, so prompts do not pass through any SleekAI server.

Yes. Multibot supports separate bots for employer-side intake (HR-shaped questions, beneficiary volume, integrity-fee tiers, third-party placement) and candidate-side education (lottery odds, OPT cap-gap, individual eligibility). Each runs on its own URL pattern via display conditions. That separation matters because employer intake feeds a billable consult and candidate inquiries need to be politely redirected to the employer's own counsel - the same bot trying to do both ends up confusing both audiences.

At a framework level. Third-party site placements (where the H-1B beneficiary works at a client's location rather than the petitioner's office) draw heightened USCIS scrutiny around the employer-employee relationship. The bot captures whether a third-party site is involved and routes the case to the consult with that flag attached. It does not opine on whether a specific third-party arrangement will sustain - that analysis depends on contracts, end-client letters, and itineraries, which is precisely what the attorney evaluates in the consult.