Skip to main content

Understanding Context Prompts in Kakiyo

This article provides an in-depth explanation of context prompts in Kakiyo, and best practices for crafting effective context instructions.

Ilan Asseo avatar
Written by Ilan Asseo
Updated over a month ago

What is a Context Prompt?

In Kakiyo, the Context Prompt is the set of instructions that governs the AI's overall behavior throughout an entire conversation with a prospect. Unlike the First Message prompt (which focuses only on the initial outreach message), the Context Prompt shapes how the AI:

  • Understands its role and purpose

  • Responds to various prospect reactions

  • Maintains conversation flow

  • Handles objections and questions

  • Works toward conversion goals

  • Applies your preferred communication style

Think of the Context Prompt as the comprehensive playbook that guides the AI through every possible scenario in a LinkedIn conversation.

Why Context Prompts Matter

A well-crafted Context Prompt is crucial because it:

  1. Creates Consistency: Ensures all prospect conversations follow your strategic approach

  2. Improves Conversion: Guides the AI to effectively move prospects toward your goals

  3. Maintains Brand Voice: Keeps communication aligned with your company's tone and style

  4. Handles Edge Cases: Prepares the AI for unusual or challenging prospect responses

  5. Reduces Risk: Prevents inappropriate or off-brand messaging


Key Sections of an Effective Context Prompt

While you have flexibility in how you structure your Context Prompt, most effective prompts include these key sections:

1. Role Definition

This section establishes who the AI is representing in the conversation:

# Role 

[Define who the AI is representing, their position, and their relationship to the prospect]

The Role section should:

  • Establish the AI's identity (using the {{agentName}} variable if appropriate)

  • Define the company or organization being represented (using the {{companyName}} variable if appropriate)

  • Clarify the professional relationship to the prospect (consultant, representative, etc.)

  • Set the overall tone (helpful, authoritative, friendly, consultative, etc.)

Important: You do not need to manually fill in {{agentName}} or {{companyName}} — the system will automatically insert the correct values during runtime.

2. Mission Statement

This section defines the purpose and goals of the conversation:

# Mission 

[Define what the AI is trying to accomplish through the conversation]

An effective Mission section:

  • States the primary goal clearly (booking meetings, sharing content, etc.)

  • Provides alternative paths for different prospect scenarios

  • Establishes priorities (what matters most in the conversation)

  • Defines success criteria (how to know when goals are achieved)

3. Conversation Instructions

This section provides specific guidance on how to conduct the conversation:

# Instructions 

[List specific guidelines for how the AI should communicate]


Effective Instructions typically cover:

  • Message length (e.g., "Keep messages under 40 words")

  • Language preferences (formal vs. casual, technical vs. simple)

  • Question strategy (when and how to ask questions)

  • Personalization approach (how to use prospect information)

  • Content priorities (what to emphasize or avoid)

  • Conversational flow (how to develop the dialogue)

4. Special Cases Handling

This section prepares the AI for specific scenarios that might arise:

# Special Cases 

[Provide guidelines for handling specific situations]

Common special cases to address:

  • How to handle objections ("I'm not interested")

  • Responding to pricing questions

  • Managing requests for information

  • Dealing with unresponsive prospects

  • Handling negative or inappropriate responses

5. Product and Prospect Information

Make sure to include the required variables somewhere in your Context Prompt:

  • {{productDescription}} - Contains details about your offering

  • {{prospectDescription}} - Contains information about the prospect

You can place these in a dedicated section or integrate them into other sections as appropriate.


Common Context Prompt Mistakes to Avoid

  1. Overly Sales-Focused: Instructing the AI to be too pushy or sales-oriented

  2. Conflicting Instructions: Giving contradictory guidelines that confuse the AI

  3. Insufficient Guidance: Being too vague about how to handle specific situations

  4. Unrealistic Expectations: Setting goals that can't be achieved in a LinkedIn conversation

  5. Ignoring Prospect Experience: Focusing only on your goals without considering the prospect's perspective

  6. Too Rigid: Not allowing the AI enough flexibility to adapt to different scenarios

  7. Too Complex: Creating overly complicated instructions that dilute the core message

Testing and Refining Your Context Prompt

Your Context Prompt should evolve based on performance:

  1. Create an initial version based on your campaign goals

  2. Test extensively with various prospect scenarios

  3. Identify areas where the AI struggles or misunderstands

  4. Refine those specific sections

  5. Test again with the updated Context Prompt

  6. Continue this iterative process based on real campaign results

Final Tips for Context Prompt Success

  • Be Clear and Direct: The AI performs best with straightforward instructions

  • Simple Instructions: Keeping your instructions simple helps the AI respond more accurately and stay aligned with your goals.

  • Prioritize Guidelines: Make it clear which rules are most important

  • Consider User Experience: Create prompts that lead to positive prospect experiences

  • Balance Structure and Flexibility: Give enough guidance without micromanaging

  • Evolve Continuously: Treat your Context Prompt as a living document that improves over time

Remember that the Context Prompt works in tandem with your First Message Prompt, which focuses specifically on crafting the initial outreach message. For guidance on creating effective first messages, see our Crafting Effective First Messages article.

Did this answer your question?