Register the enquiry source
Keep channel, contact claim, received clock, marketing permission source and preliminary subject category.
An enquiry register, not legal advice, conflict clearance, client acceptance, engagement, privilege determination, identity verification or marketing consent.
Preserve acquisition and permission sources, minimise preliminary facts, route conflict and suitability questions and require evidence before matter conversion.
Keep channel, contact claim, received clock, marketing permission source and preliminary subject category.
Collect only routing facts, restrict sensitive narratives and warn that submission does not create representation.
Separate conflict-input preparation, lawyer review, referral, consultation scheduling and declined-enquiry disposition.
Require acceptance authority, engagement source, client and matter identifiers, team assignment and CRM-to-matter receipt.
The register follows a web enquiry that names an opposing party and requests an urgent consultation. Restricted facts enter a separate review lane, marketing remains off, and no matter record opens until an authorised acceptance and engagement source arrive.
This page is an operational blueprint. The final workflow, screens, permissions and integrations depend on your current process and agreed implementation scope.
Review the existing product areas that support the proposed workflow.
Run the operational calculation, save the result in the URL and share it with your team.
Tell Codeblix how work moves today. We will confirm the practical scope before proposing an implementation.
Discuss your workflowRs 1,000 monthly. Unlimited users, invoices and integrations.