Home

Home is the first page after signing in (the address is still /dashboard, so every bookmark and email link keeps working). It answers three questions in this order: does anything need me, are my AI employees working, and how did this week go. Everything on it is read from data Blengi already stores; nothing new is tracked.

Needs your attention

A list of what needs a person, most urgent first. Each line says what happened, since when, and has one button that opens the page where you fix it. A line disappears only when the thing it reports is gone (the visitor was helped, the source was read, the lead was followed up), never because you clicked it. Five lines show at once; the rest sit behind Show all. When the list is empty it says Nothing needs you right now, with the time it was checked.

Line	When it appears	Button opens
A visitor is waiting for you	A visitor asked for a person and nobody has taken the chat yet.	That chat (or the waiting list when there are several)
A visitor asked for a person and got no answer	Nobody took the chat within five minutes, so the visitor was asked to leave their email. Last 7 days.	That chat (the Conversations list when there are several)
Visitors cannot see name	The AI employee is published but no website is allowed to show it.	Website › Websites where it may appear
name is not published	It has read pages but was switched off. (One that has not read a page yet is in the setup checklist instead.)	The overview
A payment failed / New conversations are paused / Your trial ends in N days	Only shown to the workspace owner. Paused means the plan's monthly conversation limit was reached: new visitors are turned away until next month or an upgrade. A trial is announced from three days before it ends. After it ends, until a plan is chosen, the pages under /app and Settings › Team, Integrations and the Human takeover pages send the owner to Plan and billing and everyone else to Home. Home, Plan and billing and the other Settings pages stay open.	Plan and billing
N sources could not be read	Knowledge sources in the failed state.	The sources of the AI employee with the most failures
Your team is still in N chats	A person took a chat over more than a day ago and nothing has happened since. The AI employee stays silent in a taken-over chat until someone hands it back.	Conversations, live now
N new leads	Leads whose status is still New.	Leads, filtered on New
N questions it could not answer	Open unanswered questions, however long ago they were asked.	Results › Unanswered questions, which lists all open questions by default (the same number), each with a prefilled fixed answer
Visitors rated N answers down	Thumbs-down feedback in the last 7 days.	Knowledge › Visitor feedback of the AI employee with the latest thumbs-down

An AI employee that is Ready (published and allowed, but not seen on your website yet) is not a line in this list: its card below says Install it.

A line whose fix needs rights your role does not have shows without its button: a viewer still reads Visitors cannot see …, to pass it on, but gets no Fix this that would end on a page they cannot open.

Your AI employees

One card per AI employee, the ones visitors cannot reach first, with its checked status (Online, Ready, Blocked, Draft; see AI employees), how many sources it has read and how many could not be read. Test it opens the overview with the real widget already open in the corner; the conversation counts as a test, never as a visitor. The second button is the next thing to do: Add your website when it is blocked, Install it when it is ready, Continue setup for a draft that has not read a page, otherwise Open. People with the viewer role see only Open.

Finish setting up

While an AI employee is not fully set up, Home shows its checklist: Add your website (a source has been read), Try it yourself (you had a test chat) and Put it on your website (the chat has been seen on your website, not merely published). It is the same checklist, with the same rules, as on the AI employee's overview. The menu's Getting Started entry shows while the workspace has no AI employee yet or one of your AI employees has a step open, and disappears when all are done. People with the viewer role see the checklist without its Continue button: every step is a change they cannot make.

This week

Four numbers for the last 7 days — today and the six days before it, from midnight, the same stretch Results calls Last 7 days — each compared with the equally long stretch just before: Conversations (a session in which the visitor wrote at least one message; opening a page with the chat on it is not a conversation), New leads (left by visitors; a lead sent from a test chat is not counted), Could not answer (the open questions visitors asked in those days) and Visitors who saw the chat (widget sessions: one per visitor per day, however many pages they open). Test chats never count.

Each number opens the list behind it for the same 7 days: Conversations, Leads and Results with Last 7 days, Unanswered questions with Last 7 days. (Leads also lists test leads from your own preview chats, with a Test label; the tile leaves them out.) Below them are the five latest conversations with the visitor's first question, and the five newest leads.

First visit

A workspace without an AI employee sees one thing: Let us build your AI employee and a website field. Entering the address opens the setup wizard, which starts reading the site straight away and ends in a live chat with the new AI employee. The wizard is also what New AI employee on the AI employees page opens; see Quickstart.

Where the old Dashboard's figures went

• Conversations, messages, leads, conversion and engagement, the chart and the per-AI-employee table, for the last 7, 30 or 90 days: Results (/app/results).
• The lead pipeline (how many leads are New, Qualified, Contacted, Won, Lost) and the lead filters: Leads (/app/leads), as a strip above the list; each count filters the list.
• Source health: the AI employee cards above and each AI employee's Knowledge sources page.