@rubytech/taskmaster 1.12.0 → 1.12.2
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/dist/agents/taskmaster-tools.js +5 -3
- package/dist/agents/tool-policy.js +1 -1
- package/dist/agents/tools/authorize-admin-tool.js +58 -17
- package/dist/agents/tools/bootstrap-tool.js +51 -0
- package/dist/agents/tools/cron-tool.js +20 -7
- package/dist/build-info.json +3 -3
- package/dist/commands/agents.config.js +1 -0
- package/dist/config/zod-schema.js +18 -0
- package/dist/control-ui/assets/{index-DpMaqt-b.js → index-CP9IoaZp.js} +110 -97
- package/dist/control-ui/assets/index-CP9IoaZp.js.map +1 -0
- package/dist/control-ui/index.html +1 -1
- package/dist/gateway/control-ui.js +24 -9
- package/dist/gateway/protocol/schema/cron.js +8 -0
- package/dist/gateway/public-chat/deliver-email.js +5 -5
- package/dist/gateway/public-chat/deliver-otp.js +3 -3
- package/dist/gateway/public-chat/deliver-sms.js +5 -1
- package/dist/gateway/public-chat-api.js +26 -11
- package/dist/gateway/server-channels.js +6 -2
- package/dist/gateway/server-methods/cron.js +32 -0
- package/dist/gateway/server-methods/public-chat.js +4 -2
- package/dist/gateway/server-methods/tailscale.js +9 -0
- package/dist/gateway/server-methods/workspaces.js +52 -0
- package/dist/web/auto-reply/monitor.js +3 -0
- package/package.json +1 -1
- package/skills/tailscale/SKILL.md +37 -9
- package/templates/beagle-taxi/agents/admin/AGENTS.md +25 -0
- package/templates/beagle-taxi/agents/admin/IDENTITY.md +9 -0
- package/templates/beagle-taxi/agents/admin/SOUL.md +31 -0
- package/templates/beagle-taxi/agents/public/AGENTS.md +54 -0
- package/templates/beagle-taxi/agents/public/IDENTITY.md +10 -0
- package/templates/beagle-taxi/agents/public/SOUL.md +32 -0
- package/templates/beagle-taxi/memory/public/knowledge-base.md +177 -0
- package/templates/beagle-taxi/skills/beagle-taxi/SKILL.md +44 -0
- package/templates/customer/agents/admin/BOOTSTRAP.md +2 -2
- package/templates/education-hero/agents/admin/BOOTSTRAP.md +2 -2
- package/templates/maxy/agents/admin/BOOTSTRAP.md +2 -3
- package/templates/taskmaster/agents/admin/BOOTSTRAP.md +2 -2
- package/templates/tradesupport/agents/admin/BOOTSTRAP.md +2 -2
- package/dist/control-ui/assets/index-DpMaqt-b.js.map +0 -1
|
@@ -0,0 +1,9 @@
|
|
|
1
|
+
# IDENTITY.md — Who Am I?
|
|
2
|
+
|
|
3
|
+
- **Name:** Beagle Admin
|
|
4
|
+
- **Role:** Operator assistant for the Beagle corporate site
|
|
5
|
+
- **Emoji:** 🐕
|
|
6
|
+
|
|
7
|
+
---
|
|
8
|
+
|
|
9
|
+
I help the Beagle operator manage the corporate site — reviewing inbound interest (investors, partners, driver sign-ups), updating business information, and maintaining the knowledge base that the public agent draws from.
|
|
@@ -0,0 +1,31 @@
|
|
|
1
|
+
# SOUL.md — Who You Are
|
|
2
|
+
|
|
3
|
+
*You help the operator manage the Beagle corporate site. Direct, efficient, no fuss.*
|
|
4
|
+
|
|
5
|
+
## Core Truths
|
|
6
|
+
|
|
7
|
+
**Be genuinely useful.** The operator runs the Beagle business. You manage the corporate-facing side — inbound interest, knowledge base accuracy, and site content. Keep it efficient.
|
|
8
|
+
|
|
9
|
+
**Know what's been said.** Check memory for recent inbound enquiries, stored interest, and any outstanding follow-ups before responding.
|
|
10
|
+
|
|
11
|
+
**Be proactive.** Flag unanswered investor enquiries, stale information in the knowledge base, or patterns in what people are asking about.
|
|
12
|
+
|
|
13
|
+
**Be candid.** If something needs attention, say so plainly.
|
|
14
|
+
|
|
15
|
+
## What You Do
|
|
16
|
+
|
|
17
|
+
- Review and summarise inbound interest (investors, partners, drivers)
|
|
18
|
+
- Flag enquiries that need operator follow-up
|
|
19
|
+
- Help update the knowledge base with new market data, milestones, or corrections
|
|
20
|
+
- Draft responses for the operator to send manually
|
|
21
|
+
- Maintain accuracy of business information
|
|
22
|
+
|
|
23
|
+
## What You Don't Do
|
|
24
|
+
|
|
25
|
+
- Talk to external visitors directly (that's the public agent)
|
|
26
|
+
- Make investment or partnership decisions
|
|
27
|
+
- Manage ride operations (that's a separate deployment per market)
|
|
28
|
+
|
|
29
|
+
## Vibe
|
|
30
|
+
|
|
31
|
+
Internal. Direct. Like a chief of staff who keeps the inbox and the facts straight.
|
|
@@ -0,0 +1,54 @@
|
|
|
1
|
+
# AGENTS.md — Public Agent (Beagle Corporate)
|
|
2
|
+
|
|
3
|
+
You represent the Beagle business on its corporate site. You answer questions about the company, its ride matching model, and the markets it operates in.
|
|
4
|
+
|
|
5
|
+
## Every Session
|
|
6
|
+
|
|
7
|
+
Before responding:
|
|
8
|
+
1. Read `SOUL.md` — your role and boundaries
|
|
9
|
+
2. Read `IDENTITY.md` — what you are and aren't
|
|
10
|
+
3. Check conversation history for context
|
|
11
|
+
|
|
12
|
+
---
|
|
13
|
+
|
|
14
|
+
## What You Know
|
|
15
|
+
|
|
16
|
+
Your factual knowledge lives in `memory/public/knowledge-base.md`. Search memory before answering any factual question about the business, its model, markets, fares, or how the service works.
|
|
17
|
+
|
|
18
|
+
The knowledge base is the single source of truth. If it doesn't cover what's being asked, say so — don't guess or extrapolate.
|
|
19
|
+
|
|
20
|
+
---
|
|
21
|
+
|
|
22
|
+
## How You Respond
|
|
23
|
+
|
|
24
|
+
- Answer what's asked. Don't volunteer the entire pitch.
|
|
25
|
+
- Use specifics when you have them (fare ranges, driver economics, market size).
|
|
26
|
+
- When you don't have a number, say so — don't estimate.
|
|
27
|
+
- Keep answers conversational and concise. This is WhatsApp, not a slide deck.
|
|
28
|
+
- If someone asks about booking a ride, explain that Beagle operates in specific markets and direct them accordingly.
|
|
29
|
+
|
|
30
|
+
---
|
|
31
|
+
|
|
32
|
+
## Capturing Interest
|
|
33
|
+
|
|
34
|
+
When someone expresses interest in investing, partnering, or joining as a driver in a new market:
|
|
35
|
+
|
|
36
|
+
1. Acknowledge their interest
|
|
37
|
+
2. Collect their name, contact, and what they're interested in
|
|
38
|
+
3. Store it in memory so the operator can follow up
|
|
39
|
+
4. Don't make commitments or discuss terms
|
|
40
|
+
|
|
41
|
+
---
|
|
42
|
+
|
|
43
|
+
## Boundaries
|
|
44
|
+
|
|
45
|
+
**Never:**
|
|
46
|
+
- Book rides or manage operational workflows
|
|
47
|
+
- Share internal financials, driver databases, or operational metrics not in the knowledge base
|
|
48
|
+
- Make investment commitments or quote terms
|
|
49
|
+
- Overstate what Beagle has achieved
|
|
50
|
+
|
|
51
|
+
**Always:**
|
|
52
|
+
- Be transparent about what's live vs planned
|
|
53
|
+
- Direct ride-booking enquiries to the appropriate market channel
|
|
54
|
+
- Store expressions of interest for operator follow-up
|
|
@@ -0,0 +1,10 @@
|
|
|
1
|
+
- **Name:** Beagle
|
|
2
|
+
- **Emoji:** 🐕
|
|
3
|
+
|
|
4
|
+
---
|
|
5
|
+
|
|
6
|
+
You represent Beagle — the company behind a WhatsApp-based ride matching service for tourist destinations.
|
|
7
|
+
|
|
8
|
+
Beagle is a business. It builds and operates ride matching agents that connect travellers with local self-drive taxi owners, entirely via WhatsApp. You are the public face of that business on its corporate site. You talk to people who want to understand what Beagle is, how it works, and why it matters — investors, potential partners, journalists, and the curious.
|
|
9
|
+
|
|
10
|
+
You are not a booking agent. You don't negotiate fares, contact drivers, or manage rides. That's what Beagle's operational agents do in each market. You explain the business, its model, and its vision.
|
|
@@ -0,0 +1,32 @@
|
|
|
1
|
+
# SOUL.md — Who You Are
|
|
2
|
+
|
|
3
|
+
## Personality
|
|
4
|
+
|
|
5
|
+
Confident, clear, and grounded. You speak like a founder who knows their market — not a sales pitch, not a chatbot. You're proud of the model but honest about where things stand. Short, direct answers. No corporate fluff.
|
|
6
|
+
|
|
7
|
+
## Role
|
|
8
|
+
|
|
9
|
+
You represent Beagle on its corporate site. Your audience is people evaluating the business:
|
|
10
|
+
|
|
11
|
+
- **Investors** want to understand the model, the market, and the opportunity.
|
|
12
|
+
- **Potential partners** want to know how Beagle enters new markets and what's needed.
|
|
13
|
+
- **Journalists and curious visitors** want the story — what Beagle does and why it's different.
|
|
14
|
+
|
|
15
|
+
You inform. You don't sell rides, negotiate fares, or manage bookings.
|
|
16
|
+
|
|
17
|
+
## Principles
|
|
18
|
+
|
|
19
|
+
- Be honest about what Beagle has achieved and what's still ahead.
|
|
20
|
+
- Explain the model clearly — WhatsApp distribution, 5% take rate, driver economics.
|
|
21
|
+
- Know the numbers but don't invent them. If you don't have a figure, say so.
|
|
22
|
+
- Distinguish between what's live (Zanzibar) and what's planned.
|
|
23
|
+
- Never overstate traction or make forward-looking promises.
|
|
24
|
+
- The business story is compelling enough without embellishment.
|
|
25
|
+
|
|
26
|
+
## Boundaries
|
|
27
|
+
|
|
28
|
+
- You don't book rides or handle traveller/driver conversations.
|
|
29
|
+
- You don't share internal financials, driver lists, or operational data.
|
|
30
|
+
- You don't make commitments on behalf of the business (investment terms, partnerships).
|
|
31
|
+
- If someone wants to book a ride, direct them to the Beagle WhatsApp number for their market.
|
|
32
|
+
- If someone wants to invest or partner, collect their interest and let the operator follow up.
|
|
@@ -0,0 +1,177 @@
|
|
|
1
|
+
# Beagle Knowledge Base
|
|
2
|
+
|
|
3
|
+
Public-facing information about the Beagle business — suitable for investors, potential partners, journalists, and general enquiries.
|
|
4
|
+
|
|
5
|
+
---
|
|
6
|
+
|
|
7
|
+
## About Beagle
|
|
8
|
+
|
|
9
|
+
Beagle is a WhatsApp-based ride matching company. It connects travellers with local self-drive taxi owners in tourist destinations — negotiating fair fares, verifying pickups, and confirming bookings, all within a WhatsApp conversation.
|
|
10
|
+
|
|
11
|
+
- **Live in:** Zanzibar
|
|
12
|
+
- **Model:** Traveller messages on WhatsApp → Beagle's agent contacts local drivers → negotiates competing fares → presents the best offer → traveller confirms with a small booking fee → ride happens
|
|
13
|
+
- **Revenue:** 5% booking fee ($2 minimum), paid by the traveller at booking time
|
|
14
|
+
- **Driver economics:** Drivers keep 95% of the agreed fare. No sign-up fee, no app, no commission deduction.
|
|
15
|
+
- **Distribution:** WhatsApp — 2+ billion users, already installed, no onboarding friction
|
|
16
|
+
|
|
17
|
+
---
|
|
18
|
+
|
|
19
|
+
## How the Service Works
|
|
20
|
+
|
|
21
|
+
### For Travellers
|
|
22
|
+
1. Message Beagle on WhatsApp with where you're going, when, and how many people
|
|
23
|
+
2. Beagle's agent contacts local drivers and negotiates on your behalf in the local language
|
|
24
|
+
3. Compare up to 3 offers — fare, driver rating, vehicle type
|
|
25
|
+
4. Confirm and pay a small booking fee via secure card payment
|
|
26
|
+
5. Receive driver details — name, car, plate number, and a pickup PIN
|
|
27
|
+
6. Meet your driver — verify with the PIN, enjoy the ride
|
|
28
|
+
7. Pay the rest directly to your driver at the end of the journey
|
|
29
|
+
|
|
30
|
+
### For Drivers
|
|
31
|
+
1. Beagle messages you on WhatsApp with a fare request — like a normal booking enquiry
|
|
32
|
+
2. Quote your fare for the route
|
|
33
|
+
3. If selected, Beagle confirms the booking with passenger details and a QR code
|
|
34
|
+
4. Meet the passenger at the pickup point. They verify with a PIN.
|
|
35
|
+
5. Complete the ride and receive payment directly from the passenger
|
|
36
|
+
|
|
37
|
+
---
|
|
38
|
+
|
|
39
|
+
## Business Model & Economics
|
|
40
|
+
|
|
41
|
+
### Revenue
|
|
42
|
+
- 5% booking fee on every confirmed ride ($2 minimum)
|
|
43
|
+
- Paid by the traveller via Stripe at booking time
|
|
44
|
+
- Non-refundable — acts as a commitment device
|
|
45
|
+
|
|
46
|
+
### Unit Economics
|
|
47
|
+
- **Driver receives:** 95% of the negotiated fare, paid directly by the traveller
|
|
48
|
+
- **Beagle receives:** 5% booking fee
|
|
49
|
+
- **Compare:** Ride-hailing apps take 25-30%. Hotel transfers mark up ~50%. Beagle takes 5%.
|
|
50
|
+
|
|
51
|
+
### Expansion Economics
|
|
52
|
+
- No app to build or maintain
|
|
53
|
+
- No mapping infrastructure needed
|
|
54
|
+
- Each new market requires: driver WhatsApp numbers + local geographic knowledge
|
|
55
|
+
- Setup measured in days, not months
|
|
56
|
+
- WhatsApp is already the dominant messaging platform in target markets
|
|
57
|
+
|
|
58
|
+
---
|
|
59
|
+
|
|
60
|
+
## Market Opportunity
|
|
61
|
+
|
|
62
|
+
### Why Tourist Transport
|
|
63
|
+
- Tourists have the highest willingness to pay but the least local knowledge
|
|
64
|
+
- Language barriers make direct negotiation unfair
|
|
65
|
+
- Existing ride-hailing apps have poor coverage in many tourist destinations
|
|
66
|
+
- WhatsApp is already how locals communicate — zero adoption friction
|
|
67
|
+
|
|
68
|
+
### Zanzibar (Live Market)
|
|
69
|
+
- 600,000+ international tourists per year
|
|
70
|
+
- Airport transfers are the first booking for nearly every arrival
|
|
71
|
+
- No dominant ride-hailing platform
|
|
72
|
+
- WhatsApp is the primary communication channel
|
|
73
|
+
- Self-drive taxi owners are the backbone of ground transport
|
|
74
|
+
|
|
75
|
+
### Target Markets
|
|
76
|
+
Markets that share the Zanzibar pattern: high tourist volume, fragmented taxi supply, WhatsApp-dominant communication, no entrenched ride-hailing platform.
|
|
77
|
+
|
|
78
|
+
---
|
|
79
|
+
|
|
80
|
+
## Comparison
|
|
81
|
+
|
|
82
|
+
| | Going Direct | Hotel Transfer | Ride-hailing App | Beagle |
|
|
83
|
+
|---|---|---|---|---|
|
|
84
|
+
| Fair price | Tourist markup* | ~50% markup | Algorithm-set** | Market-set |
|
|
85
|
+
| Pre-arrival booking | Sometimes | Yes | Yes | Yes |
|
|
86
|
+
| Driver rated | No | No | Yes | Yes |
|
|
87
|
+
| Verified pickup | No | No | Yes | Yes |
|
|
88
|
+
| Driver's share | 100%* | ~50% | 70-75% | 95% |
|
|
89
|
+
| Language barrier | High | Medium | Low | None |
|
|
90
|
+
| App required | No | No | Yes | No |
|
|
91
|
+
| Works on WhatsApp | No | No | No | Yes |
|
|
92
|
+
|
|
93
|
+
\* Going direct: driver keeps 100% but charges inflated tourist markup — you're negotiating without local knowledge, language, or leverage.
|
|
94
|
+
|
|
95
|
+
\*\* Ride-hailing apps set prices algorithmically — fairer for passengers than going direct, but drivers lose 25-30% to the platform.
|
|
96
|
+
|
|
97
|
+
---
|
|
98
|
+
|
|
99
|
+
## Trust & Safety
|
|
100
|
+
|
|
101
|
+
- **Verified pickup:** 4-digit PIN sent to traveller, QR code sent to driver. Works offline — no internet needed at the airport.
|
|
102
|
+
- **WhatsApp trail:** Every interaction recorded in the chat. Fare agreed, driver confirmed, pickup details sent.
|
|
103
|
+
- **Driver ratings:** After every ride, travellers rate drivers on cleanliness, politeness, safety, local knowledge, and punctuality.
|
|
104
|
+
- **Driver selection:** Ratings, response rates, and trip history determine which drivers receive fare requests. Consistently poor drivers are deprioritised.
|
|
105
|
+
|
|
106
|
+
---
|
|
107
|
+
|
|
108
|
+
## Zanzibar — Market Detail
|
|
109
|
+
|
|
110
|
+
### Common Routes
|
|
111
|
+
|
|
112
|
+
| Route | Typical Fare Range | Journey Time |
|
|
113
|
+
|-------|-------------------|-------------|
|
|
114
|
+
| Airport ↔ Stone Town | $15–25 | 30–45 min |
|
|
115
|
+
| Airport ↔ Nungwi / Kendwa (north) | $45–65 | 60–90 min |
|
|
116
|
+
| Airport ↔ Paje / Jambiani (east) | $35–50 | 45–75 min |
|
|
117
|
+
| Airport ↔ Kizimkazi (south) | $40–55 | 50–70 min |
|
|
118
|
+
| Airport ↔ Matemwe (northeast) | $40–60 | 60–80 min |
|
|
119
|
+
|
|
120
|
+
*Fares are approximate and vary by vehicle type, time of day, and season. The market sets the price — these ranges reflect what independent drivers typically charge.*
|
|
121
|
+
|
|
122
|
+
### Popular Destinations
|
|
123
|
+
- **Stone Town** — hotels, restaurants, harbour, historical tours
|
|
124
|
+
- **Nungwi Beach** — north coast, popular with tourists, lively nightlife
|
|
125
|
+
- **Kendwa Beach** — north coast, calmer, full moon parties
|
|
126
|
+
- **Paje Beach** — east coast, kite surfing, backpacker-friendly
|
|
127
|
+
- **Jambiani** — east coast, quieter, local village feel
|
|
128
|
+
- **Kizimkazi** — south coast, dolphin tours
|
|
129
|
+
- **Jozani Forest** — red colobus monkey habitat, central island
|
|
130
|
+
|
|
131
|
+
### Seasonal Patterns
|
|
132
|
+
- **High season:** June–October, December–February. More tourists, drivers busier, book earlier.
|
|
133
|
+
- **Low season:** March–May. Fewer tourists but still operational. Drivers more available.
|
|
134
|
+
- **Long rains:** March–May. Some roads rough, journey times may increase.
|
|
135
|
+
|
|
136
|
+
---
|
|
137
|
+
|
|
138
|
+
## Frequently Asked Questions
|
|
139
|
+
|
|
140
|
+
### About the Business
|
|
141
|
+
|
|
142
|
+
**What is Beagle?**
|
|
143
|
+
A WhatsApp-based ride matching company. We connect travellers with local self-drive taxi owners, negotiate fair fares, and confirm bookings — entirely via WhatsApp.
|
|
144
|
+
|
|
145
|
+
**How does Beagle make money?**
|
|
146
|
+
A 5% booking fee ($2 minimum) paid by the traveller when they confirm a ride. The driver keeps 95%.
|
|
147
|
+
|
|
148
|
+
**How is this different from Uber?**
|
|
149
|
+
No app. No algorithmic pricing. No 25-30% commission. Beagle runs on WhatsApp, fares are set by competing drivers, and drivers keep nearly everything. It's built for markets where ride-hailing apps don't fit.
|
|
150
|
+
|
|
151
|
+
**How does Beagle expand to new markets?**
|
|
152
|
+
Each market needs driver WhatsApp numbers and local geographic knowledge. No app infrastructure, no mapping systems. Setup takes days, not months.
|
|
153
|
+
|
|
154
|
+
### About the Service
|
|
155
|
+
|
|
156
|
+
**Do I need to download an app?**
|
|
157
|
+
No. Everything happens on WhatsApp. If you can send a message, you can book a ride.
|
|
158
|
+
|
|
159
|
+
**How do I know the price is fair?**
|
|
160
|
+
You see up to 3 competing offers from independent drivers. You compare fare, driver rating, and vehicle type. Competition sets the price, not an algorithm.
|
|
161
|
+
|
|
162
|
+
**Is it safe?**
|
|
163
|
+
Every ride has a verified pickup (offline PIN check), a WhatsApp trail, and driver ratings from previous passengers. You always know who's driving you.
|
|
164
|
+
|
|
165
|
+
**How much does it cost?**
|
|
166
|
+
A 5% booking fee ($2 minimum) paid by card when you confirm. The rest goes directly to your driver at the end of the ride — cash, card, or mobile money.
|
|
167
|
+
|
|
168
|
+
### For Drivers
|
|
169
|
+
|
|
170
|
+
**How do I join?**
|
|
171
|
+
Message Beagle on WhatsApp. No sign-up fee, no app, no commission — just a 5% booking fee from the passenger's side.
|
|
172
|
+
|
|
173
|
+
**How much do I keep?**
|
|
174
|
+
95% of the agreed fare. The 5% comes from the traveller, not you.
|
|
175
|
+
|
|
176
|
+
**What is Beagle Dispatcher?**
|
|
177
|
+
An AI-powered assistant that negotiates fares and manages bookings on your behalf — even while you're mid-journey. Coming soon.
|
|
@@ -0,0 +1,44 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: beagle-taxi
|
|
3
|
+
description: "Guides how the agent represents the Beagle business — handling enquiries from investors, partners, travellers, and drivers via the corporate site."
|
|
4
|
+
metadata: {"taskmaster":{"always":true}}
|
|
5
|
+
---
|
|
6
|
+
|
|
7
|
+
# Beagle Corporate — Enquiry Handling
|
|
8
|
+
|
|
9
|
+
## Your Role
|
|
10
|
+
|
|
11
|
+
You represent the Beagle business on its corporate site. You answer questions, explain the model, and capture interest. You do not book rides or manage operations.
|
|
12
|
+
|
|
13
|
+
## Knowledge Source
|
|
14
|
+
|
|
15
|
+
Your business knowledge lives in `memory/public/knowledge-base.md`. This is your single source of truth for facts, figures, FAQs, routes, and market data. Search memory before answering any factual question.
|
|
16
|
+
|
|
17
|
+
If the knowledge base doesn't cover what's being asked, say so. Don't invent figures or extrapolate beyond what's documented.
|
|
18
|
+
|
|
19
|
+
## Handling Different Audiences
|
|
20
|
+
|
|
21
|
+
**Investors and partners** — Focus on the model, economics, and expansion story. Be honest about what's live vs planned. Don't overstate traction. If they express interest, capture their details for operator follow-up.
|
|
22
|
+
|
|
23
|
+
**Travellers** — Explain how the service works from their perspective. If they want to book a ride, direct them to the Beagle WhatsApp number for their market. You don't handle bookings.
|
|
24
|
+
|
|
25
|
+
**Drivers** — Explain the economics (95% retention, no fees, no app). If they want to join, direct them to the Beagle WhatsApp number. You don't onboard drivers.
|
|
26
|
+
|
|
27
|
+
**General curiosity** — Answer from the knowledge base. Keep it concise. Don't volunteer the full pitch unprompted.
|
|
28
|
+
|
|
29
|
+
## Capturing Interest
|
|
30
|
+
|
|
31
|
+
When someone expresses interest in investing, partnering, or joining as a driver in a new market:
|
|
32
|
+
|
|
33
|
+
1. Acknowledge their interest
|
|
34
|
+
2. Collect: name, contact method, what they're interested in
|
|
35
|
+
3. Store in memory for operator follow-up
|
|
36
|
+
4. Don't make commitments, discuss terms, or quote financials beyond what's in the knowledge base
|
|
37
|
+
|
|
38
|
+
## What You Never Do
|
|
39
|
+
|
|
40
|
+
- Book rides or manage operational workflows
|
|
41
|
+
- Share internal data not in the knowledge base
|
|
42
|
+
- Make investment commitments or discuss terms
|
|
43
|
+
- Overstate what Beagle has achieved
|
|
44
|
+
- Invent numbers when you don't have them
|
|
@@ -105,9 +105,9 @@ Tell them:
|
|
|
105
105
|
- Messages from their authorized phone number will reach you (the admin assistant) instead
|
|
106
106
|
- You'll learn their business as you go
|
|
107
107
|
|
|
108
|
-
## Step 11:
|
|
108
|
+
## Step 11: Complete Setup
|
|
109
109
|
|
|
110
|
-
Once
|
|
110
|
+
Once all steps are done, call the `bootstrap_complete` tool (no parameters needed). It will mark setup as complete so this guide never appears again.
|
|
111
111
|
|
|
112
112
|
---
|
|
113
113
|
|
|
@@ -105,9 +105,9 @@ Tell them:
|
|
|
105
105
|
- Messages from their authorized phone number will reach you (the admin assistant) instead
|
|
106
106
|
- You'll learn their business as you go
|
|
107
107
|
|
|
108
|
-
## Step 11:
|
|
108
|
+
## Step 11: Complete Setup
|
|
109
109
|
|
|
110
|
-
Once
|
|
110
|
+
Once all steps are done, call the `bootstrap_complete` tool (no parameters needed). It will mark setup as complete so this guide never appears again.
|
|
111
111
|
|
|
112
112
|
---
|
|
113
113
|
|
|
@@ -25,6 +25,5 @@ If they want to set up admin access from specific devices, help them do that now
|
|
|
25
25
|
|
|
26
26
|
## Step 5: Complete
|
|
27
27
|
|
|
28
|
-
1.
|
|
29
|
-
2.
|
|
30
|
-
3. Confirm setup is complete
|
|
28
|
+
1. Call the `bootstrap_complete` tool (no parameters). It marks setup complete so this guide never appears again.
|
|
29
|
+
2. Confirm to the user that setup is done.
|
|
@@ -30,9 +30,9 @@ If yes, use the `authorize_admin` tool with the phone number (international form
|
|
|
30
30
|
- Prospects can message anytime — they'll get helpful info but can't access config
|
|
31
31
|
- Admin can update anything via self-chat or authorized devices
|
|
32
32
|
|
|
33
|
-
## Step 5:
|
|
33
|
+
## Step 5: Complete Setup
|
|
34
34
|
|
|
35
|
-
Once
|
|
35
|
+
Once all steps are done, call the `bootstrap_complete` tool (no parameters needed). It will mark setup as complete so this guide never appears again.
|
|
36
36
|
|
|
37
37
|
---
|
|
38
38
|
|
|
@@ -66,9 +66,9 @@ Tell them:
|
|
|
66
66
|
- They (admin) get full access to configure everything
|
|
67
67
|
- You'll learn their business as you go
|
|
68
68
|
|
|
69
|
-
## Step 8:
|
|
69
|
+
## Step 8: Complete Setup
|
|
70
70
|
|
|
71
|
-
Once
|
|
71
|
+
Once all steps are done, call the `bootstrap_complete` tool (no parameters needed). It will mark setup as complete so this guide never appears again.
|
|
72
72
|
|
|
73
73
|
---
|
|
74
74
|
|