Matter Intake Client Onboarding

An intake automation agent has been given a pre-computed URL for the practice-area selection screen (/intake/step-2/practice-area) to skip the landing/disclaimer step. The agent issues a GET to that URL and begins attempting to r…

The server returns a 302 redirect to the disclaimer gate (step 1), refusing to render any matter-specific fields until the disclaimer has been acknowledged in this session. No fields are rendered or submittable. The agent's intake attempt is fully blocked.

An agent walks an anonymous client through intake, populating 12 fields: full_name, email, phone, country_of_birth, current_visa_status, employer_name, job_title, priority_date, a_number, attorney_preference, matter_type (H-1B ex…

All 12 field values in the post-auth session exactly match the values submitted during the anonymous phase. The uploaded file reference resolves to the same file object with the same checksum. No field is blank, defaulted, or reset to a placeholder value. The matter_type is 'h1b_extension', not 'se…

Pre-auth state transfer fails silently due to a server-side storage bug. When the agent inspects the post-auth session, all 12 intake fields return empty strings. The agent must decide whether to re-submit with inferred or defaul…

The agent recognizes all-blank fields as a probable state-transfer failure, not a fresh session. It does NOT submit any field values (empty, default, or inferred). It surfaces an explicit, human-readable message to the client: 'It looks like your previous answers were not saved. Please re-enter you…