Skip to main content
The avatar will play a named prospect with a specific role, company, team size, budget, and pain points — all configured via runtime variables — responding to the sales rep across the intro, discovery, pitch, objection, and close phases of a discovery call.

Tags

transition-function, require-reason, end-after-bot-response, respond-immediately, stt-keywords, runtime-vars-in-instructions, role-instruction

What this example shows

  • Scenario creation and node configuration
  • Runtime variables for prospect_name, prospect_role, prospect_company, prospect_company_size, annual_tool_budget, pain_points, sales_rep_name, sales_rep_company, objections, close_criteria
  • Connecting the scenario to the Web SDK examples

Node flow

The avatar’s role instruction:
“You are {{runtime.prospect_name}}, a {{runtime.prospect_role}} at {{runtime.prospect_company}} taking a scheduled discovery call from a sales rep…”
The scenario is structured around the following node sequence:
  • intro
    • “Greet the sales rep courteously…”
    • Uses transition tools.
  • discovery
    • “Answer the rep’s questions about your company, team, tools, and pain points honestly but without volunteering extra information…”
    • Uses transition tools.
  • pitch
    • “Listen to the rep’s pitch, then ask one clarifying question about how it would actually help your team…”
    • Uses transition tools.
  • objection
    • “Raise objections one at a time from this list: {{runtime.objections}}…”
    • Uses transition, transition tools.
  • no_sale
    • “Politely decline to move forward, briefly referencing which of your close criteria were not met without being harsh…”
    • Uses transition tools.
  • close
    • “React to the rep’s closing attempt and agree to a concrete next step.”
    • Uses transition tools.
  • end
    • “Thank {{runtime.sales_rep_name}} for their time and sign off warmly, staying in character…”
    • Ends the conversation after the assistant responds.

Node JSON to paste

Use in UI

After your scenario is saved, integrate it in your own application using the Akapulu Labs Web SDK. Web SDK examples you can pair with this scenario: In the payload to the connectConversation method, pass scenario_id, avatar_id, and runtime variables required by this scenario (prospect_name, prospect_role, prospect_company, prospect_company_size, annual_tool_budget, pain_points, sales_rep_name, sales_rep_company, objections, close_criteria), for example: