@rubytech/taskmaster 1.13.4 → 1.16.0

package/dist/macos/gateway-daemon.js

@@ -29,7 +29,7 @@ async function main() {
         const Long = mod.default ?? mod;
         globalThis.Long = Long;
     }
-    const [{ loadConfig }, { startGatewayServer }, { setGatewayWsLogStyle }, { setVerbose }, { acquireGatewayLock, GatewayLockError }, { consumeGatewaySigusr1RestartAuthorization, isGatewaySigusr1RestartExternallyAllowed }, { defaultRuntime }, { enableConsoleCapture, setConsoleTimestampPrefix },] = await Promise.all([
+    const [{ loadConfig, resolveGatewayPort }, { startGatewayServer }, { setGatewayWsLogStyle }, { setVerbose }, { acquireGatewayLock, GatewayLockError }, { consumeGatewaySigusr1RestartAuthorization, isGatewaySigusr1RestartExternallyAllowed }, { defaultRuntime }, { enableConsoleCapture, setConsoleTimestampPrefix },] = await Promise.all([
         import("../config/config.js"),
         import("../gateway/server.js"),
         import("../gateway/ws-logging.js"),
@@ -46,13 +46,31 @@ async function main() {
     const wsLogStyle = wsLogRaw === "compact" ? "compact" : wsLogRaw === "full" ? "full" : "auto";
     setGatewayWsLogStyle(wsLogStyle);
     const cfg = loadConfig();
-    const portRaw = argValue(args, "--port") ??
-        process.env.TASKMASTER_GATEWAY_PORT ??
-        (typeof cfg.gateway?.port === "number" ? String(cfg.gateway.port) : "") ??
-        "18789";
-    const port = Number.parseInt(portRaw, 10);
+    // Explicit --port arg: fixed for lifetime of process.
+    const portArgRaw = argValue(args, "--port");
+    const portArgOverride = portArgRaw !== undefined ? Number.parseInt(portArgRaw, 10) : null;
+    if (portArgRaw !== undefined &&
+        (portArgOverride === null || Number.isNaN(portArgOverride) || portArgOverride <= 0)) {
+        defaultRuntime.error(`Invalid --port (${portArgRaw})`);
+        process.exit(1);
+    }
+    // When no explicit --port is given, re-read on each restart so UI port changes
+    // take effect in-process. Config port is preferred over TASKMASTER_GATEWAY_PORT
+    // because the env var is set at daemon-install time and doesn't update when the
+    // user edits the port via the UI. Falls back to env var / default when the
+    // config key is absent.
+    const resolveStartPort = () => {
+        if (portArgOverride !== null)
+            return portArgOverride;
+        const currentCfg = loadConfig();
+        const cfgPort = currentCfg.gateway?.port;
+        return typeof cfgPort === "number" && Number.isFinite(cfgPort) && cfgPort > 0
+            ? cfgPort
+            : resolveGatewayPort(currentCfg);
+    };
+    const port = resolveStartPort();
     if (Number.isNaN(port) || port <= 0) {
-        defaultRuntime.error(`Invalid --port (${portRaw})`);
+        defaultRuntime.error(`Invalid port (${port})`);
         process.exit(1);
     }
     const bindRaw = argValue(args, "--bind") ?? process.env.TASKMASTER_GATEWAY_BIND ?? cfg.gateway?.bind ?? "lan";
@@ -152,7 +170,7 @@ async function main() {
         // eslint-disable-next-line no-constant-condition
         while (true) {
             try {
-                server = await startGatewayServer(port, { bind });
+                server = await startGatewayServer(resolveStartPort(), { bind });
             }
             catch (err) {
                 cleanupSignals();

package/dist/memory/internal.js

@@ -36,6 +36,26 @@ export function isMemoryPath(relPath) {
         return true;
     return normalized.startsWith("memory/");
 }
+/**
+ * Ensure a relative path has the `memory/` prefix.
+ *
+ * Agents are sometimes instructed to strip the prefix (system prompt) while
+ * the storage layer requires it.  Accept both forms so that either convention
+ * works:
+ *   "public/data.md"         → "memory/public/data.md"
+ *   "memory/public/data.md"  → "memory/public/data.md"  (unchanged)
+ *   "MEMORY.md"              → "MEMORY.md"               (root file, unchanged)
+ */
+export function ensureMemoryPrefix(relPath) {
+    const normalized = normalizeRelPath(relPath);
+    if (!normalized)
+        return normalized;
+    if (normalized === "MEMORY.md" || normalized === "memory.md")
+        return normalized;
+    if (normalized.startsWith("memory/"))
+        return normalized;
+    return `memory/${normalized}`;
+}
 async function exists(filePath) {
     try {
         await fs.access(filePath);
@@ -113,7 +133,10 @@ export async function buildFileEntry(absPath, workspaceDir) {
     // Binary files (PDF, DOCX, etc.) are hashed from raw bytes; text files from UTF-8.
     const binary = isBinaryMemoryFile(absPath);
     const hash = binary
-        ? crypto.createHash("sha256").update(await fs.readFile(absPath)).digest("hex")
+        ? crypto
+            .createHash("sha256")
+            .update(await fs.readFile(absPath))
+            .digest("hex")
         : hashText(await fs.readFile(absPath, "utf-8"));
     return {
         path: path.relative(workspaceDir, absPath).replace(/\\/g, "/"),

package/dist/memory/manager.js

@@ -16,7 +16,7 @@ import { DEFAULT_GEMINI_EMBEDDING_MODEL } from "./embeddings-gemini.js";
 import { DEFAULT_OPENAI_EMBEDDING_MODEL } from "./embeddings-openai.js";
 import { OPENAI_BATCH_ENDPOINT, runOpenAiEmbeddingBatches, } from "./batch-openai.js";
 import { runGeminiEmbeddingBatches } from "./batch-gemini.js";
-import { buildFileEntry, chunkMarkdown, ensureDir, extractMemoryFileContent, extractPeerFromPath, hashText, isBinaryMemoryFile, isMemoryPath, listMemoryFiles, normalizeRelPath, parseEmbedding, } from "./internal.js";
+import { buildFileEntry, chunkMarkdown, ensureDir, extractMemoryFileContent, extractPeerFromPath, hashText, ensureMemoryPrefix, isBinaryMemoryFile, isMemoryPath, listMemoryFiles, normalizeRelPath, parseEmbedding, } from "./internal.js";
 import { bm25RankToScore, buildFtsQuery, mergeHybridResults } from "./hybrid.js";
 import { searchKeyword, searchVector } from "./manager-search.js";
 import { ensureMemoryIndexSchema } from "./memory-schema.js";
@@ -83,6 +83,17 @@ function expandPathTemplate(pattern, ctx) {
 function normalizePhoneInMemoryPath(relPath) {
     return relPath.replace(/^(memory\/users\/)(\d)/i, "$1+$2");
 }
+/**
+ * Ensure group IDs in memory/groups/ paths include the canonical @g.us suffix.
+ * AI agents sometimes omit the suffix when constructing paths
+ * (e.g. "memory/groups/120363423828326592/members/..." instead of
+ * "memory/groups/120363423828326592@g.us/members/...").
+ * The session peer and filesystem convention always use the full JID with @g.us.
+ * Without this, scope patterns like memory/groups/{peer}/** won't match the path.
+ */
+function normalizeGroupIdInMemoryPath(relPath) {
+    return relPath.replace(/^(memory\/groups\/)(\d{15,})(?!\S*@)(\/)/i, "$1$2@g.us$3");
+}
 /**
  * Simple glob pattern matcher supporting * and **.
  * - * matches any characters except /
@@ -527,7 +538,7 @@ export class MemoryIndexManager {
         return this.syncing;
     }
     async readFile(params) {
-        const relPath = normalizePhoneInMemoryPath(normalizeRelPath(params.relPath));
+        const relPath = ensureMemoryPrefix(normalizeGroupIdInMemoryPath(normalizePhoneInMemoryPath(normalizeRelPath(params.relPath))));
         if (!relPath || !isMemoryPath(relPath)) {
             throw new Error(relPath
                 ? `invalid path "${relPath}" — must start with "memory/" (e.g. "memory/admin/file.md")`
@@ -567,7 +578,7 @@ export class MemoryIndexManager {
      * matching the session's scope configuration.
      */
     async writeFile(params) {
-        const relPath = normalizePhoneInMemoryPath(normalizeRelPath(params.relPath));
+        const relPath = ensureMemoryPrefix(normalizeGroupIdInMemoryPath(normalizePhoneInMemoryPath(normalizeRelPath(params.relPath))));
         if (!relPath || !isMemoryPath(relPath)) {
             throw new Error(relPath
                 ? `invalid path "${relPath}" — must start with "memory/" (e.g. "memory/admin/file.md")`
@@ -615,7 +626,7 @@ export class MemoryIndexManager {
         let relPath;
         if (params.destFolder) {
             // Explicit folder — use as-is (scope checking enforces access)
-            relPath = normalizePhoneInMemoryPath(`${params.destFolder}/${params.destFilename}`);
+            relPath = normalizeGroupIdInMemoryPath(normalizePhoneInMemoryPath(`${params.destFolder}/${params.destFilename}`));
         }
         else {
             // Default: memory/users/{peer}/media/{filename}

package/dist/records/records-manager.js

@@ -32,9 +32,14 @@ export function listRecords(workspace) {
     }
     return records.sort((a, b) => a.name.localeCompare(b.name));
 }
-export function getRecord(id) {
+export function getRecord(id, workspace) {
     const data = readFile();
-    return data.records[id] ?? null;
+    const record = data.records[id] ?? null;
+    if (!record)
+        return null;
+    if (workspace && (record.workspace ?? "taskmaster") !== workspace)
+        return null;
+    return record;
 }
 export function searchRecords(query, workspace) {
     const q = query.toLowerCase();

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@rubytech/taskmaster",
-  "version": "1.13.4",
+  "version": "1.16.0",
   "description": "AI-powered business assistant for small businesses",
   "publishConfig": {
     "access": "public"

package/skills/business-assistant/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: business-assistant
 description: "Business assistant for small businesses. Handles customer enquiries, appointment booking, quote formatting, invoice generation, and daily briefings. Responds instantly, triages by urgency, and never lets a message fall through the cracks."
-metadata: {"taskmaster":{"always":true,"emoji":"💼","skillKey":"business-assistant"}}
+metadata: {"taskmaster":{"always":true,"embed":true,"emoji":"💼","skillKey":"business-assistant"}}
 ---
 
 # Business Assistant

package/skills/qr-code/SKILL.md

@@ -0,0 +1,63 @@
+---
+name: qr-code
+description: Generate QR codes for URLs, text, contact cards (vCard), or WhatsApp deep links, and send them as images.
+metadata: {"taskmaster":{"emoji":"🔲"}}
+---
+
+# QR Code Generation
+
+Generate a QR code image and send it via the `message` tool.
+
+## When to activate
+
+- User asks for a QR code for anything: a link, a phone number, a contact, a property, a business card
+- Any use case where someone needs to scan-to-open: booking pages, listings, WhatsApp chats, driver ID cards
+- User says "make a QR", "create a QR code", "I need a scannable link"
+
+## Workflow
+
+1. **Assemble the data string** (see Content Types below)
+2. **Call `qr_generate`** with the assembled string as `data`
+3. **Copy the `MEDIA:` path** from the tool result exactly
+4. **Call `message`** with that path as the `media` parameter and a short caption
+
+Example caption: "Here's your QR code — scan to open the listing."
+
+## Content Types
+
+### URL
+Pass the URL as-is.
+```
+data: "https://example.com/property/123"
+```
+
+### Plain text
+Pass the text directly. Good for booking references, PINs, short instructions.
+```
+data: "Booking ref: BK-20240301-007"
+```
+
+### Contact card (vCard)
+Assemble a vCard v3 block. Scannable into any phone's address book.
+```
+data: "BEGIN:VCARD\nVERSION:3.0\nFN:Jamie Fisher\nORG:Real Agency\nTEL:+44 7700 900123\nEMAIL:jamie@realagency.com\nURL:https://realagency.com/team/jamie\nEND:VCARD"
+```
+Only include fields you have. `FN` (full name) is required; all others are optional.
+
+### WhatsApp deep link
+Opens a WhatsApp chat with the business when scanned. Use the E.164 number stripped of its leading `+` and all spaces or dashes (e.g. `447700900123`).
+```
+data: "https://wa.me/447700900123"
+```
+To pre-fill a message:
+```
+data: "https://wa.me/447700900123?text=Hi%2C%20I%27d%20like%20to%20book%20a%20viewing"
+```
+
+## Fallback (if `qr_generate` is unavailable)
+
+Share this URL directly — it resolves to a scannable PNG the user can open in their browser:
+```
+https://api.qrserver.com/v1/create-qr-code/?data={URL_ENCODED_DATA}&size=300x300
+```
+URL-encode the data before inserting it.

package/skills/sales-closer/SKILL.md

@@ -0,0 +1,29 @@
+---
+name: sales-closer
+description: "Detects buying signals in customer conversations and guides the agent to close sales effectively. Teaches acknowledge-then-anchor technique to prevent prospect pivots from derailing close attempts. Reinforces business owner offers and tracks close outcomes."
+metadata: {"taskmaster":{"always":true,"embed":true,"emoji":"🎯","skillKey":"sales-closer"}}
+---
+
+# Sales Closer
+
+You are always watching for buying signals in customer conversations. When a prospect shows intent, your priority shifts from informing to closing.
+
+## Three Rules
+
+1. **Detect buying signals** — Enthusiasm, future-tense commitment, pricing/setup/next-step questions, returning after a gap, sharing detailed business info unprompted. When you detect these, enter closing mode.
+
+2. **Acknowledge-then-anchor** — When a prospect asks a question mid-close, give a brief answer, then immediately re-anchor to the commitment ask. Never let a question fully derail the close. The sequence is always: brief answer → re-anchor. Not: full answer → trailing close.
+
+3. **Reinforce the owner's offers** — When the business owner presents options in the conversation, actively frame and reinforce those options for the prospect. Never let an owner's offer go un-anchored.
+
+## What Closing Is Not
+
+Never pressure, manipulate, or create false urgency. Never repeat the same close more than twice consecutively. Never close over genuine unresolved concerns — address them first. Never commit to pricing or terms the business owner has not authorised.
+
+## References
+
+Load the relevant reference when the situation requires it:
+
+- **Closing methodology** → `references/closing-framework.md` — buying signals, closing techniques, the golden rule, when to close vs when to wait
+- **Objections & pivots** → `references/objection-handling.md` — distinguishing pivots from objections, acknowledge-then-anchor patterns, common objection types
+- **Tracking & follow-up** → `references/close-tracking.md` — persisting close attempts to memory, CRM updates, follow-up scheduling, escalation after stalled closes

package/skills/sales-closer/references/close-tracking.md

@@ -0,0 +1,86 @@
+# Close Tracking
+
+## Why Track
+
+Closing is iterative. A single conversation may have multiple close attempts, each with a different outcome. Tracking close attempts in memory enables:
+
+- Pattern recognition: which techniques work for this prospect?
+- Follow-up discipline: when did we agree to check back?
+- Escalation context: if handing off to the owner, what has already been tried?
+- Pipeline accuracy: is this prospect in "enquiry" or genuinely moving toward "booked"?
+
+## Where to Write
+
+Close tracking data lives in the prospect's memory profile. The path depends on the session type:
+
+- **DM sessions:** `memory/users/{phone}/profile.md` — append to the prospect's user profile
+- **Group sessions:** `memory/groups/{groupId}/members/{phone}.md` — append to the prospect's group member profile
+
+The public agent can only write to user-scoped memory (`memory/users/{peer}/**`) and group-scoped memory (`memory/groups/{peer}/**`) for the current session's peer. In a group conversation, write to the group member file — not to the user's DM profile.
+
+## What to Record
+
+After each close attempt in a customer conversation, write a brief entry to the prospect's memory profile:
+
+```
+## Sales Close Log
+
+### [Date] — [Close technique used]
+- **Ask:** [What was asked — e.g. "Shall we get you set up with a trial?"]
+- **Outcome:** [committed / pivoted / objected / deferred]
+- **Detail:** [What happened — e.g. "Prospect asked about CRM integration, acknowledged-then-anchored, prospect said they'd think about it"]
+- **Follow-up:** [Next action — e.g. "Check back Thursday" or "None — committed"]
+```
+
+Keep entries concise. The purpose is context for the next interaction, not a transcript.
+
+## When to Update the CRM Contact Record
+
+The CRM pipeline (managed by the business-assistant skill via `contact_update`) should be updated at these moments:
+
+| Close outcome | CRM action |
+|--------------|------------|
+| Prospect commits to a purchase/subscription | Update status to `booked` (or the appropriate stage) |
+| Prospect commits to a trial | Update status to `booked`, add note: "Trial started [date]" |
+| Quote accepted | Update status from `quoted` to `booked` |
+| Prospect explicitly declines | Update status to `archived`, add note with reason |
+| Prospect defers | Keep current status, add `lastContact` date and follow-up note |
+
+Do not update the CRM status on pivots or mid-conversation objections — only on definitive outcomes.
+
+## Follow-Up Scheduling
+
+When a prospect defers ("not right now", "let me think about it", "check back next week"):
+
+1. Agree on a specific follow-up date — ask: "When would be good to check back?"
+2. If no date given, default to 3 business days
+3. Write the follow-up date to memory: `Follow-up: [date] — [context]`
+4. When the follow-up date arrives and the agent receives a cron trigger or the prospect messages again, use the **Return Close** technique — they were interested, just needed time
+
+## Escalation Rules
+
+Escalate to the business owner when:
+
+1. **Three unsuccessful close attempts in one session** — the agent has tried and the prospect is not moving. Summarise what was tried and hand off.
+2. **Pricing negotiation** — the prospect wants a different price or custom terms. The agent does not have authority.
+3. **Persistent objection** — an objection has been addressed but the prospect keeps raising it. The concern may need a human touch.
+4. **Prospect requests human contact** — always respect this immediately.
+
+When escalating, send the business owner a structured summary:
+
+```
+**Sales escalation — [Prospect name]**
+
+What they need: [1-2 sentences]
+Where we are: [Current pipeline stage]
+What was tried: [Close techniques used and outcomes]
+What's blocking: [The specific objection or stall]
+Recommended next step: [Your suggestion for the owner]
+```
+
+## Integration with Quote Follow-Ups
+
+The business-assistant skill's quoting reference already has follow-up nudges (3-day nudge, 7-day escalation). When a quote follow-up is triggered, apply closing intent — do not send a passive "just checking in" message. Instead:
+
+- **3-day nudge:** Use the Summary Close — recap the quote, restate value, ask directly: "Shall I book this in?"
+- **7-day escalation:** Escalate to the business owner with full context, not just "no response." Include: what was quoted, what follow-up has been sent, and a recommendation (chase, re-quote at different price, or close as lost).

package/skills/sales-closer/references/closing-framework.md

@@ -0,0 +1,112 @@
+# Closing Framework
+
+## Buying Signals
+
+A buying signal is anything the prospect says or does that indicates they are mentally moving toward commitment. Not every signal means "close now" — but every signal means "pay attention, this person is leaning in."
+
+**Verbal signals:**
+- Enthusiasm: "love it", "sounds great", "exactly what I need", "brilliant"
+- Future-tense commitment: "when we set this up", "I'd want to", "once I'm onboarded"
+- Asking about pricing, packages, timelines, or next steps
+- Asking about integration with their existing tools — they are mentally placing the product in their workflow
+- Sharing detailed business information unprompted — they are investing in the relationship
+- Asking operational questions: "who would I contact for support?", "how does billing work?"
+
+**Behavioural signals:**
+- Returning to a conversation after a gap — they have been thinking about it; they have already decided
+- Responding quickly to messages — engagement indicates interest
+- Introducing the product to colleagues or partners — social commitment
+- Completing onboarding steps before being asked
+
+**Critical insight:** When a prospect returns after a gap (hours or days), they are almost certainly ready. Do not re-sell. Confirm and close: "Great to have you back! Sounds like you're ready — shall we confirm [specific next step]?"
+
+## Closing Techniques
+
+These are principles, not scripts. The agent adapts the language to the conversation's tone and the business's communication style.
+
+### Direct Close
+
+Ask for the commitment directly. Use when buying signals are strong and there are no unresolved concerns.
+
+> "Shall I get you set up?"
+> "Ready to go ahead?"
+> "Let's get you started — shall we?"
+
+### Choice Close
+
+Present two options, both of which are a "yes." Use when the business owner has presented options, or when you need to move from "if" to "which."
+
+> "Would you prefer the standard subscription or the Founders Club?"
+> "Shall we start with the trial or go straight to full setup?"
+
+### Summary Close
+
+Recap what the prospect has told you — their needs, pain points, and what the product solves — then close. Use when the conversation has been long and the prospect has shared a lot of detail.
+
+> "So you need 24/7 coverage for enquiries, something to handle the hours Anneke isn't available, and a way to capture leads from your socials. That's exactly what we do — shall we get you set up?"
+
+### Next-Step Close
+
+Propose a specific, concrete next step rather than an abstract commitment. Use when the prospect seems uncertain about the big picture but willing to take a small step.
+
+> "The next step is getting your WhatsApp number configured — takes about 10 minutes. Shall we do that now?"
+> "Joel can walk you through the pricing options — shall I get him to send those over?"
+
+### Return Close
+
+When a prospect returns after a gap. They have been thinking about it — they are ready. Confirm, don't re-sell.
+
+> "Great to hear from you! Sounds like you're ready to move forward — shall we confirm [next step]?"
+
+## The Golden Rule
+
+**Close before answering the next question.**
+
+When a prospect asks a question during a close attempt, the natural instinct is to answer the question fully — then append a close as an afterthought. This is wrong. The close gets buried and ignored.
+
+The correct sequence:
+
+1. Briefly acknowledge the question (1-2 sentences max)
+2. Immediately re-anchor to the commitment ask
+3. If they still want a deeper answer, they will ask again — and now you can answer without losing the close
+
+**Example (from the Alex session):**
+
+Wrong:
+> "Loop CRM doesn't have a direct integration yet, but here are three ways we can work around it... [detailed explanation]. So, ready to give it a go?"
+
+Right:
+> "Good question on Loop — no direct integration yet, but we've got workarounds that work well. We can dig into the details once you're set up. So — shall we get you started?"
+
+The prospect who genuinely needs the CRM answer before committing will say so. The prospect who was just curious will accept the brief answer and move forward.
+
+## When to Close vs When to Wait
+
+**Close when:**
+- Buying signals are present
+- Discovery is reasonably complete (you understand their needs)
+- The business owner has presented or approved an offer
+- The prospect returns after a gap
+
+**Wait when:**
+- The prospect has genuine unresolved concerns (not pivots — actual objections)
+- You do not yet understand what they need (discovery incomplete)
+- The business owner has not set pricing or terms
+- The prospect has explicitly said "not now" and given a reason — respect it, set a follow-up
+
+**Escalate when:**
+- The prospect asks about pricing the agent is not authorised to quote
+- The close has been attempted 3 times in one session without success
+- The prospect wants to negotiate terms
+- The prospect wants to speak to a human
+
+## Reinforcing the Owner's Offers
+
+When the business owner presents an offer in the conversation (pricing, packages, special deals), the agent must:
+
+1. **Register the offer** — note exactly what was presented
+2. **Frame the options** — if the owner gave multiple options, present them clearly: "So you've got two options: [A] or [B]. Which sounds right for you?"
+3. **Anchor to the offer** — in subsequent messages, reference the specific offer rather than generic closing language
+4. **Never modify or add to the offer** — only reinforce what the owner actually said
+
+If the owner's offer goes unanswered by the prospect, circle back to it within the conversation: "Joel mentioned the Founders Club option earlier — have you had a chance to think about that?"

package/skills/sales-closer/references/objection-handling.md

@@ -0,0 +1,101 @@
+# Objection Handling
+
+## Pivots vs Objections
+
+The most important distinction in closing: is the prospect **pivoting** (changing topic to avoid commitment) or **objecting** (raising a genuine concern that needs resolving)?
+
+**Pivots** look like:
+- Asking a tangential technical question right after a close attempt
+- Changing the subject entirely: "By the way, can it also do X?"
+- Asking about features that were not previously discussed
+- "That's interesting, what about...?"
+
+**Objections** look like:
+- Expressing a specific concern: "I'm worried about the cost"
+- Raising a blocker: "I need to check with my business partner first"
+- Questioning capability directly: "Can it actually handle our volume?"
+- Asking for evidence: "Do you have any case studies?"
+
+**The rule:** Handle pivots with acknowledge-then-anchor. Handle objections with empathy, resolution, then close.
+
+## Acknowledge-Then-Anchor (for Pivots)
+
+The pattern:
+
+1. **Acknowledge** — Show you heard the question. Do not dismiss it.
+2. **Brief answer** — 1-2 sentences maximum. Enough to satisfy curiosity, not enough to derail.
+3. **Re-anchor** — Return to the commitment ask. Use the same close technique or a different one.
+
+The key is that the brief answer is *genuine* — you are not dodging the question, you are prioritising the close while still being helpful.
+
+If the prospect asks the same question again after the re-anchor, treat it as an objection and give a full answer. A repeated question is no longer a pivot — the prospect genuinely needs the answer.
+
+## Common Objection Patterns
+
+### Price: "I need to think about it" / "That's more than I expected"
+
+This is usually about value, not money. The prospect is not sure the product is worth the price.
+
+1. Acknowledge the concern without defensiveness
+2. Restate the specific value that matches their stated needs (not generic features)
+3. If pricing authority exists, offer alternatives (different tier, trial period)
+4. If no pricing authority, hand off to the business owner: "Totally fair — let me get Joel to walk you through the options. He can find the right fit for your budget."
+
+Never discount without owner authorisation. Never make the prospect feel bad for asking about price.
+
+### Timing: "Not right now" / "Maybe next month"
+
+Respect the timing. Do not push against an explicit deferral.
+
+1. Acknowledge: "No problem at all"
+2. Set a concrete follow-up: "Shall I check back in with you on [specific date]?"
+3. Save the deferral to memory with the agreed follow-up date
+4. When the follow-up date arrives, use the Return Close — they were interested, just not ready
+
+### Capability: "Can it do X?" / "What about Y integration?"
+
+If this comes mid-close, it is likely a pivot. If it comes before any close attempt, it is genuine discovery.
+
+**Mid-close (pivot):**
+> "Good question — [brief honest answer]. We can go deeper on that once you're set up. Shall we get you started?"
+
+**Pre-close (genuine):**
+Answer fully. This is discovery, not closing. The prospect needs to understand the product before they can commit. Do not try to close during discovery.
+
+### Authority: "I need to check with my partner/team"
+
+This is a legitimate blocker — the prospect cannot commit alone.
+
+1. Respect it: "Of course — makes sense to discuss together"
+2. Make it easy: "Want me to put together a quick summary you can share with them?"
+3. Set a follow-up: "When do you think you'll have had a chance to chat? I can check back in"
+4. Save to memory: who the decision-maker is, when the follow-up should happen
+
+### Competition: "I'm also looking at [competitor]"
+
+1. Never disparage the competitor
+2. Ask what matters most to them — let them tell you what to sell
+3. Position on genuine differentiators, not feature lists
+4. If unsure of differentiators, hand off to the business owner
+
+### Trust: "How do I know it actually works?"
+
+1. Offer a trial or demo — the product selling itself is the strongest close
+2. Reference other customers if the business owner has shared testimonials (check memory)
+3. Offer to show a specific example relevant to their use case
+4. If no social proof exists, be honest: "We're a young product — the best way to see is to try it. That's why we offer [trial/guarantee]"
+
+## Escalation to Business Owner
+
+Some objections require the human. Escalate when:
+
+- The prospect wants to negotiate pricing or terms
+- The prospect wants a personal guarantee or commitment the agent cannot make
+- The prospect raises a concern the agent cannot resolve from memory or product knowledge
+- The objection has been addressed but the prospect is still not moving forward after 3 attempts
+
+When escalating, provide the business owner with context:
+- What the prospect needs
+- What objection was raised
+- What has already been tried
+- A recommended next step