A new enquiry reaches the firm in three ways: through the website form, by email to a shared Outlook mailbox, or by a phone call after which the receptionist writes an email. It is often a long story without dates and with photos attached. The receptionist reads it, tries to work out which practice area it belongs to, asks for the client's company registration number, checks Clio to make sure the firm does not represent the opposing party, and only then forwards it to a lawyer. If a colleague is on holiday, the enquiry waits for days, and the client writes to another firm in the meantime. Worse happens too: a conflict of interest is noticed only after the first meeting.
The agent takes over the first step. From the website form or the Outlook email it collects the facts: who is contacting the firm, who the opposing party is, the substance of the dispute, amounts, deadlines and which documents are attached. If something is missing, it asks the client in a single structured email. It checks the parties and related persons against the client and opposing-party list in Clio, and verifies company details against an extract from the business register. Then it creates an unconfirmed matter record in Clio with a summary of the facts, the conflict check result and the attached documents, and notifies the responsible lawyer in Teams. To the client, the agent says only that the enquiry was received and when to expect an answer from a lawyer. It does not explain the law, even if the client asks directly. We build the agent in Copilot Studio in your Microsoft 365 tenant, and the email text with the matter facts is processed by a model in MDP CLOUD's private GPU cloud in Lithuania (EU) or by Claude through Amazon Bedrock in an EU region, with no training on your data and with a log in line with GDPR.