Installation and integrationsIn development
One script on the site, read-only account data
Designed for sites and platforms where a script can be added. The code will carry only a public site ID, the business’s server will sign the identity, and the move from the current tool will happen in stages.
Early access with hands-on help from the team. Ray is in development.
Paste before </body>
<script
src="https://widget.rai.example/v1/loader.js"
data-site-id="site_XXXXXXXX"
async
></script>Example. The real domain and ID will be provided when the site is activated.
InstallationIn development
Three steps, no secrets on the site
The widget will load only on the origins the business allows. No key or secret will travel in the site's code.
- Paste the script before
</body> - Sign the identity from the server
- Turn on by share of customers
Illustrative example of the allowed origins list in the console: two active origins and a button to add another one.
Illustrative example with sample data. Lumora is a fictional brand.
Signed identityIn development
The business will sign the identity, not the browser
The business's server will sign a short-lived identity. Without a valid signature, the customer will be treated as anonymous and Ray will not look up their account data.
The business's server
It will sign a short-lived identity for the customer signed in on the site.
Widget on the site
It will send that identity with the conversation. The widget's code will carry no secrets.
Ray will check the signature
Before looking up any account data, and only for that business.
Read-only tools
The status of an order, a shipment or a refund, with its update time.
Identified customer
Ray will be able to look up that account's data, read-only. The identity level will be visible to the team in the Inbox.
Anonymous customer
Ray will reply only from the published knowledge; for account data, it will ask the customer to sign in. A customer number typed in the chat will never be proof.
Account dataIn development
Ray will inform; the business's systems will not change
The business will choose which lookups Ray can make. All of them will be read-only: Ray will report a status, and refunds, payments and account changes will still be done by people.
Only what is needed
Each tool will return only the fields it needs. Names, ID documents and payment data will never reach the model.With its update time
Each piece of data will arrive with the time it was looked up. If it is out of date or incomplete, Ray will say so or hand the conversation over.If something fails, it fails safe
Without a connection to the data, Ray will answer only from the knowledge or hand over, and the administrator will get an alert.
Illustrative example of the enabled tools: the status of an order, a shipment and a refund, all read-only, and what happens if the connection fails.
Illustrative example with sample data.
MigrationIn development
Switch tools without turning everything off at once
The migration will move in stages and can be reversed. During the parallel run, each customer will see a single chat.
Import the existing knowledge
The export from the current support tool will become drafts with a cleanup report, and nothing will be published without review.Measure before going live
If the history can be exported and anonymized, past conversations will be replayed so the team can review the drafts.Parallel run
Ray will serve a group of customers while the current tool keeps the rest; the team will work both inboxes.A staged switch, with a way back
The share of customers will grow in stages, and a switch on the business’s side will send new sessions back to the previous chat.Share of customers on Ray
Illustrative example. The stage 04 switch shows how new sessions go back to the previous chat.
ExportIn development
The data will still belong to the business
Each business will be able to export its conversations and its knowledge at any time, in a documented format. Nothing will be tied to Ray.
Illustrative example of the export screen: conversations and knowledge, each with its export button.
Illustrative example with sample data.
Plan the installation and the migration
A short conversation with the team that builds Ray to review the company’s case: frequent questions, existing knowledge, sensitive topics and a migration plan.