AI Assistants

Customer support automation

Planned support help that would answer common questions, sort requests, and route the rest to the right person.

PlannedDelivery: To be confirmed
Planned: not available yetThis page describes how the service is designed to work. It isn't offered yet, and we won't give a launch date until it's ready. You can register interest and we'll let you know.
The problem

The same support questions arrive again and again.

Intended outcome

Common questions answered, requests triaged, and issues routed to the right person.

Delivery

To be confirmed

Boundaries

Assists your team; it does not replace people entirely.

Overview

How it is designed to work

This service is planned and not available yet. It's designed for businesses where the same support questions arrive again and again by email, chat, or web form. When it launches, it would answer common questions from approved content, sort incoming requests by type and urgency, and send each one to the right person on your team.

It's meant to assist your team, not replace it. Complaints, refunds, billing disputes, and anything sensitive would go to a person by default. Vyybe has designed its own inbox assistant the same way: routine enquiries would get a reply, while anything about pricing, contracts, or complaints waits for a person.

What it looks like

A walkthrough of the intended experience

For example, here's how support could run for a small home-cleaning company once the service launches. This is an illustration, not a real client.

  1. Requests arrive overnight

    By morning there are a dozen messages: rescheduling requests, questions about what's included, a lost-item report, and one unhappy customer.

  2. Routine questions get approved answers

    Questions like "Do I need to be home?" get a reply drawn from your approved answers. Each reply says it was written with AI help and invites the customer to reply if they need a person.

  3. Requests are sorted and labelled

    Reschedules go to the scheduler. The lost-item report goes to the crew lead. Each message is tagged so nobody has to read everything first.

  4. Sensitive messages wait for a person

    The complaint and a refund request aren't answered automatically. They're flagged as needing you, with a suggested draft you can edit or ignore.

  5. Urgent issues are escalated

    A message about a possible safety issue matches your urgent rules, so it alerts the owner directly instead of waiting in a queue.

  6. You see the whole picture

    A simple view shows what was answered, what's waiting, and who owns each request. You can correct any answer and improve the approved content.

What it does

What it is designed to do

  • Answers common questions

    It would reply to routine questions using only content you've approved, and say when it doesn't know.

  • Triage and labelling

    It would sort incoming requests by topic and urgency, so the right person sees them first.

  • Routing to the right person

    It would assign requests to the team member or queue you choose, based on rules you set.

  • Holds back sensitive topics

    Complaints, refunds, billing, contracts, and similar topics would wait for a person, optionally with a draft reply.

  • Urgent escalation

    Messages that match your urgent rules would alert a person directly.

  • Drafts for review

    Where you prefer, it would prepare draft replies for your team to approve instead of sending them.

  • Limits on automatic replies

    It would skip auto-replies, newsletters, and no-reply senders, and cap how often one person gets an automatic reply.

What it can do for you

Why it can help

  • Faster first responses

    Routine questions could get a reply without waiting for someone to reach the inbox.

  • Less repeated typing

    Your team would spend less time writing the same answers and more on issues that need judgement.

  • Fewer missed requests

    Sorting and routing would make it clearer who owns each message.

  • Sensitive issues stay personal

    Upset customers and money matters would still reach a person, which is usually what they want.

  • Answers that improve

    Reviewing replies over time would show where your approved content needs work.

Who it's for

Is this a good fit?

  • Businesses that receive many similar customer questions each week
  • Small teams where support is shared between people with other jobs
  • Owners who want consistent answers without writing each one by hand
  • Businesses that need clear ownership of each request
  • Probably not the right fit if you get only a few support messages a week, or if most of them need careful, individual judgement

How we work

From first conversation to a working setup

  1. Discovery

    We'd review where support requests arrive, the most common questions, and how your team handles them today.

  2. Scoping in writing

    We'd agree channels, approved answers, routing rules, topics that always go to a person, and what sends automatically versus as a draft. Scope and price are confirmed in writing before work starts.

  3. Setup

    We'd connect to your inbox, chat, or forms where practical, load the approved content, and set up the routing.

  4. Supervised trial

    We'd typically start in draft-only mode, so your team approves every reply until you're confident in it.

  5. Launch and ongoing review

    After switching on any automatic replies, you'd review samples regularly and we'd update content and rules within the agreed scope.

Scope

What's included, and what isn't

Typical scope. Exactly what's included is confirmed in writing for each project.

Typically included

  • Approved answers for your most common questions
  • Triage, labelling, and routing rules
  • List of sensitive topics that always go to a person
  • Draft-only mode before any automatic replies
  • Urgent-issue alerts
  • Exact scope is confirmed in writing after a short scoping conversation

Not included

  • Replacing your support team
  • Automatically issuing refunds, credits, or account changes
  • Handling legal disputes or formal complaints without a person
  • Marketing messages to customers who haven't opted in
  • Help-desk software subscriptions and AI usage, which may carry their own costs

What you'll provide

  • Your common support questions and the answers you approve
  • The channels where requests arrive and access to them
  • Who handles which kinds of requests
  • The topics that must always go to a person
  • Your rules for urgent issues and who should be alerted

Safeguards

Controls built in

  • Replies use only approved content and are clear that AI helped write them
  • Sensitive topics such as complaints, refunds, and billing always go to a person
  • Draft-only mode is available, and is typically the starting point
  • Automatic replies are rate-limited and skip no-reply and automated senders
  • Urgent messages alert a person directly
  • You can turn off automatic replies at any time

FAQ

Questions owners ask

Is this available now?

No. Customer support automation is planned and not yet offered. We're glad to hear what you need, and we'll be honest about timing. We don't give launch dates.

Will it replace my support staff?

No. It's designed to handle routine questions and sorting so your team can focus on the conversations that need a person.

What happens if it doesn't know the answer?

It wouldn't guess. The message would go to the right person, with a note that no approved answer matched.

Can I approve replies before they're sent?

Yes. Draft-only mode would let your team approve every reply. Many businesses would likely stay there for some topics permanently.

Which channels can it work with?

Email, website chat, and web forms are the most likely starting points. Other channels depend on your tools and their permissions, and would be confirmed during scoping.

Interested when it launches?

Leave your details and we will let you know when it is ready. No commitment.

Register interest