Frequently Asked Questions

A private LegalBai consultation is generally suitable for concerns that benefit from focused legal assessment, strategic guidance, or early issue-spotting. That may include personal, business, property, document, compliance, or related legal questions reflected in the intake flow.

Each request is still reviewed individually. Submission of an inquiry does not guarantee that a consultation will be accepted or scheduled.

The intake flow is designed to help LegalBai understand the nature, urgency, and context of your concern before any consultation is arranged.

If the matter appears suitable for the current consulting workflow, you may be guided to the next steps. If it is outside scope, requires clarification, or cannot be accommodated, the request may not proceed in the same way.

LegalBai may review requests involving complex personal, business, property, document, or compliance concerns through its preliminary intake and consultation workflow.

Complexity alone does not disqualify a request, but it may affect whether additional clarification, conflict review, scheduling steps, or a narrower initial consultation scope is appropriate.

Yes. The implemented intake flow already accepts requests from private individuals as well as business owners, company representatives, employers, and other organizational contacts.

Acceptance of a consultation still depends on review, fit, availability, and the current workflow requirements.

Yes, a consultation may serve as an initial strategic discussion before any broader formal engagement is considered.

That said, a consultation is not the same as ongoing representation, and any wider engagement would still require separate acceptance and scope arrangements.

That depends on the request type and the scope actually accepted. Some matters are better handled as an initial legal assessment, while others may involve document-focused review if that is part of the consultation context.

The platform does not assume that every consultation automatically includes detailed document analysis beyond the materials and scope actually reviewed.

The current workflow starts with the preliminary intake form. After submission, the request is reviewed to determine whether it can move forward and whether a consultation path is appropriate.

If a paid consultation is made available for that request, the requester may proceed through scheduling, slot hold, payment-proof submission, manual payment review, and then final approval before meeting details are treated as confirmed.

Your request is recorded for preliminary assessment and becomes available inside the requester portal when applicable. LegalBai then reviews the request in light of fit, clarity, workflow requirements, and operational availability.

Depending on that review, the next step may be portal follow-up, paid consultation scheduling, a request for clarification, or a decision not to proceed through the consultation path.

Yes. The implemented system is not an instant-booking model. The request is reviewed before a consultation is treated as ready to move forward.

Even after slot selection and payment submission, final confirmation still depends on the applicable review and approval steps.

Yes. In the current system, the consultation workflow begins from the intake process and related requester portal context.

The scheduling and payment steps are designed as post-intake actions rather than a standalone public booking form.

Prepare a concise summary of the concern, the basic facts, relevant dates, and the outcome or guidance you are seeking. If documents are involved, be ready to describe what they are and why they matter.

Only provide information reasonably necessary for preliminary assessment unless LegalBai asks for more.

If the request is incomplete, ambiguous, or needs a more precise factual picture, LegalBai may seek clarification before deciding whether to proceed.

That does not guarantee acceptance; it simply means the current information may not yet be enough for a responsible next-step decision.

If the request moves forward within the current workflow, you should receive the relevant next-step instructions through the portal or related service communications.

The exact path depends on the request outcome, such as whether the matter proceeds to scheduling, needs clarification, or remains under review.

A consultation is considered confirmed only after the applicable request review and payment review steps are completed and the request reaches an approved state in the implemented workflow.

Selecting a slot or submitting payment proof alone does not by itself create final confirmation.

The current scheduling workflow supports the consultation modes that are actively offered in the system at that time. This is generally a remote-first workflow rather than a blanket promise of all possible meeting arrangements.

If a mode is not shown in the scheduling process, it should not be assumed to be currently available through the platform.

Where supported by the current configuration, the requester can choose among the available online modes during scheduling. After approval, the operational meeting details are issued through the portal or related communications.

The confirmed delivery details shown in the approved workflow are the practical source of truth for the meeting.

Review timing can vary based on queue volume, complexity, the need for clarification, and operational availability. The platform does not promise an exact universal turnaround time for every request.

For urgent deadline-sensitive matters, the intake form should not be treated as an emergency-response channel.

In the current workflow, the consultation amount is calculated from the selected duration and the applicable platform configuration. After a slot is held, the requester submits payment proof for manual verification.

The request does not become finally confirmed merely because payment proof was submitted. Approval still depends on the review process reflected in the portal.

Yes. The workflow shows the applicable amount before the requester confirms the consultation request, and the payment screen reflects the relevant payment context again.

This helps the requester understand the financial step before moving deeper into the approval process.

Submitted information is handled through access-controlled intake, portal, and administrative workflows for assessment and consultation operations.

At the same time, users should still avoid sending unnecessary secrets or materials beyond what the preliminary workflow reasonably requires.

The implemented system uses verified email flows, authenticated portal access, structured payment and scheduling states, and controlled administrative review surfaces to reduce unauthorized access.

Those controls support confidentiality, but users should still share only what is reasonably necessary for preliminary review unless additional materials are specifically requested.

No. Submitting an intake, requesting a consultation, selecting a slot, or paying through the platform does not by itself create an attorney-client relationship for broader legal representation.

Any wider formal engagement would require separate acceptance and any additional scope or fee arrangements that may apply.

Potential follow-up assistance may be discussed after the initial consultation depending on the matter, the outcome of the discussion, and whether further work is appropriate.

Any broader assistance beyond the consultation itself should not be assumed to be automatic and may require separate acceptance or arrangements.

The current LegalBai workflow is structured rather than informal. It uses a guided intake, request review, portal tracking, consultation scheduling, payment verification, and approved meeting details instead of relying only on a loose inbox exchange.

That structure helps keep expectations clearer while preserving a deliberate and professional consultation process.