Leads
What a lead record is in OMAI, what the Leads screen shows, and how to work the list. Nothing in the product creates a lead record today, so the screen stays empty on a live account.
- Who
- Anyone with dashboard access
- Plan
- All plans
- Role
- Any role can view. Agent, Admin or Owner can change a lead status
Before you start
- A signed-in dashboard account
The Leads screen sits under Leads in the dashboard menu. It is a single table of lead records for your organization, with a status filter and a control for changing the status of one row. There is no lead detail page, and no way to create, edit or delete a lead from the product.
What a lead is
A lead is a stored record that points at one of your contacts and carries a pipeline status. It is a separate record from the contact and from the conversation — changing it does not change either of them, and the customer never sees it.
- The contact it belongs to — the customer name if one is known, otherwise the phone number.
- An optional link to the conversation the lead relates to.
- A status, one of five pipeline values.
- A score — a whole number stored on the record.
- Any number of detail fields, each a key and a value, shown as chips in the Details column.
How a lead comes to exist
It does not, today. No screen in the dashboard creates a lead, the assistant does not create one when it answers a customer, and there is no upload or API for adding one. The only lead rows that exist anywhere are the two that ship in the demo database used for screenshots and testing. The screen’s own empty-state wording suggests leads will arrive from conversations on their own; they do not.
Until that changes, the practical way to track an enquiry is inside the conversation itself: add a tag such as quote-sent, and write what you promised the customer in an internal note. Both are covered in Tags, filters and search and in Reading a conversation.
The Leads table
| Column | What it shows |
|---|---|
| Contact | The contact name, or the phone number when no name is stored. The phone number is repeated underneath, always left to right. When the lead is linked to a conversation, an Open conversation → link appears here. |
| Details | One chip per detail field, in the form key: value, sorted by key. When the record has none, the column reads No additional details. |
| Score | The number stored on the record. Nothing in the product sets it, so it reads 0. The table is sorted by this column, highest first. |
| Status | The current pipeline status, as a badge. |
| Update status | A dropdown that saves as soon as you pick a value. This is the only thing on the screen you can change. |
Lead statuses
| Status | What it is for |
|---|---|
| New | The default a lead record starts on. |
| Qualified | You decided this enquiry is worth pursuing. |
| Unqualified | You decided it is not a fit. |
| Converted | The enquiry turned into business. |
| Lost | The enquiry ended without business. |
These are labels you set by hand. Nothing in the product behaves differently because of them: the assistant does not read the status, no message is sent, no reminder is scheduled, and the conversation is untouched.
Working the list
Step 1 Open Leads from the dashboard menu.
You should see: The full list loads, sorted by score and then by newest first.
Step 2 Choose a status chip — All, or one of the five statuses — to narrow the list.
- When a filter returns nothing, the screen says no leads were found with the selected status and suggests another one.
You should see: The address bar gains a
?status=value, so you can bookmark a filtered view or share it with a colleague who has dashboard access.Step 3 Pick a new value in the Update status dropdown on the row you want to change.
- If nothing saves and an error appears, your role is below Agent. Ask an owner or admin to change it for you.
You should see: The row saves immediately — there is no separate save button and no confirmation dialog. The change is written to the audit log with the old and the new status.
Who can do what
| Action | Lowest role that can do it |
|---|---|
| Open the Leads screen and read every row | Viewer |
| Change a lead status | Agent |
| See the audit entry a status change produces | Admin |
The screen does not hide the dropdown from roles that cannot use it, so a viewer sees the control and gets an error on use. Roles are explained in Roles and permissions.
Limits
- Up to 200 lead records load per view. There is no pagination and no "load more".
- Sorting is fixed: score descending, then newest first. The column headers are not sortable.
- There is no search box on this screen — the status chips are the only filter.
- Leads are not gated by plan. Every plan can open the screen.
What goes wrong
Can I add a lead by hand?
No. The screen has no create control, there is no import, and no other screen creates one.
Does the assistant mark a customer as a lead?
No. The assistant answers, hands over to a person, and writes messages into the conversation. It does not create or update lead records.
What exactly happens when I change a status?
The record is updated and an entry is written to the audit log naming you, the lead, the old status and the new one. The customer is not notified and the conversation does not change.
Can I get my leads out of OMAI?
Lead records and their detail fields are included in the account-level JSON export, described in Getting your data out. There is no leads-only export and no CSV.
Why does the score always show 0?
Because nothing in the product writes a score. The column exists on the record and the table sorts by it, but the value never moves off its default.