# Luca remembers your leads, so they never repeat themselves.

Luca remembers what every lead told you and what they asked for, carried across channels and searchable. You can edit any of it, and it draws on the knowledge sources you connect.

Last updated: 2026-08-23

- Built from real conversations
- Searchable and editable
- On every plan

## From conversations to a lead who's remembered.

No setup forms: connect a channel and memory builds itself from real conversations. Connect a knowledge source and your facts are covered too.

1. **It reads the conversations** (Luca). As leads talk to you, Luca extracts the durable facts -- the goal, the budget, the hesitation -- into a per-lead memory.
2. **You connect your knowledge** (you). Point Luca at Notion, Google Docs, a website, or an Instagram bio, and approve the field-level suggestions it surfaces.
3. **Memory follows the lead** (Luca). Every channel, every surface -- drafts, follow-ups, Ask Luca, the pre-call brief -- reads the same remembered lead.
4. **You keep it accurate** (you). Search it, correct it, archive what's stale. The record is yours, and it stays yours.

## The difference between a tool and a teammate is memory.

A lead who has to repeat themselves is a lead who feels like a ticket. Luca remembers the goal, the budget, the hesitation -- and references them, so every reply reads like a coach who pays attention.

### Every lead, remembered

Goal, budget, what they've tried, what they flinched at, what they asked for, where they left off. Extracted from the conversations themselves into a per-lead record -- carried across channels, so a lead who moves from Instagram to WhatsApp doesn't start over.

- Extracted from real conversations, not typed up
- Follows the lead across every channel
- Open, search, correct, and archive anytime

### Searchable, not scrollable

A budget mentioned three months and forty threads back shouldn't take a scroll to find. Search a lead's memory straight from the conversation, and the fact surfaces in seconds, with the context it was said in.

- Search the lead's memory from the conversation
- Facts at hand when the moment needs them
- No digging through message history

### Your knowledge, connected once

Point Luca at a Notion page, a Google Doc, a public website, or an Instagram bio. It learns your programs, policies, and offers without you re-typing them, read whenever a draft or answer needs the facts.

- Notion, Google Docs, websites, Instagram bios
- Programs, policies, and offers without retyping
- Read wherever facts are needed

### Suggestions you approve, one tap

Luca reads your content and conversations and notices field-level facts as it goes: a price, a program name, a policy. Approve one with a tap, and it applies everywhere that fact is used.

- Field-level suggestions, not a black box
- One tap to approve a learned fact
- Reuses the same approval everywhere it applies

## Three moments memory changes the reply.

Each one is a place where a tool without memory asks a lead to repeat themselves. A remembered lead feels like a real relationship instead.

### The cross-channel lead

A lead asks about your 1:1 block on Instagram, then messages from WhatsApp a week later.

Luca picks up the thread where it left off: the goal, the price they asked about. It doesn't ask them to start over on a new channel.

### The searchable fact

Before a call you need to remember what a lead said about budget, three months and forty threads ago.

Search the lead's memory and the fact is there: the exact number and the context it was said in. No scrolling a year of messages.

### The connected knowledge source

Your programs and policies live in Notion and change with every cohort.

Connect the page once and approve the field suggestions it produces. Every draft and answer then uses the current facts, with no retyping when a price changes.

## A fresh start every thread vs. a lead who's remembered.

When a lead crosses channels or a thread goes quiet, most tools reset. Here's what resetting costs.

### Starting over

- The lead repeats themselves on every channel. They explained their goal on Instagram, then ask on WhatsApp and get asked all over again -- like the first conversation never happened.
- Context lives in one person's head. The price they flinched at, the program they asked about -- it's in your memory or it's gone, and a busy week erases it.
- Facts you typed once are retyped forever. Every draft has to be reminded of your policies and offers, or the reply quietly gets them wrong.

### A lead who's remembered

- History follows the lead across channels. The Instagram conversation carries into WhatsApp: the goal, the budget, the hesitation -- all there when they message again.
- Context is searchable, not personal. 'What did they say about budget?' is a lookup, not a memory test -- available mid-thread to whoever's drafting.
- Facts connected once, used everywhere. Your Notion page teaches Luca your programs once; every draft and answer from then on has the facts.

## Every memory carries where it came from.

A memory is not a note. Each one is stored with the thing that put it there, and that is what decides whether a draft is allowed to lean on it.

| State | What put it there | Can a draft use it |
| --- | --- | --- |
| Manual | You wrote it, or you corrected one Luca wrote | Yes, and it wins over anything that disagrees with it |
| Trusted pipeline | Pulled from the conversation after a lead qualified | Yes |
| Inferred | Noticed by Ask Luca while you were working | Yes, with lower confidence attached |
| Disputed | You flagged it as wrong, with your reason kept | No. It is filtered out before a draft ever sees it |
| Superseded | A newer fact replaced it, and the link between them is kept | No. The newer one is recalled instead |
| Archived | You put it away without deleting it | No, until you restore it |

Nothing here is pooled with another coach, and nothing trains a model anyone else uses.

## What a memory has to survive before a draft can use it.

Memory is the part of Luca that reads what strangers wrote you and then feeds it back into what you send. That makes the rules around it worth stating.

### What stops a lead from writing your memory?

Two things. Only trusted parts of the pipeline are allowed to write a lead-linked fact at all. On top of that, the text is defused before it is stored, so a lead who types something shaped like an instruction leaves a fact behind rather than an order.

### What happens when a fact changes?

The old one is not overwritten. A lead who says May and later says August ends with two memories and a link between them, the newer one recalled and the older one kept. Writes for the same lead are serialized, so two extractions cannot both win.

### Why is this a search rather than a vector lookup?

Because memories are short facts, not documents. A budget, a start date, a thing they already tried. Ranked text search finds those reliably, and it means nothing has to be embedded on every write, so a fact is recallable the moment it is stored.

### Where does memory actually get used?

In three places. A draft can pull a lead's facts mid-sentence rather than guessing. Ask Luca reads and writes it while you work. And a follow-up weeks later can name the thing that lead actually said, which is the difference between a nudge and a nag.

## The details, for people who want them.

What's remembered, where it lives, and who controls it.

- **What it stores.** Durable facts extracted from conversations: goals, budgets, hesitations, requests, and where a lead left off.
- **Objections remembered.** The qualifier extracts each objection it hears into a structured record on that lead, so a later reply or brief can reference it.
- **Objection playbook.** Six buckets: price, timing, trust, fit, authority, smokescreen. Your own handling strategy per bucket, plus CSV import of past objections once a day.
- **Across channels.** One lead stays one lead across Telegram, Instagram, Messenger, and WhatsApp, with history carried over.
- **Search.** Per-lead memory is searchable from the conversation -- a lookup, not a scroll.
- **Control.** Correct, delete, and archive memories. What you change is what Luca uses from then on.
- **Knowledge sources.** Notion, Google Docs, public websites, and Instagram bios -- connected once, read whenever facts are needed.
- **Suggestions.** Field-level facts Luca noticed, approved with one tap and reused everywhere they apply.
- **Privacy.** Scoped to your account. Nothing is pooled with other coaches or used to train a shared model.
- **Plans.** Lead memory and knowledge sources: included on every plan.

## Questions

### Can I edit or delete what it remembers?

Yes. Correct a fact that's wrong, delete one that's stale, or archive what you no longer need. What you change is what Luca uses from then on.

### What if it remembers something wrong and I haven't caught it yet?

Flag it as disputed with your reason, and it's filtered out before any draft can use it. A wrong fact doesn't keep steering replies while it's in dispute.

### Is my data pooled with other coaches, or used to train a shared model?

No. Every lead's memory and every knowledge source is scoped to your account. Nothing is pooled, and nothing trains a model anyone else uses.

### I connect a knowledge source once. Do I have to keep it updated?

Just the source itself. Luca reads a Notion page, Google Doc, website, or Instagram bio whenever a draft needs the facts, so update the source and the next draft uses the new version. Nothing needs re-typing on your end.

### How does memory actually change what a lead sees?

A draft that references the 1:1 block a lead asked about in March reads like a coach paying attention. Memory stops Luca from asking the same qualifying question twice, and lets a follow-up reference something real instead of a generic nudge.

### Which plans include it?

Included on every plan. What changes between plans is how many messages a month you get, plus what Starter leaves out: Voice tuned weekly from your newest DMs and Follow-ups that win back ghosted leads. All four channels are on every plan.

## Try it

Your leads, remembered from day one. Connect a channel and Luca starts building each lead's memory from the conversations themselves. Connect a knowledge source and it knows your offers too.

[Start free for 7 days](https://app.setluca.com/signup). Plans and prices are on the [pricing page](/pricing.md). SetLuca is the company behind Luca.

## Other features

- [Your voice](/features/voice.md): Replies that sound like you, learned from your DMs
- [Review queue](/features/review-queue.md): You approve every send. Auto-send is opt-in
- [Follow-ups](/features/follow-ups.md): Win back the leads who ghost
- [Booking](/features/booking.md): From DM to booked call on your calendar
- [Channels](/features/channels.md): Telegram, Instagram, Messenger, WhatsApp in one queue
- [Comment-to-DM](/features/comment-to-dm.md): Turn post comments into qualified DM conversations
- [Automations](/features/automations.md): Build the follow-up flow once, then let it run
- [Broadcasts](/features/broadcasts.md): One campaign to every lead who's a fit
- [Ask Luca](/features/ask-luca.md): Your business questions, answered from your own data
- [Analytics](/features/analytics.md): Know what's working before your gut does
- [Integrations](/features/integrations.md): Your CRM stays current, synced both ways
- [Inbound](/features/inbound.md): Every channel, one prioritized queue