Single-Prompt Agents
Single-Prompt Agents

A Single-Prompt agent uses one prompt to control all behaviors and actions. Use it when one instruction set can cover the full conversation without node-by-node branching, for example a quick test of a use case, a small project, or iteration on tone before you graduate to Flow Designer.
Prompting is the process of giving your agent clear instructions on how to interact. Think of it as writing an improv script: instead of fixed lines, you provide guidelines and context that help the agent generate natural, helpful responses. Good prompts ensure the agent understands business and user needs, responds clearly, and guides conversations toward the desired outcome.
Every new agent comes with a base prompt to get you started. Refine it to match your tone and goals before going live.
Prompt structure
A strong Synthflow prompt follows a consistent structure. Each component below sharpens the agent’s output for a specific stage of the conversation.
Background information
- Company overview: what the company does, its approach, and its market standing.
- Target audience: who the agent is talking to, including their characteristics and expectations.
- Value proposition: the direct benefit the audience receives, used as a hook to keep the conversation engaged.
Agent profile
- Name: personalizes the agent so interactions feel less automated.
- Role: defines the agent’s function in the customer journey.
- Goal: the specific outcome the conversation should drive toward, such as qualifying a lead, scheduling a meeting, or providing information.
Example background and profile block:
Objection handling
Objection handling prepares the agent for hurdles like budget concerns, timing hesitations, or competitor mentions. Spell out each objection you expect, the sentiment behind it, and the response that keeps the conversation on track toward the goal.
Conversation script
The script is a structured guide that outlines the conversation flow: questions to ask, points to cover, and responses to common scenarios. Treat it as a foundation. The agent will adapt as needed, but the script keeps every conversation consistent and complete.
Example script:
Best practices
Be clear and specific
Ambiguous instructions lead to unpredictable results. Define the agent’s role, tone, and objective explicitly.
- Good: “Greet customers warmly, introduce yourself as a real estate agent, and ask if they’re looking to buy or rent.”
- Bad: “Talk to the customer about real estate.”
Provide context
The agent performs better when it understands who it’s speaking for and who it’s speaking to. Always include:
- Company background (what the business does).
- Target audience (who the agent is helping).
- Goals (what the conversation should achieve).
Guide the conversation flow
AI conversations should feel natural, but they also need structure. A strong prompt outlines:
- Key questions to ask, for example “What’s your budget range?”.
- Information to collect, such as location, preferences, and contact details.
- How to respond in common scenarios, like when a customer is not ready to buy.
Anticipate objections
Customers may raise budget limits, timing concerns, or hesitation to switch providers. Prepare scripted responses so the agent reframes confidently. For example: “If the customer mentions price concerns, explain available financing options.”
Keep it concise
Excessive detail confuses the agent. Use short, clear instructions instead of long paragraphs.
- Good: “If the customer is hesitant about booking, briefly explain the process and its benefits.”
- Bad: “In cases where a customer is hesitant about scheduling a consultation due to uncertainty about the process, offer reassurance by explaining the steps and emphasizing how easy and beneficial the experience will be.”
Test and iterate
The agent will not always get it right on the first try. After launching:
- Review interactions and identify areas for improvement.
- Adjust the prompt to refine responses.
- Keep the prompt updated as your needs evolve.
Prompting is just providing directions. The quality of the outcome depends on the quality of the direction.
FAQ
When should I use a Single-Prompt agent instead of Flow Designer?
Use Single-Prompt for quick prototypes, small projects, or when one instruction set can cover the full conversation. Move to Flow Designer when you need explicit branching, reusable logic, multi-step routing, or predictable paths through complex flows.
How long should my prompt be?
Short and structured beats long and exhaustive. Aim for clear, explicit instructions broken into the structure above. If sections start running into long paragraphs, trim them or break the conversation into Flow Designer steps instead.
Can I reference variables and call data inside a single prompt?
Yes. The prompt editor includes tabs for Pre-call variables, Action results, and Actions so you can inject dynamic values into the prompt, for example a caller’s name or the result of a custom action. See the agent editor walkthrough for details.