Prompts And Welcome Messages In DialNexa

Understand DialNexa prompts, system prompts, welcome messages, conversation start modes, first sentence behavior, and prompt review.

Prompts and welcome messages tell a DialNexa agent what to do and how the call begins. The prompt controls the conversation goal, the system prompt adds higher-level rules, and the welcome message controls the first spoken turn when the agent starts the conversation.

The first sentence has a job: make the caller stay on the line long enough for the second sentence to matter.

Prompt Fields And Meaning

Write each field for a different purpose.

Field	Use it for
Prompt text	The main instructions: goal, script, objections, eligibility rules, tone, and call ending behavior.
System prompt	Higher-level behavior constraints and persistent rules.
Agent identity	Who the agent is in a conversational flow setup.
Agent background	Context the agent should remember while handling flow nodes.
Welcome message	The first message when the agent is configured to start.

Conversation Start Modes

User starts

The caller speaks first. Good for inbound calls where the caller has a reason to call.

Agent defined

The agent uses a fixed welcome message. Good for outbound reminders or introductions.

Agent dynamic

The first turn can use dynamic values. Good when the greeting needs caller-specific context.

Write Prompt Instructions That Survive Real Calls

1. Name the caller goal

   Tell the agent the single most important outcome.

2. Define what not to do

   Add boundaries for speculation, pricing, escalation, or unsupported requests.

3. Use examples

   Include phrasing for short answers, objections, wrong number, busy caller, and language switch.

4. Connect tools to intent

   Tell the agent when to use functions, not just that functions exist.

5. Make the ending explicit

   Tell the agent when to end, transfer, schedule, or summarize.

Prompt Review Questions

Does the agent know success?

If success is vague, post-call fields and summaries will be vague too.

Are variables wrapped correctly?

Use placeholders such as {{first_name}} and define defaults where needed.

Does the welcome message match the route?

Inbound and outbound openings usually need different wording.

Can the prompt be shorter?

Long prompts are sometimes necessary, but repeated rules and unclear sections make behavior harder to debug.

Related Reading

Dynamic Variables

Add caller-specific values.

Single Prompt Agents

Use one instruction set.

Testing Agents

Test the first turn and edge cases.