Skip to main content
RoutMe

Buyer guide

How to choose an AI customer support agent

By the RoutMe team. Last updated .

To choose an AI customer support agent, evaluate how it gets its facts, what it is allowed to change, how it hands off to people, which channels it supports, how pricing works, and what evidence the vendor offers. Score each product against the same checklist using your own real questions, and treat undated roadmap items as unavailable.

Step 1: define the job

List your ten most common inbound questions, and mark each as a document question (policy, how-to), a record question (order, account) or an action (refund, change). The mix tells you what the agent needs. See RAG vs tools.

Step 2: the evaluation checklist

AreaQuestions to askWhat good looks like
GroundingWhere does each answer come from?Live lookups and your documents, with sources
Data accessWhich systems and permissions are needed?Narrow, scoped, read-only credentials
SafetyWhat can it change? Can a prompt change that?Enforced in tools and credentials
VerificationHow does it confirm who is asking?Checks in code, not in the prompt
HandoffWhat does a person see?Full conversation and lookups
ChannelsWhich are live? Which are planned?Live and planned clearly separated
Platform rulesHow are WhatsApp opt-in and windows handled?Enforced by the platform
ObservabilityAre lookups logged?Reviewable logs
PricingWhat is charged and by whom?Dated, itemized, including third-party fees
ProofWhich claims have evidence?Certifications named with reports, or stated absent
ExitCan you leave?Your data and tools stay yours

Step 3: run a bake-off with your own questions

  1. Take your ten questions, plus five the product should refuse.
  2. Run them through each candidate with the same data.
  3. Record whether each answer was correct, sourced and appropriately cautious.
  4. Test a wrong order number, a request for another customer's data, and a request to change something.
  5. Ask for a person and see what happens.

Step 4: read the claims critically

Watch for these:

  • Percentages with no source or date.
  • Logos and testimonials you cannot verify.
  • "Certified" or "partner" claims for platforms. Check the platform's own directory.
  • Roadmap features sold as live.

A vendor that says plainly what it does not have yet, as RoutMe does on its Security page where it states it holds no SOC 2 or ISO 27001 report today, is giving you information you can use.

Step 5: price the whole thing

Ask what you pay the vendor and what you pay third parties. WhatsApp, for example, bills per message, and the rates depend on the message category and the recipient's market. See the dated explanation on the pricing page.

Where RoutMe stands against the checklist

  • Grounding: MCP tools to your systems, plus knowledge sources.
  • Safety: the chat assistant is offered only tools marked read-only.
  • Handoff: shared inbox with the full thread.
  • Channels: WhatsApp and website chat are live. Other channels are labeled coming soon on the channels page.
  • Not available today: a Shopify app, native platform connectors, and the one-import API to MCP path, which is in progress.

If you want to compare named products, run the checklist on each and keep the results. Treat any third-party scorecard as a starting point and verify the claims yourself.

Scoring the results

Give each area in the checklist a score from zero to two: zero for no evidence, one for a claim without a demonstration, two for something you tested yourself. Add the scores per product, but weigh the areas by your own risk. A store that handles payments should weight safety and verification more heavily than channels, while a store with most traffic on WhatsApp should weight platform rules first. Keep the raw notes, not only the totals, because the reasons behind a score are what you will want when the contract renews or when something goes wrong. Share the notes with whoever handles your legal and security review, so they can ask their own questions against the same facts.

Sources

Explore the product: RoutMe for Shopify, solutions and the documentation.

Frequently asked questions

How many vendors should I test?

Two or three, with the same test set.

Should I choose an all-in-one helpdesk or a specialist agent?

It depends on where your team works today. Evaluate both against the same checklist.

What if my data is messy?

Start with documents and one clean lookup, then expand.

Put these ideas to work