DigiBot

Connect your business data and ask questions in plain English.

DigiBot

Home

AI Assistant

Lead Assistant

Setup

Home

AI Assistant

Your team, asking about your own data.

Lead Assistant

Leads on WhatsApp, from first message to handover.

1. Create a read-only database user

There is no such thing as a read-only connection URI — a URI is only credentials. Read-only is a property of the database user, so run this once against your database, then paste a URI that uses the new role.

Loading…

2. Connect

Connections

Schema

Descriptions are sent to the model with every question, so correcting a wrong one here directly improves the SQL it writes. Click any description to edit it.

Knowledge

Company documents — policies, procedures, handbooks. Business data stays in your database; this is for the questions a database cannot answer.

Source Documents

Documents

File Source Status Chunks

Agents

An agent’s instructions are versioned: publishing a change creates a new version, so past answers stay tied to the exact configuration that produced them.

Name Talks to Knowledge Answers Version

Inbox

Conversations the agent has stepped out of. Oldest first — a queue is worked from the end that has been waiting longest.

Conversations

Every conversation an agent has had — your team’s in the chat window, and leads’ over WhatsApp. Opening one shows the transcript and what the agent did to produce each answer.

With Channel Handling Messages Started

Transcript

Leads

People outside your organization that an agent has spoken to. Open means WhatsApp still allows a free-form reply; after 24 hours of silence only an approved template may be sent.

Name Phone Lead type Source Reply window Added

Lead types

One agent, many briefs. Your CRM sends lead_type with each lead; the first matching brief below decides how that lead is greeted, what the agent is told, and which documents it may use. The default answers anything nothing else claims.

Lead type Matches Answered by Opener Conversations

Settings

Who can sign in, what your systems connect with, and where your agents send messages from.

People

You cannot change your own role, and you cannot grant a role carrying more than you hold.

Email Role Status

API keys

For your website or CRM to post leads to POST /v1/events/. A key can only submit events — it cannot read your data.

Name Key Last used

WhatsApp

The number your leads message, and the one your agent answers from. Nothing in Lead Assistant sends or receives until a number here is connected and Meta is delivering to it.

Callback URL:

Webhook below says who subscribed the number, not whether Meta is delivering — we cannot see that from here. Give us the Business Account ID and we do it for you; without one you set the callback URL and verify token in Meta yourself, which works just as well.

Number Phone number ID Status Webhook

New agent

Instructions are versioned. Saving publishes a new version.

Knowledge it may search

Channels it answers

When to fetch a person

A whole word matches a whole word: “help” will not fire on “helpful”. Put a phrase in to match it anywhere.

How it opens with a new lead

New lead type

What your CRM calls this kind of lead, and how it should be handled.

Who answers it

Leave on the routed agent unless this kind of lead needs different tools or a different database. Most organizations only ever need one.

Documents for this lead type

None selected means whatever the agent already uses. Choosing some narrows it to those — a lead type can never reach a document the agent itself may not read.

How it greets a new lead

A reply that lands the instant someone presses Submit reads as a machine. A couple of minutes reads as a person already at their desk.

When to fetch a person

New knowledge source

A grouping for related documents.

Upload a document

The worker parses, chunks and embeds it in the background.

Add a person

They sign in with this email and the password you set.

Create an API key

Shown once. Only its digest is stored.

Connect WhatsApp

Take these from Meta’s console. Stored encrypted, never shown again.

No verify token to invent — one is generated here and the webhook is subscribed with Meta on your behalf.