Help

Overview
Overview What to Expect Pre-Session Checklist Your Onboarding Session
Platform Mental Model Admin & Operator Essentials Guardrails and Governance What to Use When Roles and Responsibilities Post-Session Next Steps Optional Deep-Dives Deep-Dive: Agents and Prompts Deep-Dive: Search and Knowledge Deep-Dive: Functions and Secure Services Deep-Dive: Handoff and Escalation Deep-Dive: Voice Mode Deep-Dive: Analytics and Improvement Facilitator Guide
Overview Account Overview User Management Usage
Overview General User Interface Custom External Scripts Agent Messages Voice Mode Analytics
Admin Chat UI Design Curated Answers Search Settings
Overview Concepts AI Assistant Categories Scopes Index Fields Facets Result Cards Saved Results Layout Website Integration Styling Testing Preview Funnelback Migration Troubleshooting
Conversational Intelligence Data Sync Upload Documents
Overview General Crawl Scope Image Extraction Field Mappings
Overview Creating an Agent Editing An Agent Catalog Search Overview
Overview Editing a Prompt User Segmented Prompts
Overview Writing Your First Function AirScript Functions AirScript Reference
Overview Privacy Security
Analytics API Documents Ingestion API
Human Handoff
Overview Customer Service Insights Categories And Themes Search Insights
Overview Identity Provider Widget SharePoint Integration How It Works SharePoint Checklist Implementation Checklist
Admin Console Authorisation
Methods Script Tag Gtm Analytics AI Question Input Fields
Overview Optimiser Monitor
Contact Support

Future Student on Your Website

Airgentic Help

You can offer Future Student Experience in the main website chat, on a dedicated landing page, or both. The agent is the same; only how the visitor reaches it changes.

See Future Student Experience for the product, and Website Integration for the full script-tag reference.

Dedicated landing page (recommended to start)

Pin the chat to the Future Student Experience agent with data-agent-id="future_student". The Frontline agent is skipped, so the visitor goes straight into the interview.

This is the right mode while the agent status is Testing, and it stays useful as a campaign URL after you go Live (open days, school outreach, paid ads).

<script id="airgentic-script"
        src="https://chat.airgentic.com/_js/airgentic-1.4.js"
        data-account-id="YOUR_ACCOUNT_ID"
        data-service-id="YOUR_SERVICE_ID"
        data-agent-id="future_student"
        defer></script>

Notes:

  • future_student is the agent id from Configure Agents, not the display title.
  • An invalid id falls back to normal routing.
  • Human handoff still works if you use it.
  • On a dedicated page you can omit hand_off_to_agent from the agent, because there is no other specialist to send people to.

Page copy around the widget should set expectations: a short conversation, then a page they can share with a parent. Do not promise admission, scholarships, or instant deletion of what they tell you.

Coexist in the main widget

When the agent is Live, the Frontline agent can route matching questions into the interview from your ordinary chat icon.

Use this when Study Pathways is already behaving well. If course-browse questions currently go to the Frontline agent, turning Future Student Experience live too early will pull those questions into an interview.

Keep the role descriptions distinct:

  • Study Pathways: help me find or compare named courses
  • Future Student Experience: help me figure out my future, including circumstances
  • Enrolment: apply / fees / visas as a lookup when the interview is not in progress

Once an interview has started, conversation lock keeps side questions (“what are the fees?”) with the concierge.

Testing vs Live

Status Main website chat Dedicated data-agent-id page Admin Chat
Off Not used Not used Not used
Testing Frontline will not route here Works — use this for demos Works
Live Frontline can route matching questions here Still works Works

Recommended rollout:

  1. Index and catalog filters ready (Configuration).
  2. Institution prompt written for your campuses and entry model.
  3. Agent Testing; demo only on a dedicated page or Admin Chat.
  4. Walk real stories (school leaver, mature-age, no rank / no ATAR).
  5. Switch to Live when you want the main widget to offer it as well.

What the student can do with the page

The generated page is a normal browser tab, not inside the chat bubble.

  • Copy link — the signed URL. Anyone they send it to can open it until it expires.
  • Email a parent or adviser — opens their mail app with the link in the body.
  • Print or save as PDF — uses the browser print dialog; share controls are hidden on the printout.
  • Apply / enquire / visit — your buttons. Clicks pass through Airgentic, then to the URL in configuration.

The link is bound to the retention date (future_student.retention_days). If you shorten retention, existing links stop working.

Optional email delivery (future_student.delivery including email) only sends if the student offered an address during the chat. Do not add “what is your email?” to the interview prompt.

Branding

The page picks up:

  • future_student.artifact_title (heading)
  • Service logo, if set
  • --brand-primary, --brand-on-primary, --brand-canvas, --brand-ink (and other --brand-* tokens) from your service style.css

Edit those in UI Design. You do not need a second stylesheet for the experience page.

Analytics and review

What Where
The interview Insights / conversation thread, when persist_trace_logs is on
Admin test conversations Admin Chat Trace Log
Button clicks on the page Recorded against that experience (apply, enquire, and so on)
Application or enquiry completion Your own apply / enquire systems, as today

Success for this feature is recruitment action (enquire, apply, visit), not whether the chat “sounded helpful”. If the page is accurate but nobody clicks through, check CTA URLs and landing-page copy before rewriting the interview.

You have unsaved changes