Stories A promise's telling · terms re-made 2026-11-18 on Tony's words; 19 features. Read 2026-11-22 against one-ie main 910269b3a7; production is the 2026-11-21 01:58 UTC deploy (release 16 shipping): 9 live, 2 built (the client site, not on a client domain; the Follow-Up Engine, fixed in production, no reply sent yet), 8 partial, 0 missing. Text messages left Capture on 2026-11-21 and are sold in Close. OO's North Star v1 is answered in full (clients/oo/docs/one-answers-2026-11-22.md + -part2.md). Ads safety guards are on main, not live; the rest of the ads loop is in build (one-ie text/vespio-ads-build.md, rows A–J). Dominate re-read 2026-11-22 against North Star v1 section 6 and 14.3: custom integrations are one webhook in and one answer back (Tony 2026-11-22), AI search is measured on OO's rung scale, lanes in one-ie text/vespio-dominate.md. Signup, provisioning on payment and the welcome page are live on app.vespio.ai (text/vespio-connect.md); card payments wait on Stripe Connect; proof red
Vespio
A Vespio client's stranger is answered by the front desk, lands in the client's CRM as a lead, is booked, and shows up in that month's report, with no person in the loop.
The seven beats
- Groups
- A local business loses the lead that rings after six, the form nobody answers until Monday, the text that waits three days.
- Actors
- Donal, who runs Vespio; his clients, each a workspace under vespio; the front desk agent each client gets; ONE, the substrate under all of it.
- Events
- A client pays for ads and still loses half the leads they bring, because nobody answers in the first five minutes.
- Things
- Every lead answered, captured, booked and followed up, on every channel, and the client can see it in a report.
- Paths
- Three tiers on paths ONE already runs: the front desk captures, the follow-up engine closes, the ads and AI search bring more.
- Outcome
- The first client whose stranger is answered, booked and counted in the month's report with no person in the loop.
- Learning
- Open.
This story carries its beats but no written telling yet — text/vespio.md has no “The story” section.
Connected to
Every link here was checked against the repo when the page was built. 4 names the story uses could not be found and are shown without a link.
People
- Donal — runs Vespio and sells the tiers
- a client — a local business owner
- the client's stranger — the lead
Agents
Each opens a chat with that agent.
- the front desk agent, one per client
- ads-meta, ads-google
- tracking-engineer
- strategist
Skills
Each opens the skill's page.
- vespio
Paths
The flows this story walks — trigger → step → step.
- receiver:lead:capture → visitor:identify → entity:tag → message:send → booking link
- schedule:cron → analytics:run → message:send
Tools
Receivers and scripts it signals.
Docs
What derives from this file.
Events
Every event is a signal; each names the path it marks or warns.
- lead:capture · from the client's lead form or front desk the lead-follow-up path (workflow-templates.ts:502) tags: vespio, lead
Transactions
- each client pays Vespio monthly at the tier price above; VERIFY: which rail bills the client is not read here
Analytics
- leads by stage per client
- minutes from lead to first touch
- report delivered per cadence