meetingPolicy parameter lets you control how a Persona responds when a user asks to meet in person. This is especially useful on dating platforms where managing in-person meeting expectations is an important part of the user experience.
How it works
When a user brings up the idea of meeting in person, the Persona will handle it according to themeetingPolicy you set in replyParameters.
By default (when meetingPolicy is null or omitted), the Persona uses DEFAULT_MODE.
The Three Modes
DEFAULT_MODE — Warm personal excuse
The Persona declines warmly using a plausible personal excuse (e.g., a busy schedule, a family commitment, etc.). If long-term memory is enabled and the Persona already used an excuse in a previous conversation, it will reuse that same excuse for consistency. Best for: Most standard dating platforms where personas are meant to stay in-chat.DEFERRED_MEETING — Hopeful deferral
The Persona first expresses genuine interest in meeting — making the user feel heard and wanted — then softly declines with a personal excuse, and closes on an optimistic, forward-looking note. This mode keeps the door open emotionally without committing to a real meeting. Best for: Platforms where you want users to feel a strong connection and keep engagement high, while still avoiding in-person meetups.CHAT_ONLY — Firm redirect
The Persona gives a warm but firm redirect back to the chat. There is no mention of a future possibility of meeting, and no personal-life excuses are used. This mode is clear and leaves no ambiguity. Best for: Chat-only or entertainment platforms where the nature of the service (virtual-only) should be clearly communicated to users.Quick Reference
| Value | Excuses used? | Future meeting implied? | Tone |
|---|---|---|---|
DEFAULT_MODE | Yes | No | Warm |
DEFERRED_MEETING | Yes | Yes (hopeful) | Warm, eager |
CHAT_ONLY | No | No | Warm, firm |
Compatibility
meetingPolicy is supported by the chat-2-smart and chat-2-pro models. It has no effect with other model values.