LeadBind Docs

Mani

The assistant inside LeadBind. One conversation, whether you use the panel or the full page.

Mani is the assistant inside LeadBind. It can see your account, so it answers about your actual leads and calls rather than about the product in general.

Two places, one conversation

Mani lives in two surfaces and they are the same conversation.

The panel. Open it from any screen in the app when you have a quick question and do not want to lose the page you are on.

The full page. Open Mani from the nav for a working session: the conversation takes the whole window, with your earlier chats in a rail down the side.

A message sent in one appears in the other. Start something in the panel, open the page, and you are in the same thread where you left it. While the full page is open the panel stays out of the way, because a floating panel over a full-page chat is the same conversation twice.

What to ask it

Anything you would otherwise build a filter for:

  • "Summarize my pipeline today."
  • "Which leads went cold this week?"
  • "Review my last ten calls and tell me what I keep getting wrong."
  • "Draft a follow-up to the hot ones waiting on me."

It is better than a filter for questions with a judgement in them. "Who should I call first" is not a query, and it is exactly the sort of thing Mani is for.

When it wants to do something

Some answers end with a card rather than a paragraph: schedule a follow-up, open the dialer on a lead or a list, take you to a page. Nothing happens until you confirm the card.

The same rule holds underneath, where you cannot see it. Anything that reaches a customer or destroys something is confirmed with you first, and that is enforced on the server, not left to the model's manners. Sending a text or an email, booking an appointment, enrolling leads in follow-up, changing your front desk, deleting leads: each of those refuses to run until you have seen exactly what it is about to do and said yes.

Reading your account, drafting a message, and organizing a list are not gated, because none of them reach anybody.

When several are waiting. You decide them in one place, Ideas: each action waiting on you shows who it goes to and the exact words, with the same three answers, Approve, Not now, and Decline. The top one that can be approved has the blue Approve button; the rest have a white one that does exactly the same thing. Answer the top one and the blue moves to the next, so your eye always lands on the next decision. Older drafts of the same kind for the same person fold under the newest one ("1 older draft for the same person"), and nothing is deleted or declined for you. Your Inbox lists each one as a row that opens it in Ideas, Today says how many are waiting at the top of the page, and the Mani page says the same in one line.

What Mani does on her own

Overnight. On the Service plan, with notifications on, Mani works your book once a night, between 2 and 6 in the morning on your account's clock: notes, owed follow-ups, and anything that would reach a customer parked for your approval. The Logbook shows one entry per night: the first pass of each day, even if a pass ran more than once.

Waiting on you. The Tasks tab lists each approval by what it would do (for example, the exact text it would send), so two runs of the same routine never look like the same row.

Settings, then Mani holds three rows, the same three as the iPhone app: Routines (work Mani repeats on a schedule or when a lead arrives), Autopilot (what she may do without asking first) and What Mani knows (the facts she remembers about your business, which you can edit). On the web each opens its tab on the Mani page.

Mani is not AI Access

Two different things with a similar shape, and it is worth being clear which one you want.

Mani is our assistant, inside LeadBind, already connected to your account. Nothing to set up.

AI Access is the opposite direction: connecting your assistant, Claude or ChatGPT or anything else that speaks MCP, so it can reach LeadBind from wherever you already work. That needs a key, and you choose what it may do. See Keys and permissions.

Use Mani when you are in the app. Use AI Access when you are not.

When a text cannot be sent yet. A text Mani drafted says what approving would really do. While texting is paused across LeadBind, or your account has no number to text from, or its texting registration has not cleared, the card keeps the draft, shows Approve greyed out with the reason beside it, and still offers Not now and Decline. Nothing is sent, and Approve opens on its own once the reason is gone.

The morning plan. Plan my day drafts up to three texts. While texts from an earlier plan are still waiting for you, it drafts no new ones and says so in the plan, so one person never has two near-identical texts waiting.

Was this page helpful?