KeBao Cross-site customer service engine

Let the machine answer first.Put someone on.

Access AI × Response by Knowledge × All AutoRecall

Connect customer service across websites, WeChat, mini-programs, apps, and marketplaces to AI. Answer from approved knowledge, send offline alerts or automatic callbacks, and hand off to a person when needed.

Access Scripts and callback addresses are generated by station in the console. This station service is available on the right.

Access
ExistingAccess to AI
Response
By knowledgeAutomatic Reply
Call back.
Message.Full automatic access.
Transfer.
I can't.Get in line again.

Product

Product Modules

Click into any module to see how it works in the real scene. Client management, response strategies, talk hangars and backups continue in functional presentations. Web site and App access plugin; tripartite system open API or MCP.

01

AI Answers

FAQ precise matching, vector retrieval, continuation of large models, fixed three-tiered sequence. There is no library of knowledge.

Understood AI Response
02

Knowledge Base

A set of independent knowledge per site. Upload Word / PDF/ Web page, extract FAQ, and synchronize open documents with the help center.

Understanding the knowledge base
03

Live Support

Computer duty stations, mobile phone duty stations, Android client functions. Queue, sticky distribution, skill groups, relays and quality checks.

Get to know the manual duty.
04

Customer Management

To-do, 360 archives, business opportunities, follow-up and the high seas. The people who come in here are followed, not by a different kind of sales cloud.

Knowledge of customer management
05

Notification SMS

Only cloud manufacturers have reviewed the template: messages have been received, return confirmations made, and tickets closed. Not marketing.

SMS on call.
06

AI Callback

Do a task-based AI callback for offline messages. Connect to the same repository of knowledge; return to the watch station if you switch people.

Know Smart Callback
07

Channel Integrations

Connect existing online customer service to AI. Posters, public signs, applets, Apps, as well as microclinics and electric stores, are replaced by new places.

Get to know channel access.
08

Traffic Analytics

Open page to consultation. Real-time visitors, funnels, sources, click maps, and agenting and operation audits.

Getting to know the interview analysis
09

Integration Setup

Codes, styles, keys are all console. Copying scripts and echoes by station is effective when colours and entry styles are saved.

Know access configuration
10

Integration Plugins

Website command queue, App Official Shell, WordPress with npm. The same set of contracts opens the current web-based web-mounted installation without writing open API keys to the front.

Know access plugin
11

Introduction to All Functions

Response strategies, sandboxes, talk hangars, knowledge gaps, access controls, multilingual responses, backup migration are all included in the functional introduction.

Open function introduction

Platforms

Triangular platform supported

Only the official and accessible route. The directory is consistent with the system's "channel interface". The electronic store is subject to the authorization of the store and does not promise that a particular store will be connected.

Path

How do you finish a consultation?

All channels follow the same path. The desk is not changed and access is different.

01 Visitors ' questions

From anywhere.

Website bubbles, public signs, applets, Apps, help centres, or many / shivering shops, nailed sessions.

02 Knowledge first.

FAQ and RAG

Accurate questions and answers take precedence and documents and vector search follow. Inverted responses, with the same calibre as the help centre.

03 Model Bottom

Large model configured by site

Resumes when search is insufficient. It can be answered and quoted. OPC valuation plugins, etc., are active on site and do not contaminate other stations.

04 Follow up.

Line up to the line.

Sticky distribution, skill groups, SLA. Leave a message after work. The customer service centre can send a text message or make a batch of calls back to AI.

Desk

It's a queue, not a maze management.

On the left are pending and ongoing sessions, with dialogue in the middle and client information and follow-up records on the right. The session that was brought in manually had information that AI had already asked for, and the agent did not have to ask again.

  • Sticky distribution: Old visitors returned and found the last agent.
  • Skills groups: pre-sale, post-sale, technology diversion, automatic upgrading over time
  • Leave a message after work: No online messages; call from the customer service centre
The real interface for the computer desk: list of sessions, dialogue window and visitor information

SMS

Only reviewed templates issued for notification rather than promotion

Once the customer service centre has imported the list, it is possible to send a copy of the template that has been approved by the cloud manufacturer: messages have been received, visits will be made at some point, and tickets are closed. The text cannot be filled in freely. Could not close temporary folder: %s

  • Templates, sifters, mapping variables, preview numbers and then send them
  • Do not disturb, blacklist, 24 hours to weigh, day quota will stop.
  • Marketing / Extension Templates will be synchronized but not distributed
Client lists can be filtered by telephone, and imported for notification text messages

Voice

If you don't pick up your message, use the phone to get him back.

The operations centre does offline messages on a mission-based AI callback. Connect to the same repository of knowledge; return to the watch station if you switch people. Blacklist numbers, text messages and phone calls skip. The key is still in the system setting.

  • Call by batch: pause, plus sign, see the funnel; one can still ring immediately
  • Lines, ASRs, TTS are hosted by the TTL.
  • No prognosis, IVR hotline, agenting softphone.
Checklist: A number of offline messages can enter the callback queue

Plugin

Website and App, connect with plugins without rewrite chat windows

Access plugins are thin shells: web site command queue, App Official WebView shell, WordPress and npm. Organisation Login user can identify; do not write open API keys to the front.

  • Even if the script isn't loaded. aics('open') / identify
  • Android / iOS / Flutter / un-app / React Nature plugins/
  • Domain names to be registered Hosts; reasons are visible on the console when failure, and the visitors page is not red
Access code bullet window: Copy the command queue and entrance style by site