Help

Overview Admin Chat Data Sync Upload Documents Search Settings Curated Answers Agents, Prompts & Functions Contact Support

Overview

Airgentic Help

Visitor Profiles

A visitor profile is the structured set of details Airgentic can save during a chat — name, email, campus, area of interest, and so on — so your advisors and CRM see the same facts the assistant learned.

The visitor does not fill in a form. The assistant records a field only when the visitor actually said it (or clearly confirmed it). Those values then appear on Human Handoff and, if you turn CRM sync on, on the matching HubSpot contact or Marketo lead. See Visitor Profiles and CRM for HubSpot and Marketo setup.

This is separate from Future Student Experience. That product builds a shareable page from an interview. Visitor profiles capture lead and qualification fields on a live chat.


What your team sees

On Human Handoff, a claimed conversation can show:

  • A visitor profile card with the known fields (name, email, campus, and any other fields configured for the service). A value filled from your CRM is marked as such, and is not shown to the visitor or used by the assistant until the visitor states it.
  • A short summary of what the visitor asked, written for the advisor.
  • Conversation tags (Callback, Enrolment, and so on), added by an advisor or by the AI.

Structured fields update as the chat continues. Tags belong to the whole conversation and stay in Insights after the session ends.


How fields are collected

Each service has its own field list. Typical fields include first name, last name, email, phone, and — for education services — campus, study area, or domestic / international.

How a field is collected What the assistant does
Required Ask before offering a callback or follow-up (for example email).
Optional Record if the visitor volunteers it; do not push.
Inferred Record when the visitor states it; do not ask a standalone question.

The assistant must not invent a value. If the visitor has not said their campus, that field stays empty. When the visitor gives a new value for a field already saved, the new one replaces it.

A follow-up extract can fill fields the assistant skipped, still only from what the visitor said. Values already saved in the conversation always win.

A playbook can override collect mode for this session only (for example make email required on a campaign landing page). If several playbooks match, the highest-priority card that sets a field wins. That does not change the schema defaults above. Playbooks can also match on a saved field, including values filled from CRM hydrate — that can add a layer mid-chat.


Field types

Type What is stored
Text Free text, kept as the visitor said it.
Email An email address. Anything that does not look like one is ignored.
Choice list One value from the allowed list you set.
Number A number.
Yes / no Yes or no.
List of text Several text values.

Choice lists

Allowed values is the only set of values the assistant may store for that field, written as a comma-separated list. Matching ignores capitals, and the stored value is the one you listed, capitals and all. A value that is not on the list is discarded, so it never reaches your CRM or the handoff card.

When the field maps to a picklist in HubSpot or Marketo, copy that picklist's values here exactly. A near miss, such as an extra apostrophe, is discarded rather than written.

The field's Description for the chat assistant is where you say how to choose. Use it for rules the list itself cannot express: which subject belongs to which value, to record the one the visitor is most interested in when they name several, and to replace the value if they change their mind.


Conversation tags

Tags are set up on Configuration & Design → Conversation tags, not as visitor-profile fields. An advisor adds them on Human Handoff, and, when AI tagging is on, the AI adds them too. The AI tags the turn in which an advisor takes the chat, then stays out while the advisor holds it, so a request such as a callback is tagged even when an advisor joins straight away. See Conversation tags.

When CRM sync is on, those labels are written to your CRM automatically. You do not add tags as a visitor-profile field, and you do not need a custom field mapping. See Visitor Profiles and CRM.


Where this is configured

For accounts that have the editor, open Configuration & Design → Visitor profile on the service card.

There you can:

  • Turn capture on or off, and turn on the follow-up extract that fills fields the assistant skipped.
  • Choose education vs other conversation type (this only changes the advisor summary wording).
  • Add, reorder, or remove fields. Each field has an id, a label shown to advisors, a type, how it is collected, and a description the assistant follows.
  • For a choice list, edit Allowed values.
  • Mark a field as Personal data. Insights then records only that the field was captured, never the value. Email is treated this way whether or not you tick it. The value is still shown on the handoff card.
  • Choose Sync to CRM per field. A field left unticked still appears at handoff; a new value for it does not trigger a CRM write.
  • Turn CRM sync on, enter HubSpot or Marketo credentials, and map extra fields. A built-in mapping you replace is marked Replaced below. See Visitor Profiles and CRM.

A live preview on the right shows the instruction block the assistant receives, for an empty session and for a sample visitor.

If your account does not show that editor yet, Airgentic can configure the field list for you.

Journey rules that use those fields live next to this editor: Configuration & Design → Playbooks. See Playbooks.


You have unsaved changes