The Lead Relay takes over the first review of new leads as soon as they come in through a form. Instead of every inquiry being screened manually and prioritized roughly by gut feeling, an AI scoring step evaluates budget, need and timing against predefined criteria and assigns a traceable A to D score with a rationale.
\nThe core of the workflow is the point logic itself: three criteria, each worth up to ten points, and an overall score that determines how the lead is handled next. What sets it apart from a plain scoring tool is the confidence rating. When form fields are incomplete or an entry stays vague, the assistant flags this in the result instead of projecting a precision the data does not support. That builds trust in the prioritization, especially at the borderline between two scoring tiers.
\nA human stays in the loop at two points: calibrating the scoring thresholds initially against real deals already won or lost, and spot checking the first runs before the workflow continues without supervision. From there, the relay handles the presorting and sales handles the close.
\nCopy the prompt below in full into your automation tool or agent builder. As a file: lead-staffel.en.json
\n" } ], "schritte": [ { "nr": 1, "titel": "Trigger: new lead", "beschreibung": "A form webhook delivers the incoming lead data, including budget, need and timing, to the workflow.", "rolle": "mensch" }, { "nr": 2, "titel": "Enrichment", "beschreibung": "Company size, industry and tech stack can optionally be added through an enrichment service such as Clearbit or Apollo, to complete the picture before scoring.", "rolle": "automatisch" }, { "nr": 3, "titel": "AI scoring", "beschreibung": "Budget, need and timing are each scored from zero to ten points, resulting in an overall score from A to D with a rationale.", "rolle": "automatisch" }, { "nr": 4, "titel": "Duplicate check and CRM entry", "beschreibung": "The workflow checks whether the lead already exists in the CRM and either creates a new entry or updates the existing one with the score and rationale.", "rolle": "automatisch" }, { "nr": 5, "titel": "Notify sales", "beschreibung": "The responsible person receives the score, rationale and a concrete recommended action directly in team chat, for example via Slack, Teams or email.", "rolle": "ergebnis" } ], "herausgeber": "Voyage Digital", "version": "2.0", "stand": "2026-07-26", "nutzen": [ { "titel": "Fast response", "text": "Promising leads reach the right salesperson within minutes, instead of sitting in an inbox for days." }, { "titel": "Consistent prioritization", "text": "Every lead is scored against the same criteria, no matter who sees the inquiry first." }, { "titel": "Focus on the promising cases", "text": "A and B leads are immediately visible, while C and D leads flow into nurturing." }, { "titel": "Clean CRM data", "text": "Every lead is filed with a score, rationale and status, not just the raw data from the form." } ], "voraussetzungen": [ { "label": "Form tool", "text": "A tool with a webhook trigger, for example Typeform or Google Forms.", "icon": "description" }, { "label": "CRM system", "text": "HubSpot, Salesforce, Pipedrive or a comparable system for storing leads.", "icon": "contacts" }, { "label": "Scoring criteria", "text": "Thresholds for budget, product fit and timing, defined before go live.", "icon": "rule" }, { "label": "LLM access and team chat", "text": "Access to a language model, for example from OpenAI, Anthropic or Google, plus a chat tool such as Slack or Teams for the sales notification.", "icon": "key" } ], "betrieb": { "testing": [ { "label": "Test lead", "text": "Submit a form with realistic data, including budget, need and timing.", "icon": "send" }, { "label": "Data mapping", "text": "Check whether all form fields arrive completely in the workflow.", "icon": "move_down" }, { "label": "Scoring and CRM", "text": "Check whether the score is plausible and the lead lands with the right status in the right stage.", "icon": "scoreboard" }, { "label": "Edge cases", "text": "Test incomplete data, a duplicate case, a very small budget and recognizable spam.", "icon": "rule" } ], "goLive": [ { "label": "Approve", "text": "Activate the workflow only once scoring, CRM entry and routing run cleanly.", "icon": "check_circle" }, { "label": "Cross check", "text": "Manually review the first roughly twenty scored leads and sharpen the thresholds.", "icon": "visibility" }, { "label": "Routing", "text": "Route leads by region, industry or budget to the right salesperson.", "icon": "alt_route" }, { "label": "Expand", "text": "Add enrichment, nurturing tracks for B and C leads, and intent analysis as needed.", "icon": "rocket_launch" } ], "haeufigeFehler": [ { "label": "Form fields not mapped", "text": "Connect every placeholder in the prompt explicitly to the matching form field name.", "icon": "link" }, { "label": "No valid JSON", "text": "Keep the instruction for pure JSON output in the prompt and add validation.", "icon": "data_object" }, { "label": "CRM required fields missing", "text": "Set email address, last name and other required fields in the form as mandatory.", "icon": "checklist" }, { "label": "Scoring feels arbitrary", "text": "Spell out the thresholds explicitly in the prompt and calibrate them against real deals.", "icon": "tune" } ] }, "arbeitsprompts": [ { "titel": "Lead scoring", "beschreibung": "Used in step 2 to assess budget, need and timing of the incoming lead and assign an A to D score with a rationale.", "prompt": "You are an assistant for lead qualification. Analyze the following lead data and assess the lead quality:\n\nLead information:\n- Name: [LEAD_NAME]\n- Company: [COMPANY_NAME]\n- Budget: [BUDGET_INFO]\n- Need/requirement: [NEED_DESCRIPTION]\n- Timing/timeframe: [TIMING_INFO]\n- Additional information: [ADDITIONAL_INFO]\n\nYour task:\nAssess the lead against the following criteria and assign an overall score.\n\n1. Budget fit (0 to 10 points): [BUDGET_CRITERIA]\n2. Need fit (0 to 10 points): [NEED_CRITERIA]\n3. Timing fit (0 to 10 points): [TIMING_CRITERIA]\n\nScoring scheme:\n- A lead (25 to 30 points): high priority, immediate contact\n- B lead (18 to 24 points): good quality, contact within 24 hours\n- C lead (10 to 17 points): medium quality, nurturing required\n- D lead (0 to 9 points): low quality, automatic follow-up\n\nRespond exclusively in the following JSON format:\n{\n \"total_score\": [total points],\n \"scoring_category\": \"[A/B/C/D]\",\n \"budget_points\": [0 to 10],\n \"need_points\": [0 to 10],\n \"timing_points\": [0 to 10],\n \"qualification_status\": \"[Qualified/Conditionally qualified/Not qualified]\",\n \"recommended_action\": \"[concrete recommended action]\",\n \"summary\": \"[2 to 3 sentences justifying the score]\"\n}" } ], "prompt": "GOAL\nBuild a workflow that automatically scores new leads from forms on budget, need and timing, assigns an A to D score with a rationale, files the lead cleanly in the CRM, and notifies the responsible salesperson with a concrete recommended action.\n\nAdapt the structure to the concepts of your automation tool, for example nodes, steps, zaps or agent actions. While doing so, preserve the trigger logic, the sequence, the parallelism and the data flow.\n\nTRIGGER\nType: form webhook, for example Typeform or Google Forms. Fires on every new submission.\nRequirement: required fields in the form for email, name, budget, need and timing, otherwise the CRM is missing required data.\n\nSTEPS\n1. Optional, enrichment: add company size, industry and tech stack through Clearbit, Apollo or a comparable service.\n2. AI step: lead scoring. Use exactly the scoring prompt below. The output is a JSON with total_score, scoring_category, the three sub scores, qualification_status, recommended_action and summary.\n3. Duplicate check: search for the lead by email address or company in the CRM. Update an existing entry with the new score, instead of creating a duplicate.\n4. CRM: create or update the lead, with score, category, rationale and status in the right stage.\n5. Output: notify the responsible salesperson, with routing by region, industry or budget. The message contains the score, rationale and recommended action. A and B leads are reported immediately and prominently, C and D leads flow into nurturing.\n\nPROMPTS (use exactly and unchanged)\nPrompt 1, lead scoring:\n\"\"\"\nYou are an assistant for lead qualification. Analyze the following lead data and assess the lead quality:\n\nLead information:\n- Name: [LEAD_NAME]\n- Company: [COMPANY_NAME]\n- Budget: [BUDGET_INFO]\n- Need/requirement: [NEED_DESCRIPTION]\n- Timing/timeframe: [TIMING_INFO]\n- Additional information: [ADDITIONAL_INFO]\n\nYour task:\nAssess the lead against the following criteria and assign an overall score.\n\n1. Budget fit (0 to 10 points): [BUDGET_CRITERIA]\n2. Need fit (0 to 10 points): [NEED_CRITERIA]\n3. Timing fit (0 to 10 points): [TIMING_CRITERIA]\n\nScoring scheme:\n- A lead (25 to 30 points): high priority, immediate contact\n- B lead (18 to 24 points): good quality, contact within 24 hours\n- C lead (10 to 17 points): medium quality, nurturing required\n- D lead (0 to 9 points): low quality, automatic follow-up\n\nRespond exclusively in the following JSON format:\n{\n \"total_score\": [total points],\n \"scoring_category\": \"[A/B/C/D]\",\n \"budget_points\": [0 to 10],\n \"need_points\": [0 to 10],\n \"timing_points\": [0 to 10],\n \"qualification_status\": \"[Qualified/Conditionally qualified/Not qualified]\",\n \"recommended_action\": \"[concrete recommended action]\",\n \"summary\": \"[2 to 3 sentences justifying the score]\"\n}\n\"\"\"\n\nDATA FLOW\nTrigger/step 1 to step 2: form fields to [LEAD_NAME], [COMPANY_NAME], [BUDGET_INFO], [NEED_DESCRIPTION], [TIMING_INFO]. Enrichment data to [ADDITIONAL_INFO].\nStep 2 to step 4: JSON fields to the CRM properties (score, category, status, rationale).\nStep 2 to step 5: scoring_category for routing and prioritization, recommended_action and summary.\n\nERROR HANDLING\nForm fields not mapped: connect every placeholder explicitly to the form field name, instead of guessing.\nAI returns no valid JSON: keep the pure JSON output instruction, validate the output and repeat the step once. After that, file the lead unscored in the CRM and send a note to sales.\nIncomplete lead data: have missing information scored as \"not provided\", instead of guessing it.\nSpam or fake entries: treat these as a D lead, or filter them out through a plausibility check on the email domain.\nDuplicate found: update the existing entry, instead of creating a new one (step 3).\nScoring feels arbitrary: fill in the three criteria placeholders concretely, calibrate them against real deals, and manually cross check the first twenty leads.\n\nPLACEHOLDER CONVENTION\nAll placeholders in square brackets are variables. Mapped dynamically are [LEAD_NAME], [COMPANY_NAME], [BUDGET_INFO], [NEED_DESCRIPTION], [TIMING_INFO] and [ADDITIONAL_INFO], as described in the data flow. Not dynamic are [BUDGET_CRITERIA], [NEED_CRITERIA] and [TIMING_CRITERIA]. These are the company specific scoring criteria that you define manually before activation. The square brackets in the JSON format are format instructions to the language model and stay unchanged. List all placeholders that require manual configuration separately at the end.\n\nSELF CHECK BEFORE COMPLETION\nCheck, before you report the workflow as finished:\n1. Are all steps connected correctly, including the duplicate check before the CRM entry?\n2. Is the scoring prompt inserted in full and unchanged, and are all form fields mapped to the placeholders?\n3. Is the JSON validated, and does the routing work (A and B immediately, C and D into nurturing)?\n4. Are all points listed that require manual configuration: the form webhook with required fields, CRM access with stage mapping, sales routing, [BUDGET_CRITERIA], [NEED_CRITERIA], [TIMING_CRITERIA] and the LLM access?", "einrichtung": { "intro": "Two routes lead to the same result. Pick the one that fits your setup.", "varianten": [ { "variante": "Builder-Prompt", "einleitung": "Suitable when you want to build the workflow in your own automation tool.", "schritte": [ "Open your workflow tool, for example n8n, Make, Zapier or Langdock.", "Create a new workflow and give it a name.", "Choose the AI-assisted build option if your tool offers one.", "Paste the builder prompt from above in full.", "Check the result against the step sequence in this document, then add your access credentials and channels." ] }, { "variante": "JSON-Import", "einleitung": "Suitable when you want to take the workflow over unchanged.", "schritte": [ "Download the JSON file from the JSON export section.", "Open the workflow area of your tool and create a new workflow.", "Give it a name and confirm.", "Open the menu on the workflow name and choose to import a JSON file.", "Upload the file, then add your own access credentials.", "Run a test before you activate the workflow." ] } ] }, "exportMeta": { "datei": "w14_lead-staffel__workflow.json", "format": "voyage-workflow/1" }, "download": { "schema": "voyage-workflow/1", "name": "Die Lead-Staffel", "beschreibung": "Bewertet jeden neuen Lead aus einem Formular automatisch nach Budget, Bedarf und Timing, legt ihn mit Score und Begründung im CRM an und benachrichtigt die zuständige Vertriebsperson mit einer konkreten Handlungsempfehlung.", "trigger": { "typ": "Formular-Trigger", "bedingung": "Ein Lead-Formular wird abgeschickt und liefert Name, Unternehmen, Budget, Bedarf und Timing als Felder name, company, budget, need und timing. Das Formular wird automatisch bereitgestellt und lässt sich per Link teilen. Beim Nachbau in n8n, Make, Zapier oder Langdock übernimmt ein Formular-Webhook, zum Beispiel von Typeform oder Google Forms, dieselbe Rolle." }, "schritte": [ { "nr": 1, "titel": "Trigger: neuer Lead", "rolle": "mensch", "aktion": "Der Formular-Trigger liefert Name, Unternehmen, Budget, Bedarf und Timing als Felder name, company, budget, need und timing an den Workflow. Schlägt der Trigger fehl, bricht der Lauf ab, es gibt keinen automatischen Retry.", "prompt_ref": null, "eingang": [], "ausgang": [ "Lead-Felder name, company, budget, need, timing" ] }, { "nr": 2, "titel": "Enrichment", "rolle": "automatisch", "aktion": "Firmengröße, Branche und Tech-Stack lassen sich optional über Clearbit, Apollo oder einen vergleichbaren Dienst ergänzen. Dieser Schritt läuft nicht als eigener technischer Schritt mit, die Verbindung führt direkt vom Formular-Trigger zum KI-Scoring. Wer die Anreicherung nutzen möchte, fügt sie als zusätzlichen Schritt zwischen Trigger und Scoring ein.", "prompt_ref": null, "eingang": [ "Lead-Felder name, company, budget, need, timing" ], "ausgang": [ "Angereicherte Zusatzinformationen (optional, kein eigener technischer Schritt)" ] }, { "nr": 3, "titel": "KI-Scoring", "rolle": "automatisch", "aktion": "Der KI-Scoring-Schritt bewertet Budget, Bedarf und Timing mit dem Lead-Scoring-Prompt. Die strukturierte Ausgabe umfasst vier Pflichtfelder: score als Auswahl A bis D, reasoning als Begründung, output als Zusammenfassung und success als Erfolgskennzeichen. Die im Prompt einzeln verlangten Teilpunkte für Budget, Bedarf und Timing sowie die Handlungsempfehlung fließen als Teil des Freitexts in reasoning beziehungsweise output ein, nicht als eigene strukturierte Felder. Schlägt der Schritt fehl, bricht der Lauf ab.", "prompt_ref": "arbeitsschritt-1", "eingang": [ "Lead-Felder name, company, budget, need, timing", "Angereicherte Zusatzinformationen (optional)" ], "ausgang": [ "Strukturierte Ausgabe: score (A bis D), reasoning, output, success" ] }, { "nr": 4, "titel": "Duplikat-Check und CRM-Eintrag", "rolle": "automatisch", "aktion": "Der CRM-Schritt legt den Lead als Salesforce-Objekt an: company aus dem Formularfeld company, lastName aus dem Formularfeld name, additionalProperties bündelt Budget, Bedarf, Timing sowie Score und Begründung als zusätzliche Lead-Felder. Der Status wird aus der Scoring-Kategorie abgeleitet: A wird zu Qualified, B und C werden beide zu Working, D wird zu New. Ein eigener Suchschritt vor dem Anlegen, der auf Duplikate prüft, ist nicht Teil dieses Schritts, das Anlegen folgt direkt auf das Scoring. Schlägt der Schritt fehl, bricht der Lauf ab.", "prompt_ref": null, "eingang": [ "Lead-Felder name, company, budget, need, timing", "Strukturierte Ausgabe: score, reasoning" ], "ausgang": [ "CRM-Eintrag mit Status Qualified, Working oder New, Score und Begründung in additionalProperties" ] }, { "nr": 5, "titel": "Vertrieb benachrichtigen", "rolle": "ergebnis", "aktion": "Der Benachrichtigungs-Schritt sendet eine Nachricht mit Leaddetails, Score und Begründung in einen festen Kanal, standardmäßig #sales. Eine Verzweigung nach Region, Branche oder Budget ist nicht Teil dieses Schritts, alle Leads laufen in denselben Kanal. Die Nachricht bezieht ihre Angaben direkt aus dem Formular und dem Scoring, nicht aus dem angelegten CRM-Eintrag. Wer Routing an unterschiedliche Vertriebspersonen oder einen CRM-Verweis in der Nachricht braucht, ergänzt das als zusätzlichen Schritt. Schlägt die Benachrichtigung fehl, bricht der Lauf ab.", "prompt_ref": null, "eingang": [ "Lead-Felder name, company, budget, need, timing", "Strukturierte Ausgabe: score, reasoning", "CRM-Eintrag (nur als Ausführungsreihenfolge, nicht als Dateninhalt)" ], "ausgang": [ "Nachricht im Kanal #sales mit Score, Begründung und Zusammenfassung" ] } ], "prompts": { "arbeitsschritt-1": { "titel": "Lead-Scoring", "text": "Sie sind Assistent für Lead-Qualifizierung. Analysieren Sie die folgenden Lead-Daten und bewerten Sie die Lead-Qualität:\n\nLead-Informationen:\n- Name: [LEAD_NAME]\n- Unternehmen: [COMPANY_NAME]\n- Budget: [BUDGET_INFO]\n- Bedarf/Anforderung: [NEED_DESCRIPTION]\n- Timing/Zeitrahmen: [TIMING_INFO]\n- Zusätzliche Informationen: [ADDITIONAL_INFO]\n\nIhre Aufgabe:\nBewerten Sie den Lead anhand folgender Kriterien und vergeben Sie ein Gesamtscoring.\n\n1. Budget-Fit (0 bis 10 Punkte): [BUDGET_CRITERIA]\n2. Bedarfs-Fit (0 bis 10 Punkte): [NEED_CRITERIA]\n3. Timing-Fit (0 bis 10 Punkte): [TIMING_CRITERIA]\n\nScoring-Schema:\n- A-Lead (25 bis 30 Punkte): hohe Priorität, sofortiger Kontakt\n- B-Lead (18 bis 24 Punkte): gute Qualität, Kontakt innerhalb 24 Stunden\n- C-Lead (10 bis 17 Punkte): mittlere Qualität, Nurturing erforderlich\n- D-Lead (0 bis 9 Punkte): niedrige Qualität, automatisches Follow-up\n\nAntworten Sie ausschließlich im folgenden JSON-Format:\n{\n \"score_gesamt\": [Gesamtpunktzahl],\n \"scoring_kategorie\": \"[A/B/C/D]\",\n \"budget_punkte\": [0 bis 10],\n \"bedarf_punkte\": [0 bis 10],\n \"timing_punkte\": [0 bis 10],\n \"qualifizierung_status\": \"[Qualifiziert/Bedingt qualifiziert/Nicht qualifiziert]\",\n \"empfohlene_aktion\": \"[konkrete Handlungsempfehlung]\",\n \"zusammenfassung\": \"[2 bis 3 Sätze Begründung des Scorings]\"\n}" } }, "datenfluss": [ { "von": 1, "nach": 2, "nutzlast": "Lead-Felder name, company, budget, need, timing, sofern die optionale Anreicherung genutzt wird" }, { "von": 1, "nach": 3, "nutzlast": "Lead-Felder name, company, budget, need, timing, direkt vom Trigger ohne Zwischenschritt" }, { "von": 2, "nach": 3, "nutzlast": "Angereicherte Zusatzinformationen (Firmengröße, Branche, Tech-Stack), sofern der optionale Enrichment-Schritt ergänzt wird" }, { "von": 3, "nach": 4, "nutzlast": "Strukturierte Ausgabe des Scoring-Schritts: score und reasoning" }, { "von": 1, "nach": 5, "nutzlast": "Lead-Felder name, company, budget, need, timing fließen direkt in die Benachrichtigung ein" }, { "von": 3, "nach": 5, "nutzlast": "score und reasoning aus dem Scoring-Schritt fließen direkt in die Benachrichtigung ein" }, { "von": 4, "nach": 5, "nutzlast": "Nur die Erfolgsmeldung des CRM-Schritts als Ausführungsreihenfolge. Der CRM-Eintrag selbst, etwa ein Link oder eine ID, wird nicht in die Benachrichtigung übernommen" } ], "voraussetzungen": [ "Formular-Tool mit Webhook-Trigger, zum Beispiel Typeform oder Google Forms", "CRM-System für die Lead-Ablage, zum Beispiel HubSpot, Salesforce oder Pipedrive", "Vorab definierte Scoring-Kriterien und Schwellenwerte für Budget, Produkt-Fit und Timing", "LLM-Zugang per API-Key (OpenAI, Claude oder Gemini)", "Team-Chat für die Sales-Benachrichtigung, zum Beispiel Slack oder Teams" ], "fehlerbehandlung": [ { "fall": "Formular-Felder nicht gemappt", "massnahme": "Jeden Platzhalter im Prompt explizit mit dem Feldnamen des Formulars verbinden, statt zu raten." }, { "fall": "KI liefert kein valides JSON", "massnahme": "Anweisung zur reinen JSON-Ausgabe beibehalten, Ausgabe validieren, Schritt einmal wiederholen. Lead danach unbewertet ins CRM legen und Hinweis an Sales senden." }, { "fall": "Scoring-Ausgabeschema weicht vom Prompt-Format ab", "massnahme": "Der Scoring-Schritt liefert nur score, reasoning, output und success als strukturierte Felder, der Prompt verlangt zusätzlich Einzelpunkte für Budget, Bedarf und Timing. Beim Nachbau in einem Tool mit striktem strukturiertem Output das Schema entsprechend schlank halten oder die Einzelpunkte als zusätzliche Felder ergänzen." }, { "fall": "Unvollständige Lead-Daten", "massnahme": "Fehlende Angaben mit nicht angegeben bewerten lassen, statt sie zu raten." }, { "fall": "Spam- oder Fake-Einträge", "massnahme": "Als D-Lead behandeln oder über eine Plausibilitätsprüfung der E-Mail-Domain aussortieren." }, { "fall": "Duplikat gefunden", "massnahme": "Der CRM-Schritt sucht nicht selbst nach bestehenden Einträgen. Vor dem Anlegen einen eigenen Suchschritt per E-Mail-Adresse oder Firma ergänzen, oder eine native Upsert-Funktion des Ziel-CRM nutzen, damit kein Duplikat entsteht." }, { "fall": "Scoring wirkt willkürlich", "massnahme": "Die drei Kriterien-Platzhalter konkret befüllen, mit echten Deals kalibrieren und die ersten zwanzig Leads manuell gegenprüfen." }, { "fall": "Kein Fallback bei technischem Fehler", "massnahme": "Formular-Trigger, Scoring, CRM-Eintrag und Benachrichtigung sind auf Abbruch bei Fehlschlag eingestellt. Schlägt ein Schritt fehl, stoppt der gesamte Lauf ohne Retry. Monitoring oder eine manuelle Nachbearbeitung fehlgeschlagener Läufe separat einrichten." }, { "fall": "Sales-Benachrichtigung ohne Bezug zum CRM-Eintrag", "massnahme": "Die Nachricht bezieht ihre Angaben direkt aus dem Formular und dem Scoring, nicht aus dem angelegten CRM-Eintrag. Ein CRM-Link in der Benachrichtigung erfordert ein zusätzliches Feld aus der Antwort des CRM-Schritts." }, { "fall": "Kanal oder Routing nicht angepasst", "massnahme": "Der Kanal ist standardmäßig fest auf #sales gesetzt, eine Verzweigung nach Region, Branche oder Budget ist nicht vorgesehen. Kanal-ID vor dem Go-Live anpassen und bei Bedarf eine Verzweigung für unterschiedliche Vertriebspersonen ergänzen." } ], "platzhalter": [ { "name": "leadForm.output.name", "quelle": "Feld Name des Leads aus dem Formular-Trigger" }, { "name": "leadForm.output.company", "quelle": "Feld Unternehmen aus dem Formular-Trigger" }, { "name": "leadForm.output.budget", "quelle": "Feld Budget aus dem Formular-Trigger" }, { "name": "leadForm.output.need", "quelle": "Feld Bedarf aus dem Formular-Trigger" }, { "name": "leadForm.output.timing", "quelle": "Feld Timing aus dem Formular-Trigger" }, { "name": "score", "quelle": "Score-Feld (A bis D) aus der strukturierten Ausgabe des Scoring-Schritts" }, { "name": "reasoning", "quelle": "Begründungsfeld aus der strukturierten Ausgabe des Scoring-Schritts" }, { "name": "output", "quelle": "Zusammenfassungsfeld aus der strukturierten Ausgabe des Scoring-Schritts" }, { "name": "success", "quelle": "Erfolgskennzeichen aus der strukturierten Ausgabe des Scoring-Schritts" }, { "name": "channelId", "quelle": "Kanal-Kennung im Benachrichtigungs-Schritt, standardmäßig #sales" }, { "name": "status", "quelle": "CRM-Statusfeld, aus der Scoring-Kategorie abgeleitet: A auf Qualified, B und C auf Working, D auf New" }, { "name": "company", "quelle": "Feld im CRM-Schritt, gesetzt aus dem Formularfeld company" }, { "name": "lastName", "quelle": "Feld im CRM-Schritt, gesetzt aus dem Formularfeld name" }, { "name": "additionalProperties", "quelle": "Sammelfeld im CRM-Schritt für Budget, Bedarf, Timing, Score und Begründung als zusätzliche Lead-Eigenschaften" }, { "name": "LEAD_NAME", "quelle": "Platzhalter im Scoring-Prompt, gemappt auf das Formularfeld name" }, { "name": "COMPANY_NAME", "quelle": "Platzhalter im Scoring-Prompt, gemappt auf das Formularfeld company" }, { "name": "BUDGET_INFO", "quelle": "Platzhalter im Scoring-Prompt, gemappt auf das Formularfeld budget" }, { "name": "NEED_DESCRIPTION", "quelle": "Platzhalter im Scoring-Prompt, gemappt auf das Formularfeld need" }, { "name": "TIMING_INFO", "quelle": "Platzhalter im Scoring-Prompt, gemappt auf das Formularfeld timing" }, { "name": "ADDITIONAL_INFO", "quelle": "Platzhalter im Scoring-Prompt für das Ergebnis des optionalen Enrichments" }, { "name": "BUDGET_CRITERIA", "quelle": "Firmenspezifisches Budget-Kriterium, vor Aktivierung manuell definiert" }, { "name": "NEED_CRITERIA", "quelle": "Firmenspezifisches Bedarfs-Kriterium, vor Aktivierung manuell definiert" }, { "name": "TIMING_CRITERIA", "quelle": "Firmenspezifisches Timing-Kriterium, vor Aktivierung manuell definiert" } ], "herausgeber": "Voyage Digital", "version": "2.0", "stand": "2026-07-26" }, "itemIcon": "user-plus", "recommended": [ { "slug": "pipeline-schiene", "category": "workflow", "name": "The Pipeline Pulse", "teaser": "A weekly report that reads your open pipeline from the CRM and flags risks, opportunities and stagnating deals for the sales team.", "domaene": "Vertrieb & Outreach", "itemIcon": "git-branch" }, { "slug": "kundentermin-protokoll", "category": "skill", "name": "The Client Meeting Protocol", "teaser": "Turns notes or a transcript from a client meeting into a structured protocol with a BANT or MEDDIC opportunity analysis, action items, and a follow-up email draft.", "domaene": "Vertrieb & Outreach", "itemIcon": "notebook-pen" }, { "slug": "pipeline-protokoll", "category": "skill", "name": "The Pipeline Protocol", "teaser": "Systematically checks your CRM pipeline, flags deals that need action, and delivers a compact report with metrics and prioritized next steps.", "domaene": "Vertrieb & Outreach", "itemIcon": "git-branch" }, { "slug": "qbr-dossier", "category": "skill", "name": "The QBR Dossier", "teaser": "Creates a structured Quarterly Business Review for existing customers, from health score to a prioritized roadmap for the next quarter.", "domaene": "Vertrieb & Outreach", "itemIcon": "pie-chart" }, { "slug": "scoring-schema", "category": "skill", "name": "The Scoring Framework", "teaser": "Scores incoming leads against your ICP criteria, assigns a traceable score with a confidence rating, prioritizes them into Hot, Warm and Disqualified, and delivers first-outreach drafts for the top leads.", "domaene": "Vertrieb & Outreach", "itemIcon": "star" }, { "slug": "angebots-schiene", "category": "workflow", "name": "The Quote Pipeline", "teaser": "A workflow that automatically turns an incoming quote request into a reviewed quote draft, from requirements extraction through to sales approval.", "domaene": "Vertrieb & Outreach", "itemIcon": "file-badge" }, { "slug": "termin-briefing-staffel", "category": "workflow", "name": "The Meeting Briefing Relay", "teaser": "A workflow that automatically prepares a structured briefing before every customer meeting by combining calendar details, CRM history and fresh web research.", "domaene": "Vertrieb & Outreach", "itemIcon": "calendar-clock" }, { "slug": "vertriebsantwort-schiene", "category": "workflow", "name": "The Sales Response Pipeline", "teaser": "Automatically drafts a personalized sales reply from CRM context for incoming lead emails and notifies the responsible sales rep for review before it is sent.", "domaene": "Vertrieb & Outreach", "itemIcon": "send" }, { "slug": "angebots-pruefer", "category": "assistent", "name": "The Quote Reviewer", "teaser": "Systematically checks quotes before they go out for completeness, arithmetic consistency and pricing logic, and returns a clear approval recommendation.", "domaene": "Vertrieb & Outreach", "itemIcon": "file-badge" }, { "slug": "call-analyst", "category": "assistent", "name": "The Call Analyst", "teaser": "Turns call notes or a sales call transcript into a CRM-ready follow-up document with needs analysis, BANT assessment and a scheduled follow-up plan.", "domaene": "Vertrieb & Outreach", "itemIcon": "phone-call" }, { "slug": "lead-qualifizierer", "category": "assistent", "name": "The Lead Qualifier", "teaser": "Scores incoming customer emails for fit and urgency, attaches a confidence rating to every assessment, and proposes concrete next steps with clear ownership.", "domaene": "Vertrieb & Outreach", "itemIcon": "user-plus" }, { "slug": "einwand-drehbuch", "category": "skill", "name": "The Objection Playbook", "teaser": "Classifies a customer objection psychologically and delivers three ready-to-use response strategies with concrete phrasing instead of a generic stock answer.", "domaene": "Vertrieb & Outreach", "itemIcon": "shield-question" }, { "slug": "11x", "category": "tool", "name": "11x", "teaser": "11x is a vertically integrated GTM platform offering autonomous AI sales agents for outbound sales: lead research, multi-channel sequencing, voice calls and appointment booking in one tool.", "domaene": "Vertrieb & Outreach", "logoFile": "11x.png", "logoEinzug": 0.78 }, { "slug": "artisan", "category": "tool", "name": "Artisan", "teaser": "Artisan is an AI outbound sales tool centered on Ava, an autonomous agent that researches leads, personalizes email sequences and manages follow-ups for B2B SaaS teams.", "domaene": "Vertrieb & Outreach", "logoFile": "artisan.png", "logoEinzug": 0.78 }, { "slug": "clay", "category": "tool", "name": "Clay", "teaser": "A spreadsheet-based platform that combines over 100 data sources and an AI research agent for lead enrichment and personalized outbound.", "domaene": "Vertrieb & Outreach", "logoFile": "clay.png", "logoEinzug": 1 }, { "slug": "gong", "category": "tool", "name": "Gong", "teaser": "Gong is a revenue intelligence platform that records and analyzes sales calls with AI to power coaching, deal insights, and forecasting for enterprise sales teams.", "domaene": "Vertrieb & Outreach", "logoFile": "gong.svg", "logoEinzug": 0.78 }, { "slug": "hubspot", "category": "tool", "name": "HubSpot", "teaser": "Cloud based customer platform that bundles marketing, sales, customer service, content marketing, data management, and billing around a shared CRM database, with AI agents under the Breeze product brand.", "domaene": "Vertrieb & Outreach", "logoFile": "hubspot.png", "logoEinzug": 0.78 }, { "slug": "instantly", "category": "tool", "name": "Instantly", "teaser": "Sales platform for automated cold email outreach with built-in deliverability infrastructure, a B2B lead database, and AI sequence writing.", "domaene": "Vertrieb & Outreach", "logoFile": "instantly.svg", "logoEinzug": 1 }, { "slug": "pipedrive", "category": "tool", "name": "Pipedrive", "teaser": "Visual sales-pipeline CRM with AI-assisted deal prioritization, workflow automation, and an optional projects module for post-sale delivery.", "domaene": "Vertrieb & Outreach", "logoFile": "pipedrive.png", "logoEinzug": 1 }, { "slug": "salesforce", "category": "tool", "name": "Salesforce", "teaser": "Cloud CRM combining connected building blocks for sales, commerce, and customer service, extended with the Agentforce 360 agent layer for industry-specific AI use cases such as appointment scheduling or case management.", "domaene": "Vertrieb & Outreach", "logoFile": "salesforce.svg", "logoEinzug": 1 } ] }