Who is calling?
People who made an inbound property enquiry and may be comparing options.
Avoid: Anyone who needs help.Lesson 1 of 8
Plan one job your agent can finish well
Turn a broad idea into a precise call job with one audience, one successful outcome, approved facts, required inputs and outputs, and a safe human fallback.
In this lessonOutcome
You will leave this lesson with a one-page brief for an inbound property-enquiry agent. It will say exactly who calls, what the agent must achieve, which facts it may use, what information goes into and comes out of the call, and when a person takes over.
What done looks like
You can demonstrate the lesson result in the dashboard and complete its practical checklist before continuing.
01
Open the creation surface—but do not generate yet
Use the product to frame the decision, then finish the brief before asking AI to draft the agent.
Open the HeyRik dashboard
Sign in to the workspace that will own the agent, knowledge, phone number, and call records.
Click AI Agents
This opens the Create an assistant surface and your existing agent list.
Find the large description field
Do not press Generate yet. First write the seven decisions below in a separate note.
Why planning happens before prompting
AI can organize a job you understand. It cannot decide which promises your business may make, which data it is allowed to collect, or which calls require a human.
02
Answer seven planning questions
Use concrete answers. Each answer becomes either a builder setting, an instruction, a knowledge source, a variable, or a test.
What is the one job?
Capture and confirm property type, budget, location, timeline, and permission for human follow-up.
Avoid: Sell properties and provide support.What proves success?
The caller confirms the four requirements and says Yes or No to a follow-up.
Avoid: The call feels positive.Which facts may it state?
Only facts in the approved projects and pricing source, or returned by a configured tool.
Avoid: Anything it knows about real estate.What is known before the call?
company_name; optionally customer_name when supplied by an API request or campaign.
Avoid: Assume all lead details are present.What must the call produce?
property_type, budget, location, timeline, follow_up_consent, and outcome.
Avoid: Capture useful information.When does a person take over?
When the caller requests a person, needs an unsupported fact, or the request falls outside qualification.
Avoid: Transfer when necessary.03
Complete planning brief
Use this level of detail as the minimum input for the next lesson.
Property-enquiry agent plan
Agent name: Property Enquiry Assistant
Audience:
People calling after seeing or requesting information about a property.
Direction:
Inbound.
Primary job:
Capture and confirm property type, budget, preferred location, buying
timeline, and whether the caller agrees to a human follow-up.
Successful call:
The caller confirms the captured requirements and the real next action.
Approved facts:
Only project, location, amenity, pricing, and policy information in the
attached approved PDF or website, or returned by a configured tool.
Known before the call (inputs):
- company_name — default: Acme Properties
- customer_name — default: there
Captured during the call (outputs):
- property_type — flat, villa, plot, other, or unclear
- budget — confirmed amount/range with currency, or unclear
- location — confirmed preferred area/city, or unclear
- timeline — confirmed buying timeline, or unclear
- follow_up_consent — yes, no, or unclear
- outcome — qualified, not_qualified, follow_up_needed, opted_out, or unclear
Must never do:
Invent price or availability; promise returns; provide legal or investment
advice; collect passwords, one-time codes, or payment-card data; claim a
follow-up or booking happened unless a configured action confirms it.
Human fallback:
Transfer when enabled and requested. Otherwise capture the reason and offer
a human follow-up without promising an unapproved response time.
Languages and tone:
English and Telugu. Warm, concise, one question per turn.04
Verify the plan before creating anything
Every checked item should be supported by a sentence in the brief—not an assumption in your head.
05
Common planning mistakes
Fix these now; they become much more expensive after phone numbers, campaigns, and integrations are attached.
Planning a department
Why it fails
It leaves behavior, data, or ownership ambiguous.
Correct it
Split “sales, support, scheduling, payments, and complaints” into separate jobs or explicit later phases.
Using sentiment as success
Why it fails
It leaves behavior, data, or ownership ambiguous.
Correct it
Define a confirmed result the call record can show.
Putting policies in the prompt
Why it fails
It leaves behavior, data, or ownership ambiguous.
Correct it
Identify an owned knowledge source so facts can change without rewriting behavior.
Capturing everything
Why it fails
It leaves behavior, data, or ownership ambiguous.
Correct it
Keep only fields a person or system will use after the call.
Writing “escalate when needed”
Why it fails
It leaves behavior, data, or ownership ambiguous.
Correct it
Name the triggers, destination, and fallback when transfer is unavailable.
Ignoring opt-out and wrong person
Why it fails
It leaves behavior, data, or ownership ambiguous.
Correct it
Plan these as immediate stop outcomes before outbound or follow-up use.
API equivalent
Planning does not create an API resource
POST /agents/generateOpen reference The closest API operation accepts a plain-language description and returns an unsaved draft. It cannot approve your factual sources, collection purpose, transfer policy, or prohibited actions. Complete this brief first, then use it as the description in the next lesson.