Writing “create a sales agent”
Why it fails
It leaves behavior, data, or ownership ambiguous.
Correct it
Use the complete brief so the draft begins with the right audience, result, facts, outputs, and boundaries.
Lesson 2 of 8
Create a saved Draft from your plan
Use the AI Agents creation surface, give HeyRik a complete brief, review optional AI enhancement, generate the agent, and confirm the saved Draft before editing it.
In this lessonOutcome
You will create one saved agent, confirm that it remains in Draft, and open its builder. This lesson stops before detailed configuration so generation and review remain separate decisions.
What done looks like
You can demonstrate the lesson result in the dashboard and complete its practical checklist before continuing.
01
Open AI Agents
Use the workspace that will own this agent and its call data.
Click AI Agents in the dashboard navigation
The page shows a description field, Enhance with AI, Start from scratch, Generate, optional templates, and existing agents below.
Stay on the Create an assistant area
Do not edit an existing production agent for this first exercise.
Confirm you have the planning brief
You need the job, audience, success, languages, outputs, source boundary, and human fallback from Lesson 1.
02
Enter a complete description
The creation field is a brief for generation, not the final instruction document. Include the decisions that materially shape the draft.
Paste into the Create an assistant field
Create an inbound property-enquiry assistant for Acme Properties.
It should speak English and Telugu in a warm, concise style and ask one
question at a time. Its only job is to capture and confirm property type,
budget, preferred location, buying timeline, and permission for a human
property expert to follow up.
It must use approved attached knowledge or a configured tool for projects,
prices, amenities, and availability. It must never invent those facts, promise
investment returns, collect passwords or payment credentials, or claim that a
follow-up was booked when no action confirmed it.
If the caller asks for a person or needs unsupported information, transfer
when enabled; otherwise offer a human follow-up. It must handle corrections,
refusal, silence, wrong person, and do-not-contact requests safely.Optional: Enhance with AI
Click the wand button labeled Enhance with AI only if you want HeyRik to expand the brief in the field. Read the expanded text before generating. Enhancement changes the brief; it does not approve it.
03
Generate the saved Draft
The dashboard saves a usable Draft first, then enriches it. Wait for the preparation state to finish before opening it.
Click Generate
The description clears and a Preparing card appears in the agent list while the background work runs.
Wait for preparation to finish
Do not open or duplicate the agent while the card says Preparing.
Open the generated agent card
The builder opens on Assistant Details.
Confirm the status is Draft
The header Live control must remain off while you review and test.
Start from scratch is a different path
Start from scratch creates a blank saved Draft and opens the builder. Use it when you want to write every field manually. It does not run the AI generation described in this lesson.
04
What a usable generated Draft should contain
Exact wording and selections may differ. Review the structure and product fields, not whether generation copied this example verbatim.
Generated Draft review
expectedStatusDraft / Live control is off
NameA recognizable property-enquiry agent name
LanguagesEnglish and Telugu
VoiceA selected voice that supports the primary language
GreetingIdentifies Acme Properties without unresolved placeholders
InstructionsIdentity, conversation sequence, fact boundary, guardrails, and closing
Inputscompany_name and optional customer_name with defaults
Outputsproperty_type, budget, location, timeline, follow_up_consent
Acceptable generated greeting
Hello, thank you for calling Acme Properties. How may I help with your property enquiry?05
Verify that the Draft exists safely
Do not fix detailed content yet. Confirm persistence, identity, and readiness for the configuration lesson.
06
Common creation mistakes
Generation is fast, which makes it easy to mistake visible output for validated behavior.
Pressing Enhance and Generate without reading
Why it fails
It leaves behavior, data, or ownership ambiguous.
Correct it
Treat enhanced text as a proposal; remove assumptions before generation.
Generating duplicates while Preparing
Why it fails
It leaves behavior, data, or ownership ambiguous.
Correct it
Wait for the first job to finish and open its resulting card.
Switching Live immediately
Why it fails
It leaves behavior, data, or ownership ambiguous.
Correct it
Keep Draft until all builder areas and difficult test scenarios pass.
Assuming AI connected tools or knowledge
Why it fails
It leaves behavior, data, or ownership ambiguous.
Correct it
Generation can describe behavior; you must attach sources and configure actions separately.
Using a production agent as the exercise
Why it fails
It leaves behavior, data, or ownership ambiguous.
Correct it
Create a separate Draft so testing cannot alter active customer behavior.
API equivalent
API generation and dashboard generation are not the same transaction
POST /agents/generate → POST /agentsOpen reference POST /agents/generate returns a draft configuration and saves nothing. Review the returned name, greeting, languages, prompt_sections, input variables, and extracted variables; then call POST /agents to create it. By contrast, the dashboard creates a saved Draft before enrichment so a failed enrichment does not discard the agent.