Skip to content
Early access: Ray will answer from the knowledge each business publishes. Request access
Ray
Sign inTalk to salesSee demoBook a demo

CompanyIn development

Convray builds Ray, customer service that resolves

Ray is the product and the agent; Convray is the company that builds it. The goal is simple to state: every question resolved in the same conversation, with sources the team can review.

Request accessTalk to the team

Early access with hands-on help from the team. Ray is in development.

Mission

The customer gets the answer, and the team knows where it came from

Convray starts from one conviction: an automated chat is only worth it if it resolves. That takes grounding in each business’s knowledge, explicit limits and a team that can review every reply.

The customer will get a clear, written reply with no internal references. The team will see the source, the version and the checks behind each one.

Product
Ray, an AI customer support agent, with a console for the team and a widget for the site.
Stage
In development, with early access and guidance from the team.
Languages
Latin American Spanish, English and Brazilian Portuguese, from the ground up.

PrinciplesIn development

Five rules for building Ray

They will hold for every conversation and every business, with no configuration exceptions.

  1. No source, no answer

    Ray will answer only from published, current articles or from account data. The customer will get a clear answer, and the team will be able to audit the source of each one in the console.

  2. Only sensitive topics go to a person

    An explicit list: personal data, legal complaints, disputed payments, account closure and the topics each business adds. Outside it, Ray will try to resolve.

  3. Read-only

    Ray won’t move money, issue refunds or change accounts. People will keep doing that, in the business’s own systems.

  4. No change without tests

    Knowledge, instructions or model: every change will go through the test cases. If results get worse beyond the tolerance, it will be held.

  5. The customer will see the answer; the team, the source

    Ray will not send article cards or links to read. The source will stay in the console, in view of whoever is helping.

How it is builtIn development

Tested, read-only and auditable

Four engineering practices behind the rules above.

  • Tested before publishing

    Every change to knowledge, instructions or the model will go through the test cases, with a sensitive-topics floor that cannot be turned off. If something gets worse beyond the tolerance, the change will be put on hold.

  • Read-only

    Ray’s tools will be able to look things up, not act: no money, no refunds, no account changes.

  • Auditable

    Every reply will be recorded with its source and version, and every configuration change in an audit log.

  • Isolated per business

    Each business’s data will be isolated in the database and can be exported in a documented format.

Ray is in development. The practices describe the product being built; early access will be arranged with the team.

Team

The people behind Ray

Profiles will be published with each person’s approval. Until then, this section illustrates the format.

  • [Name][Role][City, country]
  • [Name][Role][City, country]
  • [Name][Role][City, country]
  • [Name][Role][City, country]

Company facts

Convray at a glance

Company
Convray
Product
Ray
Legal entity
[Legal entity to be confirmed]
Address
[Address to be confirmed]
Year founded
[year]
People on the team
[number]
General contact
[Contact email to be confirmed]
Press
[Press email to be confirmed]

Details in brackets will be filled in once they are set.

Meet the team that builds Ray

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.

Request accessTalk to sales