Let AI generate your agent from natural language descriptions.
Don’t want to start from scratch? Describe what you need in plain English, and our AI will generate a complete agent — whether Single Prompt or Conversational Flow.
[IMAGE: Full Create with AI page showing configuration panel on left and prompts on right]
Each prompt shapes a different aspect of your agent. All require minimum 50 characters.
1. Role & Objective
2. Conversational Flow
3. Dos, Don'ts & Fallbacks
4. End Conditions
[IMAGE: First prompt field highlighted]
What it defines: Who the agent is and what it’s trying to accomplish.Label: “Provide the role & objective of your agent”Good example:
Copy
You are a friendly and confident customer support agent for a fintech platform. Your goal is to quickly understand the user's issue, respond with empathy, and provide clear, step-by-step solutions that make them feel heard and supported.Maintain a calm and reassuring tone throughout the conversation, ensuring that the user feels confident in your assistance. Only mark the issue as resolved once the user has confirmed they are fully satisfied with the outcome.
Tips:
Be specific about personality (friendly, professional, casual)
State the primary goal clearly
Mention the industry/context
[IMAGE: Second prompt field highlighted]
What it defines: The step-by-step conversation structure.Label: “Provide conversational flow that the agent should follow”Good example:
Copy
As a NorthLoop Support agent, greet customers warmly and confirm they are NorthLoop customers. Ask one focused question to identify if the issue is billing or connectivity.For connectivity, get the service address; for billing, collect the email or phone number. Verify the account and, if needed, try an alternate identifier.Diagnose the issue: check for outages first, then guide through reboot or cabling steps. If the outage lasted over four hours, issue a refund. If local fixes fail, schedule a technician.Confirm resolution and next steps, invite questions, and close politely.
Tips:
Describe the conversation as a journey
Include decision points (if X, then Y)
Cover the main paths callers will take
[IMAGE: Third prompt field highlighted]
What it defines: Behavioral guardrails and edge case handling.Label: “Set your agent’s dos, don’ts, and fallback behaviours — especially for edge cases or sensitive situations”Good example:
Copy
Your agent should always remain calm, polite, and solution-oriented.DO:- Listen actively and show empathy- Provide clear next steps at every stage- Confirm understanding before proceeding- Escalate politely when neededDON'T:- Make assumptions about the issue- Overpromise on timelines or resolutions- Share unverified information- Rush the customerFALLBACKS:- Account lookup failures → Offer alternate verification methods- Incomplete verification → Politely re-request information- Unclear issues → Ask clarifying questions, don't guess- System limitations → Acknowledge honestly and offer alternativesAlways prioritize accuracy, empathy, and clarity over speed.
What it defines: When and how the conversation should end.Label: “Specify the conditions under which the call should end”Good example:
Copy
End the call when:1. Issue fully resolved and customer confirms satisfaction - Thank them for calling - Offer additional help before closing2. Customer requests to end the call - Acknowledge and close gracefully - Offer callback if issue unresolved3. Successful transfer to human agent - Confirm transfer is happening - Brief goodbye4. Customer becomes unresponsive - After 3 attempts to re-engage - Leave callback information5. Issue outside scope - Acknowledge limitation - Provide alternative resources - End with helpful next steps
Tips:
Cover all the ways a call might end
Include what to say in each scenario
Don’t forget edge cases (no response, wrong department)
Since there’s no visual flow, the prompt needs to cover everything the agent should know and how it should behave.Include:
Detailed role description
All topics it should handle
Communication style
Edge case handling
Be comprehensive in conversation flow
Even without visual nodes, describe the typical conversation arc:
Copy
Start with a warm greeting. Ask how you can help. Listen to the issue. Acknowledge and confirm understanding.Provide the solution or collect needed information.Confirm resolution. Offer additional help. Close warmly.
Define flexibility
Single Prompt agents should handle topic jumps gracefully:
Copy
If the customer changes topics, acknowledge the shift and adapt. Don't force them back to previous subjects.
After greeting, ask if calling about billing or technical.BILLING PATH:- Verify account- Ask about specific charge- Explain or process refundTECHNICAL PATH:- Identify product- Troubleshoot steps- Schedule technician if needed
Specify data collection
List what information must be gathered and when:
Copy
Must collect before qualifying:1. Company name2. Company size (employees)3. Current solution4. Budget range5. Decision timeline
Define all endings
Every path needs a conclusion:
Copy
End points:- Qualified lead → Transfer to sales with context- Not qualified → Send resources, end call- Requested callback → Schedule and confirm- Angry customer → Escalate to manager