TenkaTenka
Sign in

Tenka Help Center › Platform and security › Tenkai no site

Tenkai no site

O chat de atendimento do seu site, respondido pelo Tenkai com o seu catálogo e a sua base de conhecimento, que abre lead no CRM quando o visitante quer falar com alguém.

🕒 Updated on Sep 19, 2026📖 ~3 min read

What you find on this screen

A portrait of the screen, read from the screen itself — it changes when the screen changes.

Form fields

Identificação*Como você chama este widget ("Site institucional", "Landing da campanha"). Só aparece aqui.
Nome do assistenteO nome que o visitante vê no cabeçalho do chat. Vazio, aparece "Tenkai".
SaudaçãoA primeira mensagem, antes de o visitante escrever. Diga o que o assistente sabe responder.
Domínios permitidosUm por linha ou separados por vírgula (ex.: minhaempresa.com.br). Só páginas desses domínios conseguem usar o widget. Vazio = qualquer site com o tok…
CorCor do botão e do cabeçalho, em hexadecimal (#2B2F6E). Vazia, usa a cor padrão da plataforma.
Idiomapt-BR, en ou es. Vazio, usa o idioma da empresa. Define o idioma dos textos fixos do chat e das respostas.
Pedir contato e abrir leadLigado, o Tenkai convida o visitante a deixar nome, e-mail e telefone e abre o lead no CRM com a conversa. Desligado, só responde.
AtivoDesligado, o widget some do site — sem erro para o visitante. Para desligar TODOS de uma vez, use a porta "Tenkai no site" na Central de Confiança.

Start here

Uma linha no site, e o Tenkai atende
Create the widget, copy the snippet (the line that starts with

Rules

O que o Tenkai do site NÃO faz
It sees nothing of the operation: no customers, no contracts, no finance, no other leads. The scope is closed on purpose — the visitor is a stranger, and the answer that goes to them can never carry any data from your account that isn't public. That's the difference between the site's Tenkai and the Tenkai you use when logged in.
Como o lead nasce
When the visitor wants to talk to someone (or after a few messages, if "Ask for contact" is on), the chat asks for name, email, phone and company. With that, Tenkai opens a lead with source SITE, attaches the whole transcript as an activity and puts the lead in the inbound cadence — the salesperson receives it with the conversation already read. If the email or phone already belongs to a lead, the new one isn't duplicated: the conversation goes to the existing one.
A cota do plano conta CONVERSAS, por mês
Each visitor session is one conversation. The month's scoreboard appears in the widget's record, with your plan's quota, and warns when it passes 80%. Beyond the quota, by default the chat keeps answering and the excess goes on the following month's invoice, like the other usage meters. If your company prefers a hard ceiling, turn on the parameter "Tenkai on the site: lock when quota is exceeded" — then Tenkai stops answering new visitors until the month turns, but the contact form keeps working and the lead is still created.
O token é a senha do widget
Whoever has the snippet can use your chat on any site — and spend your quota. That's why "Allowed domains" exist: fill it in with your domain and the widget only works there. If the token leaks, click "Generate new token" and save: the old snippet dies immediately, and you paste the new one.
Assumir a conversa: uma pessoa entra no lugar do Tenkai
In the Conversations tab, "Take over" passes the conversation to you: Tenkai stops answering that visitor, whatever they write arrives as a notification and you reply right there, with the full transcript in view — the visitor sees "an agent joined the conversation" and stays in the same window. "Return to Tenkai" releases it. A taken-over conversation doesn't count again toward the quota (it's the same conversation). Use it when the visitor asks for someone, or when the question is about prices and deadlines Tenkai doesn't know.

Frequently asked questions

O widget não aparece no site. O que conferir?
In order: (1) the widget is Active; (2) the "Tenkai on the site" door is turned on in the Trust Center; (3) the site's domain is on the allowed domains list (or the list is empty); (4) the snippet is on the page, with the right token. In all four cases the widget simply doesn't appear — with no error on the visitor's screen — because a broken chat on a public site is worse than none.
Was this article helpful?

In the same module: Platform and security38

Tenka Academy

Step-by-step learning paths for your industry, inside the platform.

Explore the Academy