Services AI customer support

AI support that resolves, then hands over.

Modulus Labs AI builds chatbots and support agents that answer from your own content, act in your order, booking and help desk systems, and pass the conversation to your team with a summary when a person should take it.

Channels
Web chat · WhatsApp · Email · Your help desk
Answers from
Your help content · Policies · Live order and booking data
Measured on
Resolution · Handover quality · Accuracy · Customer rating
Credential
NVIDIA Inception member since July 2026
Reply time
Within one business day

01 What we build

Support that finishes the job.

Most companies need one or two of these at first. We start where your queue is longest and the risk is lowest.

Fig. 1 The agent answers, a person takes over
  1. 1.1

    Self-service agents

    Answer status, how-to and policy questions, and make simple changes in your systems within the limits you set. On WhatsApp too: WhatsApp AI agents.

  2. 1.2

    Agent assist

    Draft replies, summarise the case and find the right policy for your team, with a person reading every reply before the customer does. The lowest-risk place to start.

  3. 1.3

    Routing and triage

    Classify each message, set its priority and send it to the right queue, with the details a person needs already collected.

  4. 1.4

    Conversation review

    Read conversations to find the top reasons for contact, failed answers and gaps in your help content, so the fixes go where they count.

02 How we build it

Grounded, limited, measured.

What separates support customers trust from a chatbot they try to escape.

03 In production

Systems already running.

Our WhatsApp agent handles 70% of a solar company's monthly sales and hands buyers to the sales team when it should, with a 4.8 out of 5 customer rating and 99% uptime. The same core of knowledge, system access, rules and tests can sit behind web chat and email.

  1. 3.1

    Do we need a chatbot or an AI agent?

    A chatbot answers from your content. A support agent also acts in your systems: it looks up the order, reschedules the booking or updates the address. Most support teams start with answers and add actions one at a time, each with its own limit.

  2. 3.2

    When does it hand over to a person?

    When the customer asks for a person, after two failed attempts at the same question, when nothing relevant is found, when an action is above a limit, on complaints or signs of distress, and when one of your systems is down. These rules run in code before the reply, and the person receives a summary so the customer never repeats themselves.

  3. 3.3

    How do you measure whether it works?

    On resolution, not containment: a conversation counts only if no person was needed and the customer didn't come back about the same issue within seven days. We also track escalation reasons, handover quality, customer satisfaction against your human baseline and accuracy on a weekly reviewed sample.

  4. 3.4

    How long does a project take?

    A focused system usually reaches production in six to ten weeks; larger integrations take three to five months. Discovery comes first, so you see the plan before any build.

  5. 3.5

    Who owns what we build?

    You do: the code, prompts, evaluation sets, infrastructure and documentation. When we hand over, your team can run and extend it.

Hiring a team to build one? Read the questions to ask an AI development company and how to test an AI system before you accept it.