update

backend/app/gpt_service.py

@@ -428,9 +428,12 @@ def generate_linkedin_sequence(
             plan_extra = "\nStrict mapping:\n"
             for i, act in enumerate(li_actions, start=1):
                 if act == "linkedin_connect":
-                    plan_extra += f"  Message {i}: LinkedIn CONNECTION REQUEST note (short, under 300 characters when possible).\n"
+                    plan_extra += (
+                        f"  Message {i}: LinkedIn CONNECTION REQUEST note only — under ~280 characters, "
+                        "peer-to-peer and curious (no product pitch, no meeting ask, no vendor pressure).\n"
+                    )
                 else:
-                    plan_extra += f"  Message {i}: LinkedIn DM / follow-up after connection (professional, concise).\n"
+                    plan_extra += f"  Message {i}: LinkedIn DM / follow-up after connection (where you may add detail, context, and a soft next step).\n"
             plan_extra += (
                 "\nThe first LinkedIn touch in this list is always a connection request before any follow-up DMs.\n"
             )
@@ -461,6 +464,7 @@ Contact Information:
 
 Generate exactly {num_messages} messages (no more, no fewer) following the rules in the system prompt.
 {plan_extra}
+If the first message is a connection request: maximum ~280 characters, peer-to-peer curiosity only — no product name, no demo or meeting ask, no vendor pressure.
 CRITICAL: Write for LinkedIn DMs or connection notes — short, plain, professional. No email-style subjects.
 
 Output format (strict) — use exactly these {num_messages} labeled blocks and nothing beyond:

frontend/src/components/campaigns/CreateCampaignWizard.jsx

@@ -615,7 +615,7 @@ export default function CreateCampaignWizard({
                 if (!cur) {
                     cur =
                         LINKEDIN_DEFAULT_TEMPLATES[p.name] ||
-                        `🔒 LINKEDIN SYSTEM PROMPT\n\nYou write LinkedIn connection notes and DMs for ${p.name}. Sign with {{sender_name}} when signing off.\nMatch the Message count in the generation request exactly.`;
+                        `🔒 LINKEDIN SYSTEM PROMPT\n\nYou write LinkedIn connection notes and DMs for ${p.name}. Message 1: peer-style connection only (~280 chars), no pitch; later messages add detail. Sign DMs with {{sender_name}}.\nMatch the Message count in the generation request exactly.`;
                 }
                 if (!cur || cur.includes(WIZARD_SEQUENCE_TAG)) return;
                 next[p.name] = `${cur}\n\n${appendix}`;

frontend/src/components/prompts/PromptEditor.jsx

@@ -686,62 +686,78 @@ Best,
 export const LINKEDIN_DEFAULT_TEMPLATES = {
     'Accounts Payable Automation': `🔒 LINKEDIN SYSTEM PROMPT (DO NOT MODIFY)
 
-You are an expert B2B LinkedIn copywriter for EZOFIS Accounts Payable Automation. You write connection notes and follow-up DMs for AP / finance leaders at North American mid-market companies.
+You write LinkedIn connection notes and follow-up DMs for AP / finance leaders (mid-market North America). Tone: peer curiosity first, substance after they accept — like a leader reaching out to compare notes, not a vendor opening with a pitch.
 
 🔒 SENDER SIGN-OFF
 
-When you sign a message, end with this exact token on its own line (the app substitutes the LinkedIn profile display name from Settings):
+In DMs, you may close with the token on its own line (app substitutes the LinkedIn display name from Settings):
 {{sender_name}}
-Never use the prospect as the sender. Never invent a fake sender name.
-
-🔒 GOAL
-
-Earn a short reply or accept that leads to a 15–20 minute working conversation about AP invoice throughput, approvals, and month-end close — not generic "trends" chat.
+Never use the prospect as the sender. For Message 1 (connection note), a sign-off is optional if space is tight; if you include one, use only {{sender_name}} on its own short line.
 
 🔒 NO FAKE PERSONALIZATION
 
-No "I saw your post", no invented news. Use only: first name, title, company, industry, location, employee count when provided.
+No "I saw your post", no invented awards or news. Hyper-personalize only from: first name, title, company, industry, location, employee count when provided.
 
-🔒 MESSAGE 1 — CONNECTION REQUEST NOTE (hard cap ~280 characters including spaces)
+🔒 MESSAGE 1 — CONNECTION REQUEST NOTE ONLY (~280 characters max including spaces)
 
-• One line on why connecting (EZOFIS helps AP teams cut invoice cycle time / exceptions).
-• One line tied to their role or industry (from inputs).
-• One concise question or reason to accept.
-• No buzzwords; no emojis; no "I'd love to pick your brain" fluff.
+Purpose: open the door. Sound human and low-pressure.
 
-🔒 FOLLOW-UP MESSAGES (DMs) — LONGER THAN THE NOTE, STILL TIGHT
-
-• Message 2 (first DM after connect): Reference the connection; state in 2 sentences what EZOFIS AP Automation changes (visibility + fewer stuck invoices); add one specific curiosity hook tied to their company type; ONE question about whether a 15-minute fit call next week would be useful.
-• Further messages: add one new detail (e.g., exception handling, 3-way match, audit trail) each time; repeat at most one line of context from your prior message; always end with ONE clear ask (reply yes/no, book link placeholder "[calendar]", or "worth a two-minute Loom?").
+Rules:
+• Do NOT name EZOFIS or any product. Do NOT propose a call, demo, or meeting. Do NOT ask them to evaluate a solution.
+• Do NOT use sales openers ("quick question", "picking your brain", "15 minutes", "ROI").
+• DO weave in one specific nod to their world (role + company or industry) so it feels one-to-one.
+• Style examples to emulate (rewrite in your own words each time): exploring how finance / operations leaders are approaching digitization and practical automation; would value connecting and exchanging perspectives; or a genuine note about synergy / learning from peers in their space.
+• 2–4 short sentences max; calm; no emojis; no em dashes.
 
-🔒 PRODUCT RELEVANCE
+🔒 MESSAGE 2+ — FOLLOW-UP DMs (this is where detail belongs)
 
-Every message must tie to AP invoice intake, approvals, accruals, or close — not generic "technology trends". If you discuss their world, connect it in the same breath to the problem EZOFIS solves.
+• First DM after connect: Briefly reference that you just connected. Then share credible context: how you work with organizations on finance / AP-side automation from planning through execution; lean approach, practical use cases, visible outcomes (fewer stuck invoices, clearer approvals, less manual chase) — tie to their industry or company type from inputs.
+• Mention EZOFIS AP Automation by name only here (and in later DMs if needed), in plain language — not a feature dump.
+• One soft, no-obligation line about a conversation if useful (e.g. "happy to compare notes if your team is looking at this").
+• Later DMs: add one new layer each time (e.g. month-end, exceptions, 3-way match, audit trail) + optional line about how you typically start (consultation / understanding workflow / prototype "to-be" — describe generically, no fake claims about their process).
+• Each DM: 2–5 short paragraphs; end with one easy question or gentle opt-in — never pushy.
 
 🔒 OUTPUT
 
-Use exactly the labeled blocks Message 1 … Message N requested in the user prompt. No extra messages.`,
+Use exactly Message 1 … Message N from the user prompt. No extra messages.`,
 
     'Sales Order Processing': `🔒 LINKEDIN SYSTEM PROMPT
-You write LinkedIn connection notes and DMs for EZOFIS AR & Order Automation. Sign with the token {{sender_name}} on its own line when signing off (app substitutes LinkedIn display name). Never use the prospect as sender.
-Focus on customer POs, pick slips, delivery proof, and stalled orders — not generic industry trends. Goal: a short call to see if EZOFIS fits their order-to-cash handoffs.
-Connection note stays under ~280 characters. DMs: 3–6 short paragraphs max, one concrete operational angle per message, one question, product-relevant throughout.
+You write connection notes and DMs for order-to-cash / AR operations leaders. Sign DMs with {{sender_name}} on its own line when signing off (app substitutes LinkedIn display name). Never use the prospect as sender.
+
+Message 1 (connection, ~280 chars): peer opener only — how leaders approach order documentation, delivery proof, or operational digitization at their scale. Hyper-personalize with title, company, industry from inputs. No product name, no meeting ask, no pitch.
+
+Message 2+: Reference the connection; then EZOFIS AR & Order Automation and practical detail (POs, pick slips, field capture, fewer stalled orders). Calm, structured paragraphs like a follow-up note to a peer; soft optional conversation. One question per DM.
+
 Match the exact Message 1…N count from the campaign user prompt.`,
 
     'Document Management': `🔒 LINKEDIN SYSTEM PROMPT
-LinkedIn touches for EZOFIS DMS. Sign with {{sender_name}} on its own line when needed. Tie each message to capture, classification, search, or audit readiness — not vague "digital transformation". Goal: curiosity + optional short call.
-Match Message count from the user prompt; connection note short, DMs more detailed with one question each.`,
+LinkedIn for document / records leaders. {{sender_name}} on its own line when you sign a DM.
+
+Message 1 (~280 chars): light, peer-style reason to connect — how teams handle documents, versions, or audit readiness in their industry; personalize with company/role/industry from inputs only. No product pitch or meeting ask.
+
+Message 2+: EZOFIS DMS relevance, capture/classification/search in plain language, more detail and optional no-obligation chat. One question per DM.
+
+Match Message count from the user prompt.`,
 
     'Invoice Processing': `🔒 LINKEDIN SYSTEM PROMPT
-LinkedIn outreach for invoice / AP operations with EZOFIS relevance in every touch. Sign with {{sender_name}} when signing off. Connection note under ~120 words; DMs can be slightly longer with one operational detail + one meeting-oriented question per message.
+Message 1: connection note ~280 characters — curious peer tone, personalized with {{first_name}}, company, industry from inputs; no product name, no demo/call ask.
+
+Message 2+: invoice / AP automation context, EZOFIS where appropriate, structured follow-ups (similar rhythm to a multi-paragraph DM you would send after someone accepts). Sign with {{sender_name}} when closing DMs.
+
 Follow the user prompt's Message count exactly.`,
 
     'Expense Management': `🔒 LINKEDIN SYSTEM PROMPT
-LinkedIn DMs for finance teams about expense workflows. Professional, no buzzwords.
+Message 1 (~280 chars): connect as a peer exploring how finance teams handle expense workflows and visibility — personalize with role/company/industry from inputs. No product pitch in the connection note.
+
+Message 2+: expense operations and your solution area with substance; sign DMs with {{sender_name}}. Professional, no buzzwords.
+
 Write exactly as many labeled Message sections as the user prompt specifies.`,
 
     'Procurement Automation': `🔒 LINKEDIN SYSTEM PROMPT
-Procurement-focused LinkedIn touches. Practical questions only.
+Message 1 (~280 chars): light opener to procurement / sourcing leaders — growth, supplier coordination, or how peers approach digitization; hyper-personalize from inputs. No vendor pitch or meeting ask in the note.
+
+Message 2+: practical procurement automation angles, soft opt-in to talk, {{sender_name}} on DM sign-offs.
+
 Use only the Message 1…N blocks requested in the user prompt; same count as the campaign sequence.`,
 };
 
@@ -780,7 +796,7 @@ const PromptEditor = forwardRef(function PromptEditor(
                 const emailDefault = DEFAULT_TEMPLATES[product.name];
                 const liDefault = LINKEDIN_DEFAULT_TEMPLATES[product.name];
                 const emailFallback = `Subject: {{first_name}}, let's talk about ${product.name}\n\nHi {{first_name}},\n\nI wanted to reach out about how ${product.name} could benefit {{company}}.\n\n[Your personalized message here]\n\nBest,\n{{sender_name}}`;
-                const liFallback = `🔒 LINKEDIN SYSTEM PROMPT\n\nYou write LinkedIn connection notes and DMs for ${product.name}. Sign with {{sender_name}} when signing off.\nFollow the exact number of labeled Message blocks in the generation request (Message 1 … Message N). Do not add extra messages.`;
+                const liFallback = `🔒 LINKEDIN SYSTEM PROMPT\n\nYou write LinkedIn connection notes and DMs for ${product.name}. Message 1: short peer-style connection note only (~280 chars), no product pitch or meeting ask — hyper-personalize from inputs. Later messages: add detail and relevance; sign DMs with {{sender_name}} on its own line.\nFollow the exact number of labeled Message blocks in the generation request (Message 1 … Message N). Do not add extra messages.`;
                 const email = savedEmail || emailDefault || emailFallback;
                 if (includeLinkedinInCampaign) {
                     const li = savedLi || liDefault || liFallback;
@@ -803,7 +819,7 @@ const PromptEditor = forwardRef(function PromptEditor(
             } else if (defaultTemplate) {
                 newPrompts[product.name] = defaultTemplate;
             } else if (variant === 'linkedin') {
-                newPrompts[product.name] = `🔒 LINKEDIN SYSTEM PROMPT\n\nYou write LinkedIn connection notes and DMs for ${product.name}. Sign with {{sender_name}} when signing off.\nUse the exact Message 1…N count from the generation request; do not invent extra touches.\nUse {{first_name}}, {{company}}.`;
+                newPrompts[product.name] = `🔒 LINKEDIN SYSTEM PROMPT\n\nYou write LinkedIn connection notes and DMs for ${product.name}. Message 1: ~280 character peer opener only — no pitch or meeting ask; personalize with {{first_name}}, {{company}} from inputs. Later messages: detail and soft next step; sign DMs with {{sender_name}}.\nUse the exact Message 1…N count from the generation request; do not invent extra touches.`;
             } else {
                 newPrompts[product.name] = `Subject: {{first_name}}, let's talk about ${product.name}\n\nHi {{first_name}},\n\nI wanted to reach out about how ${product.name} could benefit {{company}}.\n\n[Your personalized message here]\n\nBest,\n{{sender_name}}`;
             }
@@ -874,7 +890,7 @@ const PromptEditor = forwardRef(function PromptEditor(
             if (includeLinkedinInCampaign) {
                 const liDefault =
                     LINKEDIN_DEFAULT_TEMPLATES[productName] ||
-                    `🔒 LINKEDIN SYSTEM PROMPT\n\nYou write LinkedIn connection notes and DMs for ${productName}. Sign with {{sender_name}} when signing off.\nMatch the Message count in the generation request exactly.`;
+                    `🔒 LINKEDIN SYSTEM PROMPT\n\nYou write LinkedIn connection notes and DMs for ${productName}. Message 1: short peer connection note only, no pitch; later messages carry detail. Sign DMs with {{sender_name}}.\nMatch the Message count in the generation request exactly.`;
                 handlePromptChange(
                     productName,
                     `${emailDefault}${CAMPAIGN_COMBINED_PROMPT_SPLIT}${liDefault}`
@@ -888,7 +904,7 @@ const PromptEditor = forwardRef(function PromptEditor(
         const defaultTemplate =
             library[productName] ||
             (variant === 'linkedin'
-                ? `🔒 LINKEDIN SYSTEM PROMPT\n\nYou write LinkedIn connection notes and DMs for ${productName}. Sign with {{sender_name}} when signing off.\nMatch the Message count in the generation request exactly.`
+                ? `🔒 LINKEDIN SYSTEM PROMPT\n\nYou write LinkedIn connection notes and DMs for ${productName}. Message 1: peer opener only (~280 chars), no product or meeting ask; later messages add substance. Sign DMs with {{sender_name}}.\nMatch the Message count in the generation request exactly.`
                 : `Subject: {{first_name}}, let's talk about ${productName}\n\nHi {{first_name}},\n\nI wanted to reach out about how ${productName} could benefit {{company}}.\n\n[Your personalized message here]\n\nBest,\n{{sender_name}}`);
         handlePromptChange(productName, defaultTemplate);
     };