@sellable/install 0.1.83 → 0.1.84
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/package.json
CHANGED
|
@@ -341,6 +341,25 @@ lookup if it has not already run, then ask the campaign setup questions. The
|
|
|
341
341
|
setup questions should use the confirmed company context so they do not feel
|
|
342
342
|
generic.
|
|
343
343
|
|
|
344
|
+
### Sufficient Intake Bypass
|
|
345
|
+
|
|
346
|
+
When the user's invocation or first answer already supplies the campaign
|
|
347
|
+
identity plus enough strategy context to draft the campaign, do not turn that
|
|
348
|
+
into an interview. Treat setup as complete when the request contains:
|
|
349
|
+
|
|
350
|
+
- identity or client/company context;
|
|
351
|
+
- target prospects or buyer segment;
|
|
352
|
+
- offer / CTA;
|
|
353
|
+
- proof or claims to use / avoid;
|
|
354
|
+
- lead-source preference, supplied list, or permission to find people.
|
|
355
|
+
|
|
356
|
+
In that case, do one lightweight identity/company lookup, summarize the inferred
|
|
357
|
+
direction in one or two lines, and immediately draft the campaign brief. Do not
|
|
358
|
+
ask the buyer, offer, proof, or lead-source setup questions again unless a
|
|
359
|
+
required field is missing, the supplied inputs conflict, or the campaign focus is
|
|
360
|
+
genuinely ambiguous. It is fine to include an explicit assumption line in the
|
|
361
|
+
brief; the approval gate lets the user revise it.
|
|
362
|
+
|
|
344
363
|
Before the identity gate, use this customer-facing shape:
|
|
345
364
|
|
|
346
365
|
```text
|