Eliminating lead drop off by using service pricing files on voice and message channels
Prevent lead loss by using your existing pricing PDFs and documentation to power AI voice and message agents for after hours inquiries.
The Cost of After Hours Silence
A customer calling a service business after 5:00 PM usually reaches a voicemail or a generic recording. Most callers hang up rather than leave a message. They move to the next Google search result until a human answers. Marketing spend is often wasted on clicks that cannot be converted in real time. This failure to respond contributes to the phone line bottleneck where call centers sabotage marketing budgets.
Static contact forms on a website function similarly. A prospect fills out their details and waits for a response that might come the next morning. By then, the urgency has often passed. Duvi addresses this by using the information already on your website and in your files to handle these inquiries immediately. This approach helps in capturing lost leads by resolving specific technical objections in real time.
Grounding Responses in Technical Data
The setup process involves pointing Duvi at a website URL or uploading a folder of documents. The platform crawls these pages and parses the files into a vector store. When a customer asks about service areas or specific pricing, the agent retrieves the answer from this real content. It does not guess. It uses your specific data. This ensures you are aligning service eligibility checks across phone and web using real time API integration.
A plumbing company might have a PDF listing twenty different service zones and their associated call out fees. If a customer calls the business number, the Duvi agent answers. It identifies the caller location and provides the exact fee from that PDF. This happens via a live voice conversation on the phone or a message on WhatsApp. Using these agents is an effective method for automating immediate voice responses to capture overflow leads.
Unified Knowledge Across Surfaces
The conversation stays on the channel the customer chose. If they send a message on WhatsApp, the reply goes back there. If they call, they hear a voice. The knowledge remains identical across these surfaces. You do not need to configure separate logic for the website chat and the phone line. Maintaining this consistency prevents the context loss often seen when customers switch communication channels.
Agents move beyond providing information by using tools. A business can connect its own HTTP APIs or Salesforce instance to the agent. This allows the agent to check technician availability or create a new lead record during the conversation. If a customer wants to book a repair, the agent calls the scheduling API to find an open slot. This is a core part of reducing operational lag by enabling direct API execution in voice conversations.
Deployment and Optimization
Implementation requires three specific steps. First, you select a model. Second, you provide the source material. Finally, you connect the communication channel through a provider like Twilio or Meta. The agent handles the intake and qualification. If the inquiry becomes too complex, the system supports a handover to a human operator. This helps in managing lead qualification latency across distributed channels.
Analytics provided by the platform show where customers are dropping off or what questions the agent could not answer. This feedback loop allows for precise adjustments to the uploaded documentation. If multiple callers ask about a warranty policy that is not in the system, you upload that policy and the agent learns it instantly. Usage is managed through a credit system. Businesses pay for what they use rather than maintaining a large team of after hours dispatchers. This reduces the cost per conversation while ensuring no lead is ignored because of the time of day or a high volume of simultaneous calls. Any completed conversation can be recorded and analyzed to improve the response quality.