API integration for service appointment changes across phone and WhatsApp

A customer calls to move an appointment and waits on hold for six minutes before hanging up. Ten minutes later, they send a WhatsApp message that stays unread for four hours. By the time a staff member replies, the desired slot is taken. The customer has already found a different provider.

Managing calendar updates is a high volume task that requires access to internal scheduling software. When these requests come in through different channels, the risk of double booking or missing a message increases. Most businesses try to solve this by adding more staff to the phones or assigning a dedicated person to monitor WhatsApp. This increases the cost per conversation without necessarily improving the speed of the resolution. Manual data lookups stall support operations and create friction when the customer is forced to wait for a person to check a database.

Duvi handles these requests by connecting the same intelligence to every communication channel. If a customer calls your business number, the agent answers in a human voice. If they message your WhatsApp Business account, the agent replies with text. The knowledge used to answer remains identical because it comes from the same source. Setting up the agent starts with the material you already have. Duvi crawls your website and parses uploaded files to understand your specific services. This information is stored in a vector store. It allows the agent to provide answers based on your business rules. There is no need for manual programming to get the agent to understand your service hours or cancellation policies.

Knowledge alone is not enough for scheduling. An agent needs to act. Duvi uses HTTP APIs or MCP servers to talk to your existing booking software or CRM. Connecting support agents to live business data enables the AI to move beyond simple chat. When a customer asks to move an appointment from Tuesday to Thursday, the agent checks the available slots in your system through an API call. If the slot is open, the agent updates the record and confirms the change.

This interaction happens in real time. On a phone call, the agent speaks the confirmation. On WhatsApp, it sends a message. Because the agent uses your own Twilio or Meta account, the customer sees the message coming from your verified business number. The context of the conversation is never lost. This prevents the customer churn that often occurs when a person switches between browsing a website and sending a mobile message.

If a request becomes too complex, the agent can hand the conversation over to a human. This ensures that the automation handles the bulk of the repetitive work while high priority issues get the attention they require. All completed conversations are analyzed into insights. This provides a view of which service times are most requested.

Deploying this system requires no engineering work. You provide the script tag for the website and connect your messaging accounts. The builder interface handles the creation of the agent through a conversational setup process. Costs are managed through credits. Charges only occur when the agent handles a conversation. This removes the overhead of fixed monthly salaries for 24 hour coverage.

The consistency of the experience matters as much as the speed. Aligning service eligibility checks and scheduling logic across channels ensures that a customer who starts on your website gets the same answer when they follow up via a phone call. By anchoring the agent to a single knowledge base and the same set of API tools, the information gap between channels is closed.