AWL Consultores brought conversational AI into client onboarding and SmartDocs, connecting customer conversations to the legal workflows that follow.
Customer: AWL Consultores
Industry: Legal Services / Alternative Legal Services
Headquarters: Santo Domingo, Dominican Republic
Reach: Dominican Republic, Colombia and broader Latin America
Use cases: Client intake and legal document completion
Outcome: More efficient onboarding and a simpler path through document-heavy legal workflows
Implementation: Two conversational workflows , AWLi and SmartDocs
A person looking for legal help usually does not arrive with perfectly organized information.
They know they need a contract. Or advice on a business issue. Or help with a property transaction. The legal provider still has to understand the situation, collect the right details, decide what happens next and, in many cases, prepare a document that requires yet another round of information from the client.
For AWL Consultores, that created two practical opportunities for conversational AI.
The first was AWLi, where prospective clients could explain their legal requirement conversationally instead of relying entirely on manual intake. The second was SmartDocs, where conversation could guide customers through the information required to complete legal documents.
AWL used NitroStack to connect those conversations to actual workflow steps. The AI was not there simply to answer questions. It had work to do.
How do you automate legal intake without making it feel like another form?
AWL operates differently from the traditional model of a single law firm organized around one fixed group of lawyers. Its legal-service network brings together independent specialists across the Dominican Republic and Colombia, with broader reach across Latin America and practices spanning corporate matters, contracts, labor, real estate, tax, intellectual property, data protection, dispute resolution and emerging technologies.
That range creates an intake problem before legal work even begins.
A prospective client has to explain what they need. AWL has to collect enough context to understand the request, capture the person's contact information, and move that opportunity into the operational process where a client and corresponding job can be created.
Doing all of that manually works, but it consumes human attention at one of the most repeatable stages of the relationship.
The obvious alternative would have been a larger intake form. That would move data entry to the customer, but it would not necessarily make the experience easier. Legal requirements are rarely expressed in the same vocabulary as database fields.
AWLi takes a different approach.
A customer can begin by explaining the legal requirement as they understand it. The conversation gathers the information needed for the next step and connects that information with AWL's client and job-creation workflow.
Instead of:
Contact → manual intake → organize information → create client/job
the interaction can move toward:
Conversation → structured client information → client/job creation
The workflow stays structured behind the interface. The customer does not have to experience all of that structure at once.
AWLi turns the first legal conversation into usable intake data
That distinction is what makes AWLi more than a website chatbot.
A general-purpose legal chat could answer a question and stop there. AWL needed the conversation to participate in the actual intake process.
With NitroStack providing the application layer behind the conversational workflow, the information collected during an AWLi interaction can be tied to the actions AWL needs to perform next. A legal requirement is not left sitting in a transcript waiting for someone to manually translate it into operational data.
The conversation becomes an entry point to the workflow.
This pattern is particularly useful for an organization serving many legal areas because customers do not need to understand AWL's internal classification of services before beginning. They can start from the problem they actually have.
That does not remove the lawyer from the process. Nor should it. Specialized legal judgment still belongs with AWL's legal professionals.
What changes is the work required before that judgment becomes relevant. Repeatable information gathering can happen conversationally, leaving the legal team with a more structured starting point for the matter that follows.
SmartDocs applies the same idea to a harder interface: the legal document
Client intake was one part of the problem. Documents introduced another.
A downloadable legal template sounds simple until someone has to complete it.
Different documents require different facts. The appropriate wording or version may depend on the customer's circumstances. A person purchasing a document may also be seeing some of its questions for the first time and may not immediately understand what information belongs where.
This is where AWL's SmartDocs workflow takes the conversational model further.
Rather than putting a legal template in front of the customer and expecting them to navigate every field independently, SmartDocs can guide the information-gathering process through conversation. The answers are then connected to predefined document templates and the rules needed to produce the appropriate version.
AWL is applying this approach to repeatable legal documents such as labor contracts and vehicle sale agreements.
The underlying sequence is straightforward:
Customer need → guided conversation → required information → appropriate document version → completed legal document
There is still structure. There has to be. Legal documents cannot be assembled from vague context alone.
What changes is how that structure is presented to the person completing the document.
Instead of requiring the customer to understand the form before they can use it, the application can ask for the necessary information in a more natural order and progressively build the inputs the document workflow needs.
Why conversation matters more when it can trigger a real legal workflow
AWLi and SmartDocs solve different problems, but technically they share an important characteristic.
The conversation has consequences.
In AWLi, collected information can contribute to creating the client and the related job. In SmartDocs, the conversation supplies the structured inputs required to select and complete the appropriate document workflow.
That is where NitroStack becomes useful to AWL.
NitroStack provides infrastructure for building AI applications where models can interact with defined application capabilities rather than remaining isolated inside a question-and-answer window. Through tool-driven workflows, the conversational layer can collect structured inputs and connect those inputs to the underlying actions the application needs to perform.
For AWL, the legal expertise and business rules remain part of AWL's systems and services. NitroStack provides a path for the conversational experience to reach them.
This separation also matters from a product perspective. AWL does not need to turn every internal legal process into an AI-generated answer. It can choose the repeatable points where conversation genuinely reduces friction, expose the required actions, and keep specialized legal work where human expertise is needed.
The same architecture can support two noticeably different user journeys without pretending they are the same problem.
AWLi asks, in effect, What do you need help with, and what information do we need to start the matter?
SmartDocs asks, What do we need to know to produce the right document for your situation?
NitroStack sits underneath both as the layer connecting that conversation to application behavior.
What changed once conversation became part of the legal process
The operational benefit is easiest to see by looking at where human effort was previously concentrated.
During intake, people had to collect and organize information before the matter could move forward. AWLi gives prospective clients a direct conversational route for supplying that information and connecting it with the next operational step.
During document completion, customers could face the opposite problem: too much structure with too little guidance. SmartDocs introduces guidance while still gathering the precise information the document requires.
Neither workflow attempts to automate the whole legal service.
They remove friction around specific, repeatable parts of it.
That matters for AWL's broader service model. A network of specialized lawyers still handles work requiring legal expertise, while the customer-facing process around that expertise can become more consistent and easier to enter.
The result is not “AI replacing legal services.” It is a different division of labor.
Conversation handles more of the repetitive gathering and routing of information. AWL's legal workflows retain the structure. Lawyers retain the specialized work.
From “tell us what you need” to an actionable workflow
AWL's implementation shows two ways conversational AI can become useful inside a professional-service business without swallowing the rest of the operation.
AWLi turns the beginning of a client relationship into structured intake that can move toward client and job creation. SmartDocs takes another repetitive but difficult interaction, collecting the information required for legal documents, and guides the customer through it conversationally.
NitroStack connects those interfaces to real application actions.
That is a more practical role for conversational AI than adding a general chat window and hoping customers find something useful to ask. The conversation begins with a specific job, gathers information for that job and hands structured inputs to the workflow responsible for finishing it.
For AWL, the next opportunities do not require inventing an entirely different architecture. The same pattern can be applied selectively wherever another legal process contains repeatable information gathering, structured decisions and a clear handoff into specialist work.
Teams building similar tool-driven conversational applications can explore the NitroStack SDK and NitroStack documentation to see how application actions can be exposed to AI while the underlying business logic remains in the systems that already own it.