@leadbay/mcp 0.40.0 → 0.41.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/CHANGELOG.md +36 -0
- package/dist/bin.js +499 -18
- package/dist/http-server.js +487 -16
- package/dist/installer-electron.js +1 -1
- package/dist/installer-gui.js +1 -1
- package/package.json +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -1,5 +1,41 @@
|
|
|
1
1
|
# Changelog — @leadbay/mcp
|
|
2
2
|
|
|
3
|
+
## 0.41.0 — 2026-09-25 — boards a rep can work from: a lead desk, a route planner, and buttons that answer
|
|
4
|
+
|
|
5
|
+
- **Every Leadbay board is built from the same kit.** Asking for a triage board,
|
|
6
|
+
a call board or a coverage board now always produces one built on Leadbay's
|
|
7
|
+
own components, in the product's colours and on a light page — not a page the
|
|
8
|
+
assistant styles from scratch. Every lead card carries a **Qualify /
|
|
9
|
+
Requalify** button.
|
|
10
|
+
- **A lead desk for working a list.** After a follow-up list or a campaign call
|
|
11
|
+
sheet, the assistant offers a *Contact and outreach* board: each lead's phone,
|
|
12
|
+
email and LinkedIn in one row, with the company context, and an **Enrich**
|
|
13
|
+
button on the contacts that have no way to reach them yet.
|
|
14
|
+
- **A route planner for a day on the road.** "I'm driving to Lyon on Thursday"
|
|
15
|
+
now offers a board that is half map, half panel: click a pin to open the lead,
|
|
16
|
+
set its status, record how the visit went, and see the pin change as you work.
|
|
17
|
+
Leads with no address are listed beside the map instead of disappearing. The
|
|
18
|
+
map opens on France, and **Fit to leads** frames yours.
|
|
19
|
+
- **Two new guided sessions.** *Outreach session* runs a working session over
|
|
20
|
+
any list — follow-ups, a lens or a campaign — and checks first whether the
|
|
21
|
+
leads can actually be reached. *Route session* plans the trip. Both record
|
|
22
|
+
each outcome as you tell it.
|
|
23
|
+
- **Coverage over more than sectors.** The coverage board can measure the
|
|
24
|
+
portfolio by any dimension, and a new reachability view shows how many leads
|
|
25
|
+
have a phone, an email, both, or neither.
|
|
26
|
+
- **Prospecting actions work the way they do in the web app.** On a board you
|
|
27
|
+
can tick and untick *Still chasing*, *Meeting planned*, *Could not reach* and
|
|
28
|
+
*Not interested*, several at once, in the web app's colours. What is ticked
|
|
29
|
+
is what you ticked today, and unticking one takes it off without leaving a
|
|
30
|
+
note behind.
|
|
31
|
+
- **A board's buttons answer in a second, not a minute.** Logging outreach or
|
|
32
|
+
setting a prospecting action from a board used to wait 60 seconds and then
|
|
33
|
+
report that Leadbay "took too long" — even though the change had been saved.
|
|
34
|
+
Following that advice logged the same visit twice. Boards now save a note
|
|
35
|
+
and a prospecting action the way the web app does, so they confirm straight
|
|
36
|
+
away. Outreach logged by the assistant itself still asks you to confirm it,
|
|
37
|
+
as before.
|
|
38
|
+
|
|
3
39
|
## 0.40.0 — 2026-09-22 — every tool says plainly what it does and what it changes
|
|
4
40
|
|
|
5
41
|
- **Each tool now says what it does before it says when to use it.** A tool's
|