Skip to main content

Client intake agent

An enquiry is not an engagement.

A client intake agent organizes professional-service enquiries, collects the minimum approved information and prepares a source-linked packet for qualified review. It can clarify missing details and route potential conflicts or urgent issues. Werkon would validate this intake pattern with clear notices and accessible contact options; professionals retain advice, conflict decisions, acceptance and authority to open a matter.

Collect information for the current intake stage

Show the applicable organization, jurisdiction, role, privacy, confidentiality, no-advice, no-engagement, emergency and deadline notices before collection. Keep original statements separate from summaries. Record contact authority, related and adverse parties, broad issue, important dates, purpose, retention and correction without exposing other matters.

Use approved duplicate, contact-sanctions, geographic, service, capacity and conflict-candidate checks to return only necessary status and a review task. Protected traits or sensitive circumstances must not become service-fit or commercial-ranking proxies. Language and representative options should remain accessible.

Keep receipt separate from engagement

Acknowledgment cannot promise advice, privilege, confidentiality, response time, acceptance or protection of a deadline. Requests for further information remain distinct from engagement. Qualified reviewers decide conflict, competence, capacity, referral, decline, safeguarding and any proposed client relationship.

Client and matter records, downstream access, agreements and payments require their own explicit authority. Preserve notices, submissions, reviewer reasons, handoff acceptance, correction, deletion and appeal evidence. The assistant cannot contact an adverse party or interpret a limitation period.

Intake job boundary

Receive the enquiry. Keep representation unambiguous.

Intake is not one form submission. Four boundaries protect the person, existing matters and the professional decision that follows.

01

Notice, channel, and minimum collection

Show the correct organization, jurisdiction, privacy, confidentiality, relationship, no-advice, emergency and deadline notices; offer accessible channel, language and representative options; state purpose and retention; obtain the required authorization; and collect only fields approved for the current intake stage.

Required evidence: Notice bundle and version, organization and role, jurisdiction and service, display and comprehension route, accessibility and language choice, emergency and deadline instruction, purpose and lawful basis where applicable, consent or other authorization, withdrawal, field schema and necessity reason, channel, submission time and receipt.

02

Identity, parties, and matter outline

Resolve the enquirer, contact authority, organizations, adverse and related parties, broad issue, jurisdiction, forum and important dates; preserve exact statements and source documents; keep summaries and inferences separate; and delay unnecessary merits, strategy and sensitive information until authorized review.

Required evidence: Person and organization identifiers, contact and representative authority, preferred channel, adverse and related party names and aliases, broad matter type, jurisdiction and forum, important-date statement, exact user text, artifact and digest, source location, summary, inference label, conflict, correction and missing information.

03

Conflict, urgency, and service candidates

Run scoped duplicate, conflict, competence, geographic, service, capacity, fraud, safety, vulnerability, urgency and deadline-candidate checks; reveal no other client or matter; expose inputs and uncertainty; prevent protected-trait ranking; and route every consequential candidate to a qualified reviewer.

Required evidence: Check policy and version, permitted data scope, identity candidates, duplicate and relationship candidates, conflict-review token, service and jurisdiction candidates, capacity state, safety and urgency flags, important-date source, protected-field exclusions, confidence, alternatives, abstention, reviewer task and access log.

04

Qualified disposition and clear next step

Have named professionals decide conflict, competence, capacity, engagement, more-information, referral, decline, safeguarding and deletion; send approved language that states the current relationship, action and limits; obtain any client and engagement acceptance separately; create records and permissions only after authorization; and preserve correction and complaint routes.

Required evidence: Reviewer identity and authority, disposition and reason, conflict and service decision, urgency and deadline instruction, safeguarding action, request and response, approved acknowledgment, relationship status, no-reliance and emergency language, engagement and client acceptance, created client and matter ids, handoff receipt, decline or referral notice, retention, deletion, complaint and correction history.

Enquiry-to-disposition path

Five stages from first contact to an owned next step.

The agent can make the path faster to inspect. It cannot make the relationship or professional judgment automatic.

  1. 01

    Show notices and channel choices

    Resolve organization, jurisdiction, service and role; present approved privacy, relationship, confidentiality, no-advice, no-engagement, emergency and deadline language; provide accessible channel, language and representative choices; and record notice delivery and collection authorization.

    Owner
    Intake, privacy, accessibility, and professional owners
    Evidence
    Notice versions, jurisdiction and service, channel and language, accessibility and representative option, emergency path, purpose and lawful basis, authorization and time, withdrawal path, field schema and display receipt.
  2. 02

    Capture the minimum enquiry

    Collect identity, contact authority, adverse and related party names, broad matter type, jurisdiction, forum, important dates and preferred communication; preserve exact statements and approved artifacts; validate required formats; and defer unnecessary merits, strategy, financial and special-category details.

    Owner
    Enquirer with intake data controls
    Evidence
    Identity and contact, authority to submit, party and alias fields, matter category, jurisdiction and forum, important-date statement, channel preference, exact answers, artifacts and digests, validation, optional and deferred fields, source and correction state.
  3. 03

    Resolve identities and surface candidates

    Match people and organizations within permitted scope, detect duplicate enquiries, return conflict-review tokens without exposing protected records, classify service and jurisdiction candidates, flag possible urgency and safeguarding conditions and prepare a source-linked summary with missing questions and uncertainty.

    Owner
    Conflict, intake, and safeguarding review queues
    Evidence
    Identity candidates and evidence, duplicate link, conflict token and access boundary, service and jurisdiction candidates, capacity snapshot, urgency and safety flags, excluded protected fields, source-linked summary, missing questions, confidence, abstention and queue assignment.
  4. 04

    Make the qualified intake decision

    Review the exact source packet, resolve identity and conflict, assess competence, capacity, urgency, deadline handling, accessibility and safeguarding, request only necessary additional information and decide engagement, decline, referral or another owned path with reason and authority.

    Owner
    Qualified professional and authorized intake owners
    Evidence
    Reviewer and role, source review, identity and conflict disposition, service and capacity decision, urgency and safeguarding action, deadline instruction, additional-information request, engagement or decline decision, referral approval, reason, decision time and expiry.
  5. 05

    Acknowledge, authorize, and reconcile

    Send approved language that states receipt, current relationship, next owner, action and limits; obtain engagement and client acceptance separately; create client, matter and permissions only after authorization; preserve delivery and handoff receipts; enforce retention or deletion and correct every affected record and message.

    Owner
    Relationship, communications, records, and matter owners
    Evidence
    Communication template and version, recipient and channel, delivery and acknowledgment, relationship status, next owner and action, emergency and no-reliance language, engagement acceptance, client and matter creation receipts, permissions, referral handoff, retention or deletion, complaint and correction.

Authority model

Let systems route. Keep acceptance with professionals.

Identity facts, operational checks and professional duties are separate. The intake system should make that separation obvious to both staff and the enquirer.

01

Deterministic notice, identity, and access controls

Code should own notice versions, permitted fields, authorization state, stable identities, exact answers, validation, scoped match access, deduplication, policy execution, queue state, communication receipts, relationship gates, retention, deletion and correction propagation.

  • Organization, jurisdiction, service and role resolution; privacy, relationship, emergency and deadline notice selection; channel, language and accessibility options; purpose, lawful-basis and authorization capture
  • Stable person, representative and organization identifiers; adverse and related party normalization; exact answer preservation; artifact digests; required-field and format validation; source, timestamp and correction checks
  • Tenant and matter isolation, conflict-review tokenization, no-result disclosure controls, protected-field exclusion, duplicate detection, deterministic service and capacity policy, queue assignment and access audit
  • Approved communication templates, recipient and channel authorization, delivery and handoff receipts, engagement gate, idempotent client and matter creation, retention and deletion timers, export, restore and correction checks
02

Bounded classification and summary support

A model may classify, summarize, translate and propose follow-up questions from approved intake data. It cannot decide conflicts, urgency, service, engagement or decline, disclose protected records or give advice.

  • Practice-area, jurisdiction, forum and service candidates with exact supporting answers, alternatives, missing fields, uncertainty and abstention rather than a hidden eligibility score
  • Source-linked enquiry summaries that distinguish the person's words, submitted artifacts, normalized facts and system inferences without adding motives, credibility or legal conclusions
  • Possible urgency, vulnerability, safety, fraud and deadline indicators routed to named review with approved emergency language, never presented as a diagnosis, legal calculation or completed safeguard
  • Translated approved questions and acknowledgment drafts with minimum data, no promises, no new advice and human review for material or sensitive communications
03

Qualified professional and enquirer authority

Qualified people determine duties, conflicts, service and relationship decisions, while the enquirer controls their instructions, corrections and any accepted engagement within applicable rules.

  • Prospective-client status, confidentiality and privilege, conflict and screening, competence, capacity, jurisdiction, engagement scope, important dates, legal advice and permitted disclosure
  • Urgency, safeguarding, vulnerability accommodations, emergency response, service fit, conflict outcome, decline and reason, referral, complaint, data rights, retention and deletion exceptions
  • Client identity and authority, instructions, objectives, informed decisions, accessibility and communication needs, engagement terms, signature, payment authorization and withdrawal
  • Professional supervision, workload and availability, intake and conflict policy, notices and templates, source and tool approval, privacy incident, expansion, rollback, provider replacement and retirement

Client-intake components

Build intake around the relationship boundary.

Notices, identities, conflicts, professional decisions and communications change independently. Four components preserve what the enquirer was told and what the organization actually decided.

01

Notice, purpose, and authorization registry

Version organization, jurisdiction, service and role; privacy, relationship, confidentiality, no-advice, no-engagement, emergency and deadline notices; purpose, lawful basis where applicable, authorization and withdrawal; field necessity, channel, language, accessibility, retention and deletion policy.

Operating contract: Displayed is not understood, consent is not always the lawful basis, privacy notice is not privilege, confidentiality language is not representation, emergency notice is not response, submitted is not accepted and one jurisdiction's notice is not universal.

02

Prospect, party, and enquiry registry

Bind enquirer, representative and contact authority; people, organizations, adverse and related parties and aliases; broad matter, jurisdiction, forum and important dates; exact statements, artifacts and digests; source, summary, inference, missing data, conflict and correction state.

Operating contract: Contact is not verified identity, representative is not automatically authorized, name match is not same person, user statement is not verified fact, summary is not advice, important date is not calculated deadline and intake access is not matter-wide access.

03

Conflict, service, and routing ledger

Run scoped duplicate, conflict-token, jurisdiction, service, capacity, fraud, safety, vulnerability, urgency and deadline-candidate policies; retain inputs, versions, exclusions, alternatives and uncertainty; assign review queues; and preserve qualified decisions without exposing other matters.

Operating contract: No candidate is not no conflict, conflict candidate is not disqualification, service match is not competence, capacity snapshot is not availability promise, urgent flag is not legal advice, protected trait is not commercial rank and model score is not a decline reason.

04

Disposition, communication, and relationship ledger

Preserve reviewer, authority, decision and reason; requests, acknowledgments, declines, referrals and safeguarding actions; exact relationship status and approved language; engagement acceptance; client, matter and permission creation; handoff, delivery, retention, deletion, complaint and correction receipts.

Operating contract: Acknowledged is not engaged, requested information is not acceptance, payment is not representation, conflict-cleared is not competent or available, engagement document is not accepted until required parties act, handoff is not complete until received and correction cannot erase prior notice or decision.

Delivery path

Prove one enquiry path before widening collection.

A large intake form can hide data and relationship risk. Begin with one service whose notices, minimum fields, professional decisions and handoffs can be reconstructed.

  1. 01

    Observe current intake

    Follow first contact, notice delivery, channel and accessibility support, minimum collection, identity and party resolution, conflict and service checks, urgency and safeguarding, professional review, requests, acknowledgment, engagement or decline, referral, client and matter creation, retention, deletion, correction, staff effort, provider cost, incidents and known harm.

  2. 02

    Define the intake contract

    Name notice, purpose, authorization, field, identity, representative, party, enquiry, source, candidate, policy, protected exclusion, reviewer, disposition, message, relationship, engagement, client, matter, handoff, retention, deletion, correction and harm fields and owners.

  3. 03

    Run shadow intake

    Replay ordinary, duplicate, alias, representative, adverse-party, conflict, wrong-jurisdiction, out-of-scope, no-capacity, urgent-date, safety, vulnerability, inaccessible, limited-language, unnecessary-sensitive-data, withdrawal, prompt-injection, decline, referral, no-response, deletion and corrected-identity cases against qualified outcomes.

  4. 04

    Release one controlled service path

    Limit services, jurisdictions, channels, fields and outputs; require notice receipts and qualified conflict, urgency and disposition review; reveal no protected records; preserve manual intake and emergency routes; gate relationship and matter creation; support access revocation, export, deletion, correction and independent stop authority.

  5. 05

    Review after final dispositions

    Compare minimum-data collection, source fidelity, identity and duplicate resolution, conflict-review safety, protected-field exclusion, professional edits, response clarity, handoff acceptance, retention and deletion, staff impact, accessibility, privacy incidents, provider and operating cost and harm before adding services or autonomy.

Client-intake safeguards

Six controls before an enquiry becomes a matter.

The strongest controls prevent overcollection, cross-matter disclosure, unreviewed rejection and ambiguous relationship messages.

Notice before collection
Resolve organization, role, jurisdiction and service; present current privacy, relationship, confidentiality, no-advice, no-engagement, emergency and deadline language in an accessible and understandable form; state purpose and retention; capture the applicable authorization and preserve withdrawal and display evidence.
Minimum staged data and exact-source separation
Justify each field by intake stage, defer merits and sensitive detail until necessary, preserve exact statements and documents separately from normalized facts, summaries and inferences, identify source and effective time, allow correction and prevent secondary use outside the authorized purpose.
Scoped identity and conflict review
Use stable identities, aliases and relationship candidates, isolate tenants and matters, minimize the facts exposed before conflict clearance, return opaque review tokens rather than other-client information, log access and require qualified resolution, screening, consent or decline decisions where applicable.
Fair service, urgency, and safeguarding candidates
Version service, jurisdiction and capacity rules, exclude protected characteristics and sensitive proxies from ranking, expose reasons and alternatives, provide accessible manual routes, route urgency and safety flags promptly and keep legal deadlines, competence, vulnerability and safeguarding decisions with qualified owners.
Qualified disposition and relationship-safe messages
Require named review for engagement, more information, decline, referral and safeguarding; use approved language that states receipt, relationship, next action and limits; prohibit advice and promises; obtain engagement acceptance separately; and create clients, matters and permissions only after authorization.
Security, retention, deletion, and recovery
Protect submissions and credentials, restrict downloads and notifications, scan files safely, scope provider and recipient access, test restore and degraded intake, retain only under approved policy and legal holds, support data rights and complete evidence export and propagate deletion and correction through every downstream copy.

Outcome proof

Measure owned dispositions, not forms submitted.

A high submission count can mean overcollection and confusion. Proof follows what the person was told, what was collected, who decided and whether the next owner accepted the handoff.

Baseline

  • Intake work by service, jurisdiction, channel, notice, authorization, person, representative, organization, party, enquiry, matter type, source, duplicate, conflict, service, urgency, safeguarding, reviewer, disposition, message, engagement, client, matter, handoff, retention, deletion, correction and known harm
  • Evidence by notice and field-schema version, display and authorization receipt, exact answer and artifact digest, identity and party candidate, policy and input version, protected-field exclusion, conflict token, source-linked summary, reviewer decision, message digest, engagement acceptance and handoff receipt
  • Manual notice support, accessibility and language assistance, data intake, identity and party resolution, conflict review, service and capacity review, urgency and safeguarding, professional decision, communication, engagement, referral, deletion and correction effort, queue age, interruption, provider fees and operating cost
  • Wrong notice, purpose, field, identity, authority, party, matter, source, conflict, jurisdiction, service, capacity, urgency, safeguarding, protected-trait use, reviewer, disposition, relationship message, recipient, engagement, permission, retention, deletion, correction, access, recovery and harm

Outcome evidence

  • More eligible enquiries reach qualified reviewers with correct notices, minimum source-linked data, resolved identity candidates, protected conflict checks, visible urgency and service uncertainty and owned gaps without creating an automated client relationship
  • Fewer overcollected, duplicate, wrong-party, cross-matter, unreviewed, inaccessible, unfairly ranked or ambiguously acknowledged enquiries persist, and every request, engagement, decline, referral, safeguarding, retention and deletion decision retains qualified attribution and reason
  • Enquirers receive clearer current-state and next-step messages while intake and professional teams spend less avoidable time rekeying approved fields and chasing routine missing information, retaining complete conflicts, competence, advice, safeguarding, relationship, correction and stop authority
  • Comparable cycles expose notice and field drift, identity and conflict disagreement, protected-field exclusion, reviewer changes, response and handoff delay, accessibility failures, retention and deletion, staff impact, privacy incidents, provider cost and harm without assuming qualification accuracy, conversion or legal outcome

Guardrails

  • Organization, jurisdiction, notice, purpose, person, representative, party, enquiry, source, conflict, reviewer, disposition or recipient is misbound; exact statements or authorization are lost; or protected, confidential or privileged data crosses tenant, matter, role, purpose, recipient or provider boundaries
  • Submitted form appears as engagement, acknowledgment appears as advice, important date appears protected, no conflict candidate appears cleared, identity candidate appears verified, capacity snapshot appears availability, payment appears retainer or opaque score appears a lawful decline reason
  • The agent decides prospective-client duties, conflict, competence, service, urgency, safeguarding, legal deadline, engagement, referral or decline; reveals other matters; ranks protected traits; contacts adverse parties; gives advice; opens a matter; or learns silently from professional decisions
  • Notice or policy changes are missed, review queues fail without escalation, owners leave without backup, emergency paths break, provider outage loses submissions, restore duplicates messages or records, deletion and corrections do not propagate or expansion precedes measured exclusion and harm

Client-intake fit

Use this pattern when every relationship state is explicit.

Good reason to begin

  • The organization can bound one service and jurisdiction, define notices, minimum fields, identity and conflict access, service and urgency policies, review and communication paths and name professional, conflicts, intake, privacy, accessibility, safeguarding, records, security, cost, harm and stop owners.
  • Notices, authorizations, people, representatives, parties, enquiries, sources, candidates, decisions, messages, engagements, clients, matters, handoffs, retention, deletion and corrections retain stable identifiers, timestamps and versions; originals reopen; and the full record is exportable.
  • Representative ordinary, duplicate, alias, representative, adverse-party, conflict, wrong-jurisdiction, no-capacity, urgent, safety, vulnerability, inaccessible, limited-language, overcollection, withdrawal, injection, decline, referral, deletion and corrected cases plus qualified outcomes exist for shadow evaluation.
  • Enquirers and professionals can correct facts, withdraw where applicable, use accessible manual channels, reject candidates, change dispositions, preserve conflict controls, block client and matter creation, revoke access, delete or retain lawfully, export evidence, roll back and retire the agent safely.

Resolve before beginning

  • Organization, jurisdiction, prospective-client duties, notices, minimum data, lawful basis, conflict process, service scope, competence, capacity, urgency, safeguarding, accessibility, engagement, referral, retention, deletion, complaint or correction ownership is unclear or disputed.
  • Exact submissions cannot be reopened, identities and parties lack stable identifiers, conflict checks expose protected matter data, field necessity is undocumented, review queues and handoffs are unobservable, engagement cannot be gated or no qualified professional can own the disposition.
  • The desired first step permits broad sensitive-data collection, undisclosed secondary use, autonomous conflict or decline decisions, protected-trait ranking, advice or deadline promises, unreviewed external messages, automatic matter opening or invisible learning from prospective-client information.
  • The business case depends on guaranteed confidentiality, zero conflicts, universal compliance, exact qualification accuracy, response times, conversion, reduced professional review, savings, revenue, implementation time, case success or another legal or financial outcome.

Source basis

Sources behind the control model.

  • 01

    American Bar Association

    Model Rule 1.18, Duties to Prospective Client

    The rule defines a prospective-client consultation, protects specified information even when no relationship follows and addresses later materially adverse work, consent, screening and notice. ABA Model Rules are not universal law; adoption and interpretation vary, and the rule does not make every website message a consultation or approve an intake result.

  • 02

    American Bar Association

    Formal Opinion 510, Prospective-Client Conflict Information

    The March 2024 opinion says preliminary information should be limited to what is reasonably necessary to decide whether representation is permitted, within capability and wanted. It analyzes ABA Model Rule 1.18, not every jurisdiction, and does not determine a specific prospective-client status, conflict, consent, screening or engagement.

  • 03

    Solicitors Regulation Authority

    Code of Conduct for Solicitors, RELs, RFLs and RSLs

    The current version in effect from 11 April 2025 addresses client instructions, own-interest and client conflicts, confidentiality and permitted disclosure for specified SRA-regulated professionals. Its scope is not universal, and it does not approve an intake tool, reveal another matter or automate conflict, engagement or decline decisions.

  • 04

    European Union

    General Data Protection Regulation, Regulation (EU) 2016/679

    Articles 5 and 13 require, where the Regulation applies, lawful and transparent processing, purpose limitation, minimum necessary and accurate data, storage and security controls and information when data is collected. Territorial scope, controller and processor roles, lawful basis, exceptions and local application require qualified assessment.

[ WORKFLOW / SYSTEMS AUDIT ]
THE FIRST ENGAGEMENT

Start with one real workflow

A Systems Audit is the usual starting point. If the opportunity is already clear, we can move directly into a focused build.

Show Us the WorkflowStart with the free automation readiness checklist

OBSERVEQUANTIFYDECIDEBUILD

Continue with the work

Choose the next useful path.

Stay with the operating question. The technology can wait until the work is clear.

01

Explore governed agent patterns

Compare intake with evidence-led legal, finance and operational agent patterns before selecting one exact service and relationship boundary.

Open path02

Prepare source-linked documents

Move only approved client, matter and instruction records into a drafting workflow with versioned precedents, redlines and qualified release.

Open path03

Keep urgent dates qualified

Route important-date statements into source and rule review without implying that an intake acknowledgment calculated or protected a deadline.

Open path04

Preserve legal professional authority

Connect prospective-client duties, conflicts, confidentiality, engagement, advice, accessibility, safeguarding and correction to qualified owners.

Open path