Providing technical documentation to field teams through voice and messaging

Overcoming the mobile documentation barrier

Most technical documentation stays trapped in PDFs that are difficult to read on a mobile device. When a technician or a customer is in the middle of a setup process, they often need a specific torque setting or a wiring diagram. Navigating a mobile website with nested sidebars is a failure point that leads to expensive support calls. This happens because knowledge bases are often hidden from customers who need immediate answers while working.

Documentation is usually designed for a desktop browser, while the actual work happens in the field. A customer standing in a dark utility closet or a technician on a ladder cannot effectively search a 50 page manual. They need the specific answer delivered through a medium that allows them to keep their hands free or stay within a familiar chat interface.

Moving knowledge into the field

Duvi allows a business to take existing technical material and make it available via a phone call or a WhatsApp message. The process starts by pointing the Duvi crawler at a documentation site or uploading specific files. The platform parses these files into a vector store. This ensures that when a customer asks a question, the response is grounded in the actual facts of the product manual rather than a generic guess. Anchoring multi channel agents to a single technical knowledge base prevents conflicting answers across different support platforms.

The agent handles the request based on the channel the customer chooses. If they call a Twilio phone number connected to Duvi, the agent uses voice to relay the specific steps for a hardware reset. If they send a photo of a serial number via WhatsApp, the agent can use that context to provide the correct firmware version. The knowledge remains consistent because every channel pulls from the same indexed source.

Handling technical variables with APIs

Static knowledge is often insufficient to resolve a technical hurdle. A technician might need to know if a specific unit is still under warranty or if a part is in stock before they proceed with a repair. These details live in a CRM like Salesforce or an internal inventory database. A Duvi agent can be configured to call HTTP APIs to pull this real time data. The agent checks the database and provides the answer immediately to avoid telling the customer to call back during business hours. If the agent identifies a hardware failure that requires a physical replacement, it can trigger a workflow in an external system to ship the part.

Managing the transition to human support

There are moments when automated guidance reaches its limit. A complex wiring issue might require a human engineer to look at a photo. Duvi allows for a handover to a human agent when the automated agent cannot find a confident answer in the knowledge base. When a handover occurs, the human agent receives the full context of the conversation. Solving the context reset ensures the technician does not have to repeat serial numbers or steps already taken. Because the agent records calls and logs messages, the business can review these handovers later to see where the documentation was lacking.

Refining the agent logic

The performance of a field support agent depends on the quality of its instructions and the state of its index. In the Duvi agent builder, you describe the job the agent should perform. This is refined through a six block system prompt where you define the rules for the conversation. One block might specify that the agent must always ask for a serial number before giving technical advice. Another block tunes the voice output for clarity over a phone line. Preventing knowledge drift requires using the same agent logic for both voice and text channels.

Monitoring the indexing state is part of the maintenance. Duvi provides visibility into whether a file is currently being processed or if an index has failed to return results. If a new product version is released, you update the knowledge by adding the new manual or re crawling the site. The agent on the phone line and the WhatsApp business account are updated instantly without any changes to the underlying code. This allows the support team to keep pace with product updates without waiting for a developer to update a hardcoded decision tree.