ComparisonPlatform evaluation

Compare Kuga, Chatbase and Dante for client delivery

Use one client brief to evaluate the required setup in Kuga, Chatbase and Dante. Check the saved enquiry, source maintenance, agency operation and current plan requirements in each product.

In this guide

What you’ll finish with

A documented comparison with the same acceptance criteria and current plan checks for each product.

Before you begin

  • A client brief and approved sources.
  • Access to the relevant product experience for each evaluation.
  • A list of essential features and a consistent test record.

Check the current product scope

Chatbase’s Experts programme describes support for agencies, client management and an agency dashboard. Evaluate that experience directly rather than assuming Chatbase only serves a single business. Dante describes website and file knowledge, branding options and additional capabilities across its plans. Verify the exact tier needed for your service.

Kuga organises the service around agency and client workspaces, shared workflows and supported channels. Its plan requirements also matter: Preview supports building and testing, while features such as social channels, Insights and portal access need the relevant paid client plan.

Prepare one client task for all three

Use the same approved website pages and current file, the same response role and the same questions. Include the client’s enquiry or booking requirement so the comparison extends beyond a factual answer.

Record which features require setup, an external destination or a paid plan. If you cannot test a required capability, mark it as unverified rather than treating a product description as a completed check.

Shared test brief

Answer: [question with an approved source]. Missing information: [question the source does not answer]. Enquiry: [request that requires useful context]. Saved outcome: [fields and destination to inspect]. Source change: [one fact to update and retest]. Agency operation: [second client, branding and reporting requirements].

Run the Kuga journey

In KugaClient workspace › Knowledge

Connect the agreed source set, configure the relevant Contact Requests or Scheduling workflow and set the general response instructions under Agent > Configuration. Run the questions in Test.

Inspect the saved Contact Request or the booking outcome. If the client needs an external destination, configure the supported Webhooks event and use Send test. Review the equivalent process in the other products using their current documented setup.

  1. Prepare Knowledge from the shared source set.
  2. Configure the required workflow.
  3. Run the answer and missing-information tests.
  4. Complete the enquiry or booking journey.
  5. Inspect the saved result and delivery.

Compare the usable result the client receives, not only the wording in the conversation.

Score the operating requirements

Review a source change, a second client, branded surfaces and the reporting process. Include the time and tools needed to deliver the service you are quoting.

Check current vendor pricing and terms at the point of decision. Avoid comparing entry prices when the required agency or client features need a different plan.

CriterionRecord for each product
Answer qualityExpected source, observed answer and fallback
Enquiry outcomeSaved fields, context and receiving destination
MaintenanceSource update and retest process
Agency deliverySeparate clients, access and branded surfaces
ReportingAvailable evidence and report coverage
CostRequired plan and additional delivery work

Make the decision reviewable

Record Pass, Needs work or Unverified for each requirement, with the reason. Use the client’s essential requirements to make the decision rather than adding every possible feature to the score.

Keep the test date and product plan with the record. Revisit it when the service adds channels, volume or a new follow-up process.

Pick a client you know.

Show them their AI.

Use their website to build a demo. Put your name on it and let them try it.