API connectionIn development
Answers with the data of each customer, read-only
If the business has its own API, Ray will be able to query it to answer with the real status of an order, a plan or a booking. Only for customers with an identity signed by the business, always read-only, with every query logged for the team.
Early access with hands-on help from the team. Ray is in development.
Illustrative example of the site chat with the customer signed in: the customer asks whether the order has shipped and Ray replies with the ship date, the estimated delivery, the path to track it and the time of the data.
Illustrative example with sample data. Lumora is a fictional brand.
Before and after
The same question, with and without the connection
Without the connection, Ray will reply with the published knowledge. With it, Ray will reply about the customer's own case. Either way the customer will get a written reply, with no sources and no raw data.
Illustrative example in three panels. Without the connection, Ray explains the general refund time and the path to check it. With the connection, Ray says the refund for order 10482 was approved, the latest credit date and the time of the data. In the console, the team sees the verified identity, the read-only lookup, the names of the returned fields and the source of the time frame.
Illustrative example with sample data. Lumora is a fictional brand.
What is looked up
A closed set of read-only lookups
The business will choose which lookups to turn on, among operations defined and reviewed with the Ray team. Ray will not build free-form requests to the API: each lookup will have fixed fields and will carry no customer data as a parameter.
E-commerce
The status of an order, a shipment or a refund.
SaaS
Current plan, next invoice and account status.
Travel
The status of a booking and of a date change.
Financial services and iGaming
The status of a withdrawal or a deposit, and account status.
Examples of possible lookups. Each connection will be defined and reviewed with the business before it is turned on.
No signed identity, no account data
The business's server will sign a short-lived identity for the signed-in customer. Any failure will leave the customer anonymous: the chat will go on, with the published knowledge only.
Two cases: with a valid signature, the customer will be identified and Ray will be able to use the enabled lookups on that account; with no signature, an expired one or one from another business, the customer will be anonymous and Ray will reply with the knowledge only.
Tools per agent
The Administrator will decide what each agent looks up
Each agent will use only the lookups the Administrator assigns to it, within those the connection enables. An agent with no tools will reply with the knowledge only.
The Administrator only
Assigning or removing tools will take the Administrator role and will stay in the agent's history.Per brand
One brand's agent will be able to look up orders and another brand's, only the knowledge.In view in the Inbox
The team will see which agent handled each conversation and which lookups it made.
Illustrative example of the Lumora Hogar agent's tools: order status and shipment status turned on, refund status turned off, all read-only.
Illustrative example with sample data. Lumora is a fictional brand.
Minimal data and safe failures
Just enough to reply, and a record of each lookup
Ray will ask only for what the reply needs, will say what time the data is from and, if the API fails, will keep helping without making things up.
The minimum needed
Each lookup will return only the fields the reply needs. Names, ID documents and payment details will never get to Ray.
With the time of the data
If a piece of data is incomplete or out of date, Ray will say so or pass the question to a person.
A record of each lookup
Conversation, lookup, result and returned fields, without their values. The record will not be rewritten.
Safe failures
Each lookup will have a time limit. With no answer from the API, Ray will reply with the knowledge or pass to a person with a draft.
Illustrative example of the lookup log: a successful lookup with four fields, an order not found where Ray asked for the right number, and a lookup with no answer that went to a person with a draft.
Illustrative example with sample data. Lumora is a fictional brand.
Status
What is in development and what comes next
The signed identity and the read-only connector are being built and tested locally, with fictional data.
- In development
Signed identity and read-only connector
Tested with a test store and fictional customers, with a record of each lookup and safe failures.
- Coming soon
Connecting a business's real API
After an independent security review and the data protection requirements.
To automate the setup from the terminal or from your own assistant: CLI and MCP.
Review which data to connect with the Ray team
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.